Card Payment Message Sequences
When a client requests a card payment, Rapyd Protect immediately performs a fraud check.
The message sequences do not show this initial step.
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 client sends a Create Payment request to Rapyd.
Rapyd sends a response with details of the transaction to the client.
Rapyd sends the Payment Succeeded Webhook to the client.
Rapyd sends a payment request to the card network.
The card network approves the payment request.
Rapyd sends the Payment Completed Webhook to the client. The status of the payment is set to CLO.
Card Payment - Failed
A payment request can fail for many reasons, for example, the card has been blocked.
The client sends a Create Payment request to Rapyd.
Rapyd sends a response with details of the transaction.
Rapyd sends the Payment Succeeded Webhook to the client.
Rapyd sends a payment request to the card network.
The card network rejects the payment request.
Rapyd sends the Payment Failed Webhook to the client. 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.
The client sends a Create Payment request to Rapyd.
Rapyd sends a response with details of the transaction, including the URL of 3DS authentication site. The status of the payment is set to ACT.
Rapyd sends the Payment Succeeded Webhook to the client. The webhook includes the 3DS authentication URL.
The client sends the 3DS authentication URL to the customer.
The customer performs the authentication requirements.
The 3DS authentication site notifies Rapyd that the customer authentication is accepted.
Rapyd sends a payment request to the card network.
The card network approves the payment request.
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.
The client sends a Create Payment request to Rapyd.
Rapyd sends a response with details of the transaction, including the URL of 3DS authentication site. The status of the payment is set to ACT.
Rapyd sends the Payment Succeeded Webhook to the client. The webhook includes the 3DS authentication URL.
The client sends the 3DS authentication URL to the customer.
The customer performs the authentication requirements.
The 3DS authentication site notifies Rapyd that the customer authentication is rejected.
Rapyd sends the Payment Failed Webhook to the client. The status of the payment is set to ERR.