What is our Android SDK?

  Last updated: 

 

The Trust Payments Android SDK allows you to seamlessly integrate a prebuilt or custom UI in your app to accept card payments & comply with the Strong Customer Authentication (SCA) mandate.

  Use this integration if you need a pre-built “Drop-In” UI that supports the following features:

  • Card payments
  • Tokenization payments
  • Customisation of UI components to fit with your business branding
  • Locale and custom translations

Otherwise if you have already built your own payment checkout view in your Android app, but need a method to process payments to the Trust Payments gateway, you can use our Payment Transaction Manager API.

 

Key features of our Android SDK

  • Enables customers to make purchases on your app using credit / debit cards.
  • Handles the customer’s payment session, including any Strong Customer Authentication (SCA) required by 3-D Secure.
  • Allows data to be transmitted directly from the customer’s session to Trust Payments in a secure manner.
  • The appearance of the checkout UI can be customised to fit with your business branding.
  • Supports a number of different languages and locales.

  All businesses within the EEA (European Economic Area) will soon be mandated to be PSD2 compliant

By following the steps outlined in these documents, you will meet the requirements needed to continue processing e-commerce transactions.

Click here for further information on this mandate

 

How does the Android SDK work?

  • When the customer taps on the submit button hosted on your checkout form, the SDK will contact the card issuer to check if the card is enrolled in 3-D Secure.
  • If the card is not enrolled, a payment is processed automatically.
  • If the card is enrolled, the card issuer will check if the payment is deemed high risk.
  • Customers processing low-risk payments bypass Strong Customer Authentication (SCA) and the payment is processed automatically.
  • Customers processing high-risk payments are authenticated using SCA prior to the payment being processed.
  • Following the payment session, your app will need to handle the response returned and display a relevant success or error message to your customer.

 

What will the customer see?

The following diagrams show standard e-commerce transactions using 3-D Secure:

When payment is deemed low-risk


Frictionless payment allows for a streamlined checkout experience

CA1-EN.png

  1. The customer enters their card details on your checkout and taps the “Pay” button.
  2. Data regarding the payment session and customer’s device is shared with the card issuer. The customer is deemed low-risk, so no action is needed on their part to verify their identity.
  3. Following these checks the payment will be processed. The checkout will then display a success message to the customer.

When payment is deemed high-risk


Customer will be challenged prior to completing the purchase

CA2-EN.png

  1. The customer enters their card details on your checkout and taps the “Pay” button.
  2. Data regarding the payment session and customer’s device is shared with the card issuer. The customer is deemed high-risk, so their device may display an overlay prompting them to complete some basic actions to authenticate their identity.
  3. Following any authentication steps required by the customer’s card issuer, the overlay will close automatically, and the payment will be processed. The checkout will then display a success message to the customer.

  If the authentication fails, your checkout will display an error message and provide the customer an opportunity to re-attempt payment or provide an alternative card.

 

Authentication

When using the latest version of our Android SDK, all e-commerce payments can be configured to be automatically processed with 3-D Secure. 3-D Secure is a protocol overseen by card issuers, designed to reduce fraud and chargebacks by authenticating the customer’s identity at the point of sale. For a fully authenticated 3-D Secure transaction, in the event of a dispute at a later date, the card issuer will usually take liability of the chargeback instead of the merchant.

 

 

Benefits of 3-D Secure


  • Enhanced data checks: Data regarding the payment session and customer’s device is shared with the card issuer, allowing for risk-based decisions without always needing to seek authentication from the customer. This reduces the time that the average consumer takes to complete a transaction.

  • Easy authentication: Authentication can now be performed by biometrics (fingerprint / facial recognition). This makes it easier for your customers to complete payments and ultimately reduces shopping cart abandonment.
  • Native mobile support: There is comprehensive support for modern mobile devices, ensuring a seamless checkout experience from within your app.

CA3-EN.png
Example 3-D Secure overlay displayed to the customer

 

How do I get started?

  Android SDK

To begin processing payments with our Mobile SDK, you will need to install the SDK and initialise it within your Gradle project. Click here to continue.

Was this article helpful?
0 out of 0 found this helpful