Skip to main content

Documentation

Create Checkout Message Sequence - Bank Redirect

Diagrams and steps for when a customer pays via hosted page from their bank account.

During checkout, the customer is redirected to log in to their online banking site, respond to any authentication requirement, and approve the payment.

Success

This diagram shows the sequence of events when the customer selects a bank redirect payment method and completes the bank's requirements.

  1. The client sends Create Checkout Page request to Rapyd.

  2. Rapyd sends a response containing a redirect URL to the client.

  3. The client sends the URL to the customer.

  4. The customer selects a bank redirect payment method, completes the checkout page, and submits it directly to Rapyd.

  5. Rapyd sends Webhook - Payment Succeeded to client. The status of the payment is set to ACT (active).

  6. Rapyd redirects the customer to the bank's website.

  7. The customer completes the bank's requirements.

  8. The bank sends the funds to Rapyd.

  9. Rapyd credits the designated wallet and sends Webhook - Payment Completed to the client. The status of the payment is set to CLO (closed).

Failure - Payment Declined

This diagram shows the sequence of events when the customer selects the bank redirect payment method via a hosted page and the bank declines the payment.

  1. The client sends Create Checkout Page request to Rapyd.

  2. Rapyd sends response containing a redirect URL to the client.

  3. The client sends the URL to the customer.

  4. The customer selects the bank redirect option, completes the checkout page, and submits it directly to Rapyd.

  5. Rapyd sends Webhook - Payment Succeeded to the client. The status of the payment is set to ACT (active).

  6. Rapyd redirects the customer to the bank's website.

  7. The customer completes the bank's requirements incorrectly or has an account issue.

  8. The bank declines the payment.

  9. Rapyd sends Webhook - Payment Failed. The status of the payment is set to ERR (error).

Failure - Payment Expired

This diagram shows the sequence of events when the customer fails to authenticate or approve the transaction before the payment expires. See Checkout Page expiration and payment_expiration for more information.

  1. The client sends Create Checkout Page request to Rapyd.

  2. Rapyd sends response containing a redirect URL to the client.

  3. The client sends the URL to customer.

  4. The customer selects the bank redirect option, completes the checkout page, and submits it directly to Rapyd.

  5. Rapyd sends Webhook - Payment Succeeded to the client. The status of the payment is set to ACT (active).

  6. Rapyd redirects the customer to their bank's website.

  7. The customer fails to complete the requirements before the payment expires.

  8. Rapyd sends Webhook - Payment Expired. The status of the payment is set to EXP (expired).