Integrating CloudPayments Payment Gateway into Mobile Apps
We've seen too many mobile apps ready for release with payment acceptance reduced to a stub. CloudPayments — a Russian payment gateway — solves this in 1–2 days if you understand the architecture. Our team has integrated CloudPayments SDK in 30+ projects across iOS, Android, and Flutter, ensuring stable handling of non-trivial cases (3DS2, Apple Pay, refunds). For instance, on one project we implemented both Apple Pay and Google Pay in a single day using the SDK's built-in methods.
Why a Card Cryptogram?
CloudPayments never passes raw card data through your server, reducing PCI DSS scope. Payments become safer because the client generates a cryptogram using the merchant's PublicID. The cryptogram is an encrypted token that doesn't contain full card details. It is sent to your server, which forwards it to CloudPayments API for fund capture. This approach is three times more secure than storing PAN on the server.
// Android: generating cryptogram val cardCryptogram = Card.cardCryptogram( cardNumber = "4111111111111111", cardDate = "12/25", cardCvv = "123", merchantPublicId = "pk_your_public_id" ) // iOS: generating cryptogram let cryptogram = CPCryptogramPacket.makePacket( cardNumber: "4111111111111111", expirationDateString: "12/25", cvv: "123", merchantPublicID: "pk_your_public_id" ) On the backend, call the POST /payments/cards/charge endpoint with the cryptogram, amount, and order ID. Note: the cryptogram is single-use and time-limited — an extra layer of protection.
Handling 3D Secure
If the issuing bank requires verification, the CloudPayments API returns a 3ds status with AcsUrl, PaReq, and TransactionId. The SDK provides ready-made components to display the 3DS WebView. After the user enters the SMS code, the SDK returns PaRes — your server sends it to POST /payments/cards/post3ds to complete the payment.
// Android: launching 3DS via SDK ThreeDsDialogFragment.newInstance( acsUrl = response.acsUrl, transactionId = response.transactionId, paReq = response.paReq ).show(supportFragmentManager, "3ds") On iOS, use D3DSViewController from the SDK with the same parameters.
When to Use the SDK's Built-in UI?
CloudPayments SDK includes PaymentForm — a card entry screen with Visa, Mastercard, Mir logos and automatic validation. If custom design isn't critical, this speeds up development considerably.
val intent = PaymentActivity.getStartIntent( context, cpApiPublicId = "pk_your_public_id", totalAmount = "1500", currency = Currency.RUB, invoiceId = "ORDER-1234", description = "Order payment" ) startActivityForResult(intent, REQUEST_CODE_PAYMENT) Integrating Apple Pay and Google Pay
CloudPayments SDK offers dedicated methods for Apple Pay (iOS) and Google Pay (Android). For Apple Pay, set up an Apple Merchant ID in your CloudPayments dashboard and enable the capability in Xcode. Google Pay requires configuration in the Google Pay Console. After that, the SDK automatically displays the Apple Pay or Google Pay button on the payment screen. On success, the SDK returns a cryptogram, which is processed normally. Contactless payment integration takes about one day once merchant accounts are ready.
Why Cryptogram is Safer than Storing PAN?
The cryptogram contains no full card number, expiry date, or CVV. It is generated client-side using CloudPayments' public key and cannot be decrypted without the private key on the gateway side. Even if intercepted, the cryptogram cannot be reused. Additionally, CloudPayments does not require merchants to be PCI DSS certified, reducing security overhead.
Comparison: Custom Implementation vs CloudPayments SDK
| Criterion | Custom Implementation | CloudPayments SDK |
|---|---|---|
| Integration time | 2–4 weeks | 1–3 days |
| 3DS2 support | Requires certification | Out of the box |
| Apple Pay / Google Pay | Long setup | 1 day |
| Updates for payment system changes | Manual | Automatic |
CloudPayments cuts time-to-market for payments by 10x compared to direct acquirer connection.
Common Pre-Release Pitfalls
Before submitting to app stores, check:
- PublicID must not be hardcoded — use Build Config.
- Cryptogram is generated only on the client, never save it.
- 3DS WebView should handle timeouts (typically 10–15 minutes).
- For Apple Pay, ensure Apple Merchant ID is configured and the capability is enabled in Xcode.
- Test with test cards:
4111111111111111(success),4000000000000002(insufficient funds).
Integration Stages and Timelines
| Stage | Duration |
|---|---|
| Project analysis and PublicID preparation | 1–2 hours |
| SDK integration and cryptogram setup | 0.5 day |
| 3DS handling and testing | 0.5–1 day |
| Apple Pay / Google Pay (optional) | +1 day |
| Final testing and release | 0.5 day |
What's Included in Our Work
- CloudPayments SDK integration (iOS / Android / Flutter)
- Cryptogram generation and backend transmission
- 3DS handling via SDK components
- Optional: Apple Pay / Google Pay through CloudPayments
- Testing with test cards and PublicID
- Guidance on notification setup (Push, Email) and refunds
Timelines
2–3 days for basic integration. Cost is calculated individually after project analysis. Get a consultation on integrating CloudPayments into your mobile app — our engineers will assist with SDK setup, 3DS, and contactless payments. Order implementation and we'll propose the optimal solution for your stack and deadlines.