Skip to main content

Documentation

Card Payment Message Sequences

Create Payment From Card

Card Payment with Automatic Capture - Success

Creates a payment from a card to a Rapyd wallet. Authorization and capture occur simultaneously. The fraud check illustrated here is part of all card payment requests.

  1. The client sends a Create Payment request to Rapyd.

  2. Rapyd requests a fraud check from the card network.

  3. The card network approves the card.

  4. Rapyd requests a payment from the card network.

  5. The card network approves the payment and transfers the funds to Rapyd.

  6. Rapyd sends a response with details of the transaction to the client.

  7. Rapyd sends Payment Succeeded Webhook to the client. The status of the payment is set to CLO.

  8. Rapyd sends Payment Completed Webhook to the client.

Card Payment - Failed

A payment request can fail for many reasons, for example, the card has been blocked.

  1. The client sends a Create Payment request to Rapyd.

  2. Rapyd sends a response with details of the transaction. The status of the payment is set to CLO.

  3. Rapyd sends .

  4. Rapyd requests a payment.

  5. The card network rejects the payment.

  6. Rapyd sends Payment Failed Webhook. The status of the payment is set to ERR.

Card Payment With 3DS Authentication

Card Payment With 3DS Authentication - Success

Some card issuers require 3DS authentication for some transactions.

  1. The client sends a Create Payment request to Rapyd.

  2. Rapyd sends a response with details of the transaction.

  3. Rapyd sends Payment Succeeded Webhook.

  4. The client sends URL of 3DS authentication site.

  5. The customer successfully completes the authentication requirements.

  6. The 3DS authentication site notifies Rapyd that the customer is authenticated.

  7. Rapyd requests a payment.

  8. The card network approves the payment and transfers the funds to Rapyd.

  9. Rapyd sends Payment Completed Webhook. The status of the payment is set to CLO.

Payment With 3DS Verification - Verification Failure

When 3DS authentication fails, the payment fails.

  1. The client sends a Create Payment request to Rapyd.

  2. Rapyd sends a response with details of the transaction. The status of the payment is set to CLO.

  3. Rapyd sends Payment Succeeded Webhook.

  4. The client sends URL of 3DS authentication site.

  5. The customer successfully completes the authentication requirements.

  6. The 3DS authentication site rejects the authentication.

  7. Rapyd sends Payment Failed Webhook. The status of the payment is set to ERR.