Ready-to-Use Checkout Screens

To speed up your development process, we provide ready-to-use checkout screens. This takes away the burden of having to design and implement your own checkout screens. These screens define a customizable checkout flow which integrates nicely into your application.

There are two ways you can use our checkout screens. The following table will help you choose the solution that works best for you.

1. More flexible solution, use drop-in buttons or any other controls to display payment brands2. The best way to add specific payment brand to your app

Payment methods

Synchronous payments

In case of synchronous payments, shopper's payment details are collected only in the app. No redirects for additional checks and authentication are needed.

To learn how to integrate SDK with our prebuilt checkout forms, follow the First Integration guide.

Asynchronous payments

For some payment methods additional shopper verification (3D Secure) or account authentication is required. In this case the shopper will be redirected from the payment form to the issuer page to verify his identity.

Brand management

In the merchant and administration portal (BIP) - allowing to update the brands offered to shoppers without requiring an update of the mobile app.

Located under "Administration > COPYandPAY > Categories > Brands", you optionally can define which brands are displayed in the checkout by configuring the "Allowed Brands" on a channel, or any of its parents/ancestors.

To activate the brand configuration through the merchant and administration portal (BIP), first set the "Activate Brand Management" to TRUE.

The last setting "Override shop brands" is used to decide on the policy to propagate new Brands you enter to the checkout:

Either override whatever was defined in the shop. (Value TRUE)

Or offer only brands for payment, that are both specified in the BIP and in the checkout settings in the app (Value FALSE, default)

UI customization

We built the Checkout project so that from the default theme that we provide you can define your own appearance and apply the attributes you want to customize.

Credit card scanning

You can scan your credit card to enter your payment information for a purchase, saving you from having to key in your digits manually.

This feature is not enabled by default, refer to the Card scanning guide for integration details.

Store payment details

You can enable option to store payment details, it is supported for credit card and bank account details. Shopper's payment details are stored with unique identifier (token), which can be used for future payments.

Protect payments with Touch ID / Face ID

You can provide additional security for your shoppers by enabling biometric authentication for payment confirmation.
To complete payment shopper will have to authenticate with Touch ID of Face ID, if they are set on device, otherwise device passcode will be requested.

It's recommended to enable this protection for tokens (stored cards and back account information).
Biometrics authentication can be configured for any payment brands as well.

To configure device authentication create an appropriate OPPSecurityPolicy and add it to the securityPolicies option of the OPPCheckoutSettings.OPPSecurityPolicy applies specified mode for tokens or list of payment brands.

Protect payments with device authentication

NOTE: This functionality available only for Android 5.0 (API level 21) and higher.

You can provide additional security for your shoppers by enabling payment confirmation with device authentication.
To complete payment shopper will have to provide their credentials (Pattern, PIN, Password or Fingerprint if available).

It's recommended to enable this protection for tokens (stored cards and back account information).
Protection with device authentication can be configured for any payment brands as well.

There are three modes of requesting device authentication

NeverCheckoutSecurityPolicyMode.DEVICE_AUTH_NOT_REQUIRED

Device authentication is disabled.

If availableCheckoutSecurityPolicyMode.DEVICE_AUTH_REQUIRED_IF_AVAILABLE

App requires device authentication only if it is set by user.

AlwaysCheckoutSecurityPolicyMode.DEVICE_AUTH_REQUIRED

Device authentication is required to complete payment. Payment brand won't be available if device is not secured, i.e. Pattern, PIN, Password or Fingerprint is not set.

You can configure device authentication per payment brand. For example: