3DS Flow in Payment Page

Apart from registering for 3DS and having it activated in your Hyp terminal, you as a merchant do not need to take any additional implementation steps to enable 3DS.

The resulting 3DS flow, based on version 2 of the protocol, works as follows:

1. You generate and display a payment page to the customer.

2. The customer enters their credit card details and clicks Pay.

3. Hyp receives the information and initiates a 3DS process with the credit card issuer.

4. If required, the credit card issuer prompts the customer to enter a one-time password (OTP) sent by SMS. The prompt varies by issuer — for example, with Max it looks like this:

   

   3DS prompt from Max
5. The customer enters the OTP, and the credit card issuer informs Hyp whether the challenge succeeded.

6. The credit card issuer's response is validated against the 3DS authentication service.

7. If the challenge succeeds, the transaction is processed normally.

FAQ

Can I customize the graphics of the 3DS screens?

No. The 3DS screens are provided directly by the credit card issuer and cannot be customized by Hyp.

Does the credit card issuer always trigger an OTP challenge?

No. In some cases, the issuer may choose not to show an OTP challenge. Hyp has no control over whether a challenge is displayed.