Introduction

The payabl. Mobile SDK is a unified solution for accepting payments in your iOS and Android apps. Rather than handling sensitive payment data in your application, the SDK manages all cryptographic operations and token exchanges securely with the payabl. gateway. Your application's primary responsibility is to trigger payment flows using session credentials (sessionId and ephemeralKey) provisioned securely by your backend.

It provides a Hosted Payment Page covering all supported payment methods in a single integration, plus standalone integrations for individual payment methods if you need finer control.

Supported payment methods

How it works

Every payment method follows the same architectural pattern:

1. Your backend requests session credentials from the payabl. gateway and passes them to your app.
2. Your app triggers the payment flow using those credentials.
3. The SDK handles payment processing and all user interaction, then returns the result via callback handlers your app uses to update order status and UI.

Integration path

Follow these steps in order for the fastest route to your first sandbox transaction:

1. Try the demo app

See the SDK in action before writing any code. The demo apps run against the payabl. sandbox using a pre-configured demo merchant — no account, server setup, or SDK access required. They cover every payment method and integration pattern, with commented source code you can adapt directly.

2. Get SDK access

The SDK is distributed through private GitHub repositories. Request access and set up your package manager.
→ SDK Access Guide

3. Set up your server

Your backend creates payment sessions and provisions credentials to your app. This step is required for every payment method on both platforms — the demo app skips it only because it uses a payabl.-hosted demo merchant configuration.
→ Setup Your Server

4. Integrate your platform

Configure your project, then integrate the Hosted Payment Page or the standalone payment methods you need.

5. Test your own integration

Use our sandbox test data — test cards, bank simulator values, and wallet test setup — to exercise success, failure, and cancellation flows.
→ Testing

6. Troubleshoot with the Error Code Reference

Every error returned by the SDK and backend is cataloged with its cause and the action to take.
→ Error Handling & Troubleshooting

6. Mobile SDK FAQs

Please find our FAQ section to frequently answered questions
→ Mobile SDKs FAQs

Requirements

Need help?

If you run into an issue the Error Handling & Troubleshooting doesn't resolve, contact [email protected] with your merchant ID and the error code you received.