Test Your Integration

You can test your integration for 3DS Authentication via the gateway by using the 3DS Emulator. To access the emulator, use your test merchant profile (type "TEST" as a prefix to the Merchant ID supplied by your payment service provider).

The test cards provide a range of gateway results for the various 3DS scenarios but do not necessarily emulate ACS behavior.

Testing is supported for the following 3DS schemes:

  • Mastercard SecureCode
  • Verified by Visa
  • American Express
  • Discover
  • Maestro
  • JCB
  • Diners
  • ITMX Local Switching Secure EMVCo
Details

To test 3DS functionality:

  1. Use a test card (from the following table) when submitting the Initiate Authentication request for your TEST merchant profile.
  2. Use the expiry code "01/39" to get a successful authorization/payment in an end-to-end testing flow. Please note that the card(s) listed with * will not work for subsequent authorizations or payments.
  3. Check that the authentication is available (authentication.version=3DS2 or 3DS1)
  4. Submit an Authenticate Payer request and insert content of the authentication.redirect.html field into the page displayed to the payer to redirect the payer's browser to the 3DS Emulator challenge page.
    The 3DS Emulator redirects the payer's browser back to your website once the authentication is complete.
  5. Select a specific 3DS authentication result via drop-down selection in the 3DS Emulator (see values in the following table).
  6. Use the transaction ID for this 3DS authentication in authentication.transactionId in a subsequent Authorize or Pay transaction request. It should indicate only where authentication is successful and if the card allows for subsequent authorization or payment.
Test Cards Purpose Card Number 3DS1 Enrolled 3DS2 Enrolled Method URL tranStatus

authentication.3ds2.transactionStatus

 tranStatusReason

authentication.3ds2.statusReasonCode

 ECI Authentication Token
Mastercard 3DS2 - Challenge (Method URL provided) 5123450000000008
2223000000000007		 Yes Yes

 Yes

 C - - -
