Commerce Connect - Overview

Purpose

This integration guide defines an overview of steps required to integrate the Commerce Connect SDK with a Merchant mobile application.

This guide is targeted to be used by technical representatives of a Merchant's mobile development team.

Commerce Connect SDK Overview

The Commerce Connect SDK provides a drop-in solution for Merchants which has built-in UI and workflow for accepting payment through mobile application. The Commerce Connect SDK will show end to end UI (multi-step, multi-screen) and makes Payment API calls in the background to complete the transactions. Merchant can choose to use different combinations of payment modes which can be configured through server-to-server call between Merchant Server and Fiserv APIs. This will happen outside the scope of the Commerce Connect SDK.

Payment processing via Commerce Connect checkout

The payment process starts at the click of pay button on merchant order summary page. On this click, you need to:

1. Create an order in your order system and then generate sessionID. sessionID is used for detecting errors or tampering introduced during its transmission of request. sessionID is generated using merchantID which should be kept only on server side for security reasons.
2. Redirects the customer to Commerce Connect SDK with sessionID and ConfigID.
3. Customer fills payment details and completes the payment authentication. Once the payment is complete, redirected to app using callback with status.
4. Lastly, verify transaction status with TransactionStatus API via server to server call. This protects you from scenarios where your account credentials are compromised or request/response has been tampered.

SDK Configurations

SDK provides a variety of configurations for theme.

Merchants can provide their desired theme configuration during SDK initialization for Android.

For Android, the theme information is automatically taken from the colors.xml configuration file from the merchant mobile app.