Skip to main content

Checkout sequence diagram

The diagram presented below exemplifies the integration sequence encompassing the requests and responses necessary to successfully execute a BNPL process from start to finish. This sequence diagram serves as a visual aid to facilitate a step-by-step comprehension of the entire process, ensuring clarity and intuitiveness. It is important to note that while this diagram provides a general framework, certain steps may differ based on your specific integration requirements. Feel free to adapt and customize the sequence to suit your needs accordingly.

From the initial request to the final response, every step is documented in detail in the next sections of this document.

alt text

(1) The customer is at the merchant's checkout page and desires to finance their purchase.
(2) The merchant sends a POST Login requests with their credentials.
(2R) Nemuru returns an access token that will be used by the merchant to authenticate following requests.
(3) The merchant sends a POST Create Order requests with available customer and cart data.
(3R) Nemuru returns the order_id within the response.
(4) The merchant uses Nemuru's JavaScript library (nemuru.js) to open the Checkout widget for the order_id provided in the previous step.
(4R) Nemuru renders the Checkout widget within the merchant's checkout page.
(5) The customer completes the payment process.
(6) When the customer completes the purchase, Nemuru will send a callback to the merchant's notification_url, provided in step 3, indicating the order is approved and requires a confirmation.
(6R) The merchant confirms the order by either responding with autoconfirm: true to indicate Nemuru that the order has to be autoconfirmed –Nemuru automatically confirms the order with the corresponding lender– or, alternatively, passes the current order information to Nemuru again (cart and customer data).
(7) Nemuru sends a callback to the merchant's notification_url indicating the order is confirmed.
(7R) The merchant responds OK.
(8) Nemuru displays the confirmation message to the customer.
(9) The customer closes Nemuru's checkout widget.
(10) Nemuru informs the merchant the widget has been closed via client-side callback.
(11) The merchant redirects the customer to the confirmation page.
(12) The merchant creates a capture to inform Nemuru the order has been shipped.
(12R) If correctly captured, Nemuru responds OK. The captured amount will be transferred to the merchant in the following disbursement.