In order to render the payment methods on the checkout screen, merchant app needs to make multiple process SDK calls(as mentioned in Step 4.2). Once the checkout screen is rendered users can proceed with the transactions.
Each process SDK call takes a specific JSON Object as argument. This is known as the process payload. Sample payloads for rendering the checkout screen can be found under the category - Displaying payment options on the payload samples
page.
Based on the required payment methods, rendering the checkout page requires the following process SDK calls from the merchant application
|
Process Call
|
Purpose
|
|---|---|
List all the available payment methods
|
|
List the cards stored for a user
|
|
List of Active UPI Apps
|
|
Fetch latest balance for linked wallets
|
|
Fetch Eligible BNPL/Consumer Finance options
|
|
Check eligibility for PhonePe and GooglePay in-App Flow
|
On the payload samples page, sample request and response for rendering the checkout screen can be found under the category - Displaying payment options
All these process SDK calls can be made in parallel
Process SDK call is to be made on the same instance of HyperService using which initiate API was triggered. It should not be called on an HyperSDK instance which has not been initiated.
