3DSecure2
Test your integration
ON THIS PAGE
- Test your integration
- Test credentials
- 3DS 2 Test cards
- Sample scenarios: /3ds2/lookup
- Lookup Scenario 1: Account number supports EMV 3DS 2 and is available in Elavon's bin database, an internal repository
- Lookup Scenario 2: Account number supports EMV 3DS 2, but is not available in Elavon's bin database, an internal repository
- Lookup Scenario 3: Account number does not support EMV 3DS 2, but is available in Elavon's bin database, an internal repository
- Lookup Scenario 4: Account number does not support EMV 3DS 2 and is also not available in Elavon's bin database, an internal repository
- Authentication scenarios
- Authentication Scenario 1: Challenge flow - Issuer requires a cardholder challenge to complete authentication i.e.,
- Authentication Scenario 2: Frictionless flow - cardholder authenticated i.e.,
- Authentication Scenario 3: Cardholder doesn't get authenticated, but a proof of authentication attempt (an
- Authentication Scenario 5: Cardholder doesn't get authenticated i.e.,
- Authentication Scenario 6: Cardholder doesn't get authenticated, as authentication could not be performed due to technical or other issue i.e.,
- Authentication Scenario 7: Cardholder doesn't get authenticated because the issuer is rejecting authentication and requesting that authorization not be attempted i.e.
- Authentication Scenario 8: Merchant sent the request only for informational purposes and did not need a challenge i.e.