Once the checkout page is opened, your users can proceed with the transactions. Rendering the checkout page requires multiple process SDK calls from the merchant application.
Each process SDK call takes a specific JSON Object as argument. This argument is also known as process payload. Sample payloads for rendering the checkout screen can be found under the category - Displaying payment options on the payload samples
page.
Rendering the checkout page requires the following process SDK calls from the merchant application -
Get Payment Methods
Card - List Saved
UPI - Get Available Apps
Wallet - Refresh All
Eligibility - Wallets
Is Device Ready
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.
Parse and consume the SDK response for the process SDK calls listed in step 4.2. The SDK responds with the following respectively -
Available Payment methods
User Stored Cards
List of Active UPI Apps
Updated Wallet Balances
Eligible Paylater/Postpaid wallets
Eligibility for in-app flow in PhonePe & GooglePay
Sample response for rendering the checkout screen can be found under the category - Displaying payment options on the payload samples page.
