Pāriet uz galveno saturu

Testing 3DS Authentication in the Demo Environment

How to simulate different 3DS authentication outcomes when making test payments

Atjaunināts pirms vairāk nekā mēneša

Test Scenarios for 3DS Authentication

You can trigger both positive and negative authentication outcomes using test cards in the demo environment.


✅ Positive Scenarios

  1. Yes

    • The customer successfully completes 3DS authentication (e.g. enters correct PIN2 or equivalent).

    • Strong customer authentication status: 3DS

  2. Attempt

    • 3DS authentication was initiated, but the card issuer chose not to enforce it.

    • Strong customer authentication status: 3DS Attempted


❌ Negative Scenarios

  1. No

    • The customer fails 3DS authentication (e.g. enters incorrect PIN2 or equivalent).

    • Strong customer authentication status: 3DS Declined

  2. Rejected

    • The 3DS request was explicitly rejected by the card issuer.

    • Strong customer authentication status: 3DS Declined

  3. Unavailable

    • A technical issue prevented the 3DS process from completing.

    • Strong customer authentication status: 3DS Failed


Use these scenarios to verify your system's handling of successful, bypassed, failed, and technically failed 3DS authentication attempts.

Vai saņēmāt atbildi uz savu jautājumu?