Document Details

1. Document Details

1.1 Scope

This document provides information to assist with the integration of the Velocity Payment Orchestration Platform (POP) software development kit (SDK) with an Android native mobile application.

Note: Integration with an iOS mobile application has a similar workflow, but the details are provided in the Velocity – iOS SDK – Integration Guide v1.12.

1.2 Version

The following table provides details about the various SDKs and features listed in the document.

Document VersionSDK NameSDK VersionAdditional Features
  • Modirum 2.0
  • Payment Integrations
    • SWISH
    • G-Cash
    • PayMaya
  • HMAC changes
    • Updated Airline Data support
    • Auth-token support
    • FX Service indicator
    • Presentment currency
  • Added support for base SDK v2.0.0
  • Offline payment card support
  • Handled Sub-Code in URL scheme redirect
  • FX Service based routing support
  • SDK Improvements
  • Introduced the following:
    • Travel Fund Vouchers
    • Split Payments
  • Enhancements
    • SDK Improvements
    • Added support for base SDK v2.1.0
1.07mPoint2.3.3Introduced the following:
  • Instalments
  • SDK Improvements
1.08mPoint2.4.0Introduced the following:
  • Split Payments
  • SDK Improvements
1.09mPoint2.4.0Updated the template.
1.10mPoint2.5.0Introduced the following:
  • PayU – Online and Offline
  • SDK Improvements
  • Added support for Base SDK 2.2.0
1.11mPoint2.5.0Introduced the following:
  • STRIPE Integration
  • NMI Integration
  • SDK Improvements
1.12mPoint2.6.0Introduced the following:
  • SAFETY PAY Integration
1.13mPoint2.6.0Updated document template.

2. Introduction

Velocity SDK facilitate integration of Velocity POP with native mobile application. SDKs can be integrated with both Android and iOS applications. The SDKs use asynchronous communication when transmitting data to the Velocity server or a Payment Service Provider (PSP).

The following are some features of SDKs:

  • Simple integration with a few calling methods
  • Multiple payment methods such as APM, wallets, mVault or stored card, and cards with 3DS and
  • Native user interface (UI) elements
  • A familiar technology stack for application developers
  • Capability to control and brand the payment screen
  • Application and POP communication through SDKs

3. Glossary of Terms

The terms used in this document are listed in the table below.

CPDCellPoint Digital.
POPPayment Orchestration Platform.
HPPHosted Payment Pages.
PSPPayment Service Provider.
MerchantAny business who sells goods or services and accepts payments from customers;
also referred to as Clients.
CustomersIndividuals who want to buy goods and services from the merchant.
APMAlternative Payment Methods.
SDKSoftware Development Kit.

4. Prerequisites for Integration

After you are onboarded on the Velocity platform, you can start integrating your mobile application with the Velocity SDK.
Before you start the integration process, you must ensure that you have the following:

  • Velocity SDK, which includes the following:
    • Base SDK
    • mPoint SDK
  • Third-party SDK (optional)
  • Nexus URL
  • CPD credentials such as:
    • Username
    • Password
    • Client ID
    • Account ID
    • MESB_URL
  • Country and currency for which transaction is enabled
  • List of CPD country codes
  • Salt values for payment fraud transaction (optional)
  • Sample test application