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

Order Updation Events

1. updateOrder Event

Allows the merchant to update the orderDetails payload after Juspay Payment Page has been opened (SDK process call is done).

updateOrder Payload Structure

As the orderDetails payload is being changed, it is mandatory to generate a new signature as well that corresponds to the updated payload.

2. paymentAttempt Event

This event is triggered from Juspay to merchant on clicking the "Proceed to Pay" button (on Juspay Payment Page).

This is a blocking call and it is applicable to all payment instruments; for merchant’s approval for proceeding with the transaction initiation to payment gateway.

paymentAttempt Payload Structure

3. resumePayment Event

In response to paymentAttempt, merchant needs to call the resumePayment event with hyperServices.process call.

Status value true is indicative of merchant approval to proceed with the transaction, whereas false aborts the payment and SDK exits to return control back to merchant website.

resumePayment Payload Structure

If the orderDetails payload is being changed, it is mandatory to generate a new signature as well that corresponds to the updated payload. Else, merchant can skip the orderDetails payload and signature from this call.