3DS2 - Frictionless (Method URL provided) 5123456789012346 Yes Yes Yes Y - 02 mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Frictionless (No Method URL) 5555555555000018* Yes Yes No Y - 02 mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Authentication Attempted 5500005555555559 Yes Yes No A - 01 nHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Authentication Rejected 5506900140100503 No Yes No R 04 - -
3DS1 - Not enrolled for 3DS2 resulting in fallback to 3DS1 5506900140100305 Yes No No - - - -
3DS2 - Error during Initiate Authentication operation resulting in Generic Error Response 5210760000000004 Yes Exception - - - - -
3DS2 - Error during Authenticate Payer operation resulting in Generic Error Response 5455031257390496 Yes Yes No Exception - - -
5455031252665454 Yes Yes No Exception - - -
3DS1 & 3DS2 - Not Enrolled Response 5111111111111118 No No - - - - -
2223000000000023 No No - - - - -
3DS2 - Authentication Unavailable Error during Authenticate Payer operation resulting in a response of authenticationStatus = AUTHENTICATION_UNAVAILABLE 5123459999998221 Yes Yes No Recoverable Exception - - -
Visa 3DS2 - Challenge (No Method URL) 4440000009900010  Yes Yes No C - - -
3DS2 - Frictionless (Method URL provided) 4440000042200014 Yes Yes Yes Yes - 05 mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Authentication Attempted 4440000042200022  No Yes No A - 06 nHyn+7YFi1EUAREAAAAvNUe6Hv8=
American Express 3DS2 - Challenge (No Method URL) 340000099900051 No Yes No C - - -
3DS2 - Frictionless (Method URL provided) 340353278080900 Yes Yes Yes Yes - 05 mHyn+7YFi1EUAREAAAAvNUe6Hv8=
Maestro PSD2 Exemptions and Trusted Merchants 5000000000000000005 Yes Yes No No 81 06 kNyn+7YFi1EUAREAAAAvNUe6Hv8=
JCB 3DS2 - Challenge (Method URL provided) 3528249999991755 Yes Yes Yes C - - -
3DS2 - Challenge (No Method URL) 3528249999991748 Yes Yes No C - - -
3DS2 - Frictionless (Method URL provided) 3528249999991821 Yes Yes Yes Yes - 05 mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Authentication Rejected 3528249999981236 Yes Yes Yes R - - -
3DS1 - Not enrolled for 3DS2 resulting in fallback to 3DS1 3528000000000007 Yes No No - - - -
3DS1 & 3DS2 - Not Enrolled Response 3528249999991953 - - - - - - -
Diners 3DS2 - Challenge (Method URL provided) 3600000000000115 Yes Yes Yes C - - -
3DS2 - Challenge (No Method URL) 3600000000000123 Yes Yes No C - - mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Frictionless (Method URL provided) 3600000000000131 Yes Yes Yes Yes - 05 mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Authentication Rejected 3600000000000172 Yes Yes Yes R - - -
3DS1 - Not enrolled for 3DS2 resulting in fallback to 3DS1 3600000000000180 Yes No No - - - -
3DS1 & 3DS2 - Not Enrolled Response 3600000000000222 - - - - - - -
Discover 3DS2 - Challenge (Method URL provided) 6445644564456445 Yes Yes Yes C - - -
3DS2 - Challenge (No Method URL) 6445644564456460 Yes Yes No C - - mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Frictionless (Method URL provided) 6445644564456411 Yes Yes Yes Yes - 05 mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Authentication Rejected 6445644564456155 Yes Yes Yes R - - -
3DS1 - Not enrolled for 3DS2 resulting in fallback to 3DS1 6445644564456163 Yes No No - - - -
3DS1 & 3DS2 - Not Enrolled Response 6445644564456239 - - - - - - -
MASTERCARD_ITMX 3DS2 - Frictionless 5594509999999006 Y Y Yes Y - - mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Challenge 5297649999999000 Y Y No C - - -
3DS2 - Authentication Attempted 5391979999999048 Y Y No A - - mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Not Authenticated 5391979999999055 Y Y No N 04 - -
Mastercard ITMX 3DSV1 and 3DSV2 Frictionless V220 5391979999999014 Y Y No Y - - mHyn+7YFi1EUAREAAAAvNUe6Hv8=
VISA_ITMX 3DS2 - Frictionless 4215849999999008 Y Y No Y - - mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Challenge 4943129999999004 Y Y No C - - -
3DS2 - Authentication Attempted 4013679999999045 Y Y No A - - mHyn+7YFi1EUAREAAAAvNUe6Hv8=
3DS2 - Not Authenticated 4013679999999052 Y Y No N 04 - -
Visa ITMX 3DSV1 and 3DSV2 Frictionless V220 4013679999999011 Y Y No Y - - mHyn+7YFi1EUAREAAAAvNUe6Hv8=

In the case of a "C" transStatus, the following outcomes are possible via drop-down selection in the 3DS Emulator:

Description transStatus challengeCancel eci
Successful authentication
 Y - 05 / 02
Failed authentication
 N - 07 / 00
Cancelled authentication
 N 01 07 / 00
Unable to authenticate U - 07 / 00
Authentication rejected R - 07 / 00
What to do when I receive a particular 3DS Error codes?

The gateway is enhanced to return error messages from the authentication servers. These can be used to help you identify which fields may be causing your integration to break when an authentication request is sent.

This table describes sample error message and error cause.

Error Message Error Cause
The authentication scheme has indicated that you have not been onboarded with the authentication scheme for EMV 3DS by your acquirer. Please contact your acquirer or payment service provider. Before you can start using the EMV 3DS functionality, you may need to be onboarded with the respective authentication scheme by your acquirer. Please contact your acquirer or payment service provider to get these values checked.

Please note that you will need a mastercard developer account.

What should I do when there is a delay while searching for orders or transactions within the Merchant Administrator portal?

If you use the Authentication API, you can see the authentication details on the Merchant Administrator portal when the payer authentication is complete. If the payer authentication is not yet complete, you may experience a delay in the authentication transaction that displays when searching for an order or transaction on the Merchant Administrator portal. For example, going through a challenge flow.

In the meantime, you can retrieve the current state of the authentication using the Retrieve Order or Retrieve Transaction operation.

Retrieve Order API Reference [REST][NVP]

Retrieve Transaction API Reference [REST][NVP]

Copyright © 2023 Suncorp