SCB provides partners who are on-boarded as billers to complete payment easily. By simply adding a payment option in your app, the app can deep link to the SCB EASY app and complete their payment seamlessly before getting re-directed back to your app on completion.
Currently, Partners can accept multiple sources of fund as follows;
Current or savings account (CASA)
Customers can make a payment by using either current or savings account as source of fund. Partners should apply for Biller (Tag30) to receive payments from current or savings account via SCB EASY App Payment. Biller ID must be different from Biller ID of SCB Bill Payment and SCB Cross Bank Bill Payment services.
Credit Card with full amount payment (CCFA)
Customers can make a payment by using a credit card with full amount payment.
Partners should apply for Merchant in order to receive credit card payment via SCB EASY App Payment.
Installment plan by credit card and/or Speedy Cash card (CCIPP)
Customers can pay with an installment plan by credit card or Speedy Cash.
Partners should apply for Merchant in order to receive installment payments (IPP) via SCB EASY App Payment and be able to specify the number of months of installment.
There are 3 types of IPP the Merchant can choose to use.
• IPP Type 1, the Merchant absorbs interest of the transaction.
• IPP Type 2, the Customer or consumer absorbs interest of the transaction.
• IPP Type 3, the Supplier absorbs interest of the transaction.
Note:
- The Merchant can choose to apply to receive a payment made with all three types of sources of funds or only accept CASA payment.
- For credit card or installment payments, customers using SCB EASY must link their cards with SCB EASY before enabling payment via SCB EASY App Payment.
Partners can create a transaction record using the deeplink URL API. Partners that have on-boarded as merchants can complete the purchase transaction swiftly by embedding a purchase option into their app. Then the users can complete the payment process using the SCB EASY app.
User Journey
SCB also allows partners to retrieve details of a transaction with the corresponding transaction ID. To do so, partners needs to specify a transaction ID in the request parameter, the transaction details of the provided ID will then be returned.
User Journey
A 'callbackUrl' is an optional parameter that can be supplied in the merchantMetadata obtained from step 6 to instruct the SCB EASY simulator app to redirect back to your app after the transaction is completed. the merchantMetadata is an optional JSON object containing any metadata the merchant needs to log regarding the new transaction. However, if the URL is not provided, there will be no redirection back to your app. For more details, refer to Deeplink for payment.
Seq No. | API Name | API Endpoints |
---|---|---|
1 | Generate Access Token | POST /v1/oauth/token |
3 | Deeplink for payment | POST /v3/deeplink/transactions |
7 | Payment Confirmation | - |
9 | Retrieve Transaction Details | GET /v2/transactions/{transactionId} |
After you have read the deeplink payment documentation, follow the guideline to test deeplink payment via SCB EASY Simulator App. You will have a better understanding of the processes involved in integrating SCB EASY.