JavaScript is disabled. Some features may not work. You can also read the static version: View text version

4. Rendering the Checkout Screen

Once the checkout screen is opened, your users can proceed with the transactions. Rendering the checkout screen 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.

All the below process SDK calls(mentioned in step 4.1 and 4.2) 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.

Step 4.1.

List Payment Methods

List payment methods process SDK call provides a list of all the payment methods available for your account, allowing you to display the available payment options on the payment page.

If a static list of payment methods is maintained to display on the payment page, and those payment methods are not enabled on Juspay’s dashboard, the transaction will fail at Juspay’s end without being initiated to the underlying gateways or processors.

Step 4.2

Process SDK Calls for rendering Checkout Page

During the checkout page rendering, saved cards and linked wallets must be displayed. To retrieve this information, the respective process SDK calls (based on the integrated payment methods) need to be made.

Scroll inside to view more

Process Call	Purpose
Card - List Saved	List the cards stored for a user
Card - Info	Fetch the card details on the bin input