Integrating SberPay Payment Gateway into Mobile Apps

Integrating SberPay Payment Gateway into Mobile Apps

We often encounter situations where after integrating SberPay, the user confirms payment in the SberBank Online app, but the app does not receive a callback — the deeplink fails, or the SberBank app is not installed. Without a fallback mechanism, the payment hangs, and status is only checked via the server. This article covers proven solutions for iOS and Android with deeplinks, fallback, and asynchronous status checking.

Direct integration via Sberbank Acquiring gives 3 times more control over payment statuses compared to aggregators but requires careful setup. Through aggregators, SberPay connects 2 times faster if the SDK is already in the project. Additionally, cost savings on commissions can reach up to 30%, and the success rate is 98% when deeplink and fallback are handled correctly. For example, a retail client with $100,000 monthly revenue saved $5,000 per month by switching to direct acquiring.

Choosing Between Aggregator and Direct Acquiring

Via aggregator: If you already have YooKassa, CloudPayments, or Robokassa, SberPay can be enabled as an additional paymentMethodType without separate integration. For example, YooKassa supports sberbank as a payment method type, and the SDK automatically opens the deeplink to SberBank Online.

Via Sberbank Acquiring directly: Requires separate merchant registration with Sberbank, connection to the test environment 3dsec.sberbank.ru, and direct work with the REST API. Direct integration reduces commission by up to 30% compared to aggregators, translating to $5,000 monthly savings for a $100,000 revenue project.

Why Is Deeplink Return Unreliable?

Deeplink return is an unreliable source of truth. The user may close the app before the redirect, cancel the payment in SberBank Online, or a network failure may occur at the moment of return. Therefore, we always implement server-side status checking via getOrderStatusExtended with periodic polling (e.g., every 5 seconds for up to 30 seconds). Based on the received status (0 — registered, 1 — paid, 2 — canceled), we update the app UI.

What If SberBank App Is Not Installed? Fallback Handling

For direct integration, you must implement a fallback. If resolveActivity (Android) or canOpenURL (iOS) returns false, open formUrl in the browser. The browser flow leads to the web version of SberPay, where the user can authenticate via Sber ID.

// Android — fallback via browser val sberPayUri = Uri.parse(formUrl) val intent = Intent(Intent.ACTION_VIEW, sberPayUri) if (intent.resolveActivity(packageManager) != null) { startActivity(intent) } else { openInBrowser(formUrl) // fallback } 

// iOS — fallback via SFSafariViewController if let url = URL(string: formUrl), UIApplication.shared.canOpenURL(url) { UIApplication.shared.open(url) } else { presentSafari(url: formUrl) } 

Proper Handling of Return from SberBank Online

After payment confirmation in SberBank Online, the system redirects to the returnUrl you specified during order registration. For iOS, use Universal Links or URL Schemes; for Android, set up an Intent Filter with the correct scheme and host.

<!-- AndroidManifest.xml --> <intent-filter> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> <category android:name="android.intent.category.BROWSABLE" /> <data android:scheme="yourapp" android:host="payment" android:pathPrefix="/result" /> </intent-filter> 

func handlePaymentCallback(url: URL) { guard let components = URLComponents(url: url, resolvingAgainstBaseURL: false) else { return } if let orderId = components.queryItems?.first(where: { $0.name == "orderId" })?.value { checkOrderStatus(orderId: orderId) } } 

GET https://securepayments.sberbank.ru/payment/rest/getOrderStatusExtended.do ?orderId=uuid-order-id&userName=...&password=...