Create Checkout Message Sequence - Card - 3DS
Diagrams and steps for when 3DS authentication is required for a card transaction via a hosted page.
Some card networks require 3DS authentication for certain transactions.
Success
This diagram shows the sequence of events when the card passes 3DS authentication, and the payment proceeds to successful completion.
The client sends Create Checkout Page request to Rapyd.
Rapyd sends the client a response containing a redirect URL.
The client sends the URL to customer.
The customer completes the checkout page and submits it directly to Rapyd.
Rapyd sends Webhook - Payment Succeeded to the client. The status of the payment is set to ACT (active).
Rapyd sends the URL of the 3DS authentication site to the customer.
The customer completes the authentication requirements.
The 3DS authentication site notifies Rapyd that the customer is authenticated.
Rapyd requests a payment.
The card network approves the payment and transfers the funds to Rapyd.
Rapyd credits the wallet and sends Webhook - Payment Completed to the client. The status of the payment is set to CLO (closed).
Failure
This diagram shows the sequence of events when the card fails 3DS authentication.
The client sends Create Checkout Page request to Rapyd.
Rapyd sends a response containing a redirect URL to the client.
The client sends the URL to the customer.
The customer completes the checkout page and submits it directly to Rapyd.
Rapyd sends Webhook - Payment Succeeded to the client. The status of the payment is set to ACT (active).
Rapyd sends the URL of the 3DS authentication site to the customer.
The customer completes the authentication requirements, but there is a serious error.
The 3DS authentication site rejects the authentication.
Rapyd sends Webhook - Payment Failed. The status of the payment is set to ERR (error).