Skip to main content

Documentation

Create Checkout Message Sequence - Bank Transfer

Diagrams and steps for when a customer chooses to pay with a bank transfer via a hosted page.

Bank transfers require the customer to interact with the bank via their website, by calling on the phone, or visiting the branch in person.

Success

This diagram shows the sequence of events when the customer selects the bank transfer 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 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 presents the bank transfer instructions to the customer via the hosted page.

  7. The customer accesses the bank's website, visits a bank branch, or contacts the bank by phone.

  8. The bank sends funds to Rapyd.

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

Failure - Payment Declined

This diagram shows the sequence of events when the bank declines the transfer due to insufficient funds or other account issues.

  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 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 presents the bank transfer instructions to the customer via the hosted page.

  7. The customer accesses the bank's website, visits a bank branch, or contacts the bank by phone.

  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 complete the transfer requirements before the payment expires. See Checkout Page Objectexpiration and payment_expiration for more information.

  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 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 presents the bank transfer instructions to the customer via the hosted page.

  7. The customer fails to complete the transfer requirements before the payment expires. Rapyd sends Webhook - Payment Expired. The status of the payment is set to EXP (expired).