Overview
The PaySuite Mobile SDK provides complete and customisable ways to process payments for mobile apps (Android and iOS).
Features
-
Enhance the customer experience with native in-app payments
-
Supports all major cards, Apple Pay and Google Pay
-
App support for Android and iOS based devices
-
Process payments using Strong Customer Authentication (3DSv2.x)
-
Full card token support
-
The data transfer between the UI components and the central payment processor business logic through the payment journey is not accessible or exposed to the customer, merchant or integrator.
-
Easy to set up payment process, with an integrator-built UI that fits all needs
-
Customisable UI components available for Android Views, Jetpack Compose and Swift
-
Allows the integrator to build the whole payment page to fit their app
Getting started
We recommend reading the pages in the following order:
- Pre-Requisites
- Setup
- Authentication Token
- Payment Setup
- Payment Methods
- UI Components
- Testing
- Migrate to Production
For Pay by Bank (Open Banking), start with the Pay by Bank Mobile SDK section after Payment Setup.
Release notes
1.3.0 Release
New features
- Pay by Bank (Open Banking) payments, with a built-in Pay by Bank button for Compose, Android Views and iOS. See Pay by Bank with the Mobile SDK.
setTransactionIdCallbackreceives the API-assigned transaction id as soon as the API returns it, before the payment finishes - useful for tracking a payment while 3-D Secure, the wallet sheet or the bank redirect is still in progress. See Transaction id callback.- Open Banking: the SDK sends a single resume when the customer returns. If the provider is still processing the transaction, it is returned as
Status.Pendingwith its transaction id, so it can be retrieved for the final status; the resume is never retried. A transaction the bank already finished is reported with its outcome - success when it completed, error when it was declined. See Pending transactions.
Improvements
- The SDK has moved to the latest stable toolchain, including Android API 37 compliance - ready for apps targeting Android 17.
- Improved autofill support on the card input fields.
- Accessibility: the Google Pay button now exposes a "Google Pay" label to TalkBack and other screen readers.
Bug fixes
- Android: cancelling a 3-D Secure challenge from the ACS page's own cancel control now reports a cancellation to the payment result callback, instead of an error or leaving the payment unresolved.
- The saved-card list on the payment page now refreshes immediately after a card is deleted.
- Failed payments are now correctly reported to your error callback, with the reason returned by the gateway.
1.2.2 Release
New features
- Added token based authentication for Card Management (docs)
Bug fixes
- Fixed a case where the Apple Pay result was not returned correctly
Deprecation
- Deprecated basic authentication for Card Management
1.2.1 Release
Bug fixes
- Fixed connectivity issues with iOS and Flutter
1.2.0 Release
Improvements
- Strengthened duplicate processing prevention for payment sessions
Bug fixes
- Fixed connection status not being updated properly in some edge cases
- Fixed
rememberPaymentProcessingnot keeping state on recomposition - Fixed Google Pay button not being hidden after the payment session is detached
Performance & infrastructure
- Improved performance and stability across all platforms
1.1.0 Release
Improved reliability
- Enhanced error handling and stability across payment processing and card management.
Better user experience
- Updated the look and feel of card management and payment screens for both Android and iOS. Improved accessibility and made it easier to manage saved cards.
Security & compliance
- Added more transparency around data protection and encryption.
Performance & infrastructure
- Improved performance and stability across all platforms
1.0.5 Release
Improvements
- Enforcing billing address data being required to use Google Pay. This is already pre-filled by most if not all Google Pay customers as a requirement to use the method. The enforcement combats scenarios where the payment method would return the bare card details instead of a token, and in that scenario a cardholder name is required: the cardholder full name from the wallet’s billing address is sent to the API instead.
Bug fixes
- Fixed
billingAddressobject not being sent under thepaymentMethodobject - Fixed a concurrency crash in 3DS caused by the Android WindowManager while trying to dismiss an already dismissed dialog
API changes
- Internal: added a new field for the cardholder name,
googlepay.paymentMethod.cardHolderName