Merchant calls our bnplx.io API with payment details. We process and store the payment information, then build the appropriate request body for the selected BNPL provider.
We call the BNPL provider with the formatted request. The provider evaluates customer creditworthiness and processes the payment.
If the payment requires customer action (requires_customer_action state), the customer is redirected to the BNPL provider’s page to complete additional information or verification steps.
Based on customer actions and provider evaluation, the payment either succeeds and moves to requires_capture state, or fails.
When payment is in requires_capture state, the merchant can capture the payment anytime through our API, which in turn captures with the BNPL provider.
State | Description | |
---|---|---|
Succeeded | payment has succeeded | |
Failed | payment has failed | |
Cancelled | payment has been cancelled | |
Processing | payment is still being processed | |
RequiresCustomerAction | payment is waiting on some action from the customer | |
RequiresMerchantAction | payment is waiting on some action from the merchant | |
RequiresPaymentMethod | payment is waiting to be confirmed with the payment method by the customer | |
RequiresConfirmation | payment has to be confirmed | |
RequiresCapture | payment has been authorized, waiting to be captured | |
PartiallyCaptured | payment has been captured partially and remaining amount cannot be captured | |
PartiallyCapturedAndCapturable | payment has been captured partially and the remaining amount is capturable |