Cards & Wallets · Mobile SDK

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:

  1. Pre-Requisites
  2. Setup
  3. Authentication Token
  4. Payment Setup
  5. Payment Methods
  6. UI Components
  7. Testing
  8. Migrate to Production

Release notes

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 rememberPaymentProcessing not 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 billingAddress object not being sent under the paymentMethod object
  • 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