3/27/2023 0 Comments Simulator status magicTo test how different Real Time Account Updater scenarios work for your integration, use the following test card numbers in your payments request. Refer to the list of the avsResult values you can receive. Use the following shopper details to test AVS: Card Number Depending on your configuration, the transaction might still proceed to a successful authorization. This test card simulates a timeout during the 3D Secure 2 authentication flow on the issuer side. The card is not enrolled for 3D Secure transactions. To test different authentication scenarios for app-based integration, use the following test cards: Card numberĪpp single select then text authentication To test the frictionless flow, in which you perform a fingerprint but no challenge, use the following test card number: Card number To test the web-based flow where the device fingerprinting step is skipped (because the issuer's ACS has not configured a threeDSMethodURL), and you get a ChallengeShopper resultCode immediately after submitting the payment request, use the following card: Card Type ChallengeShopper: You will get this result code after you submit the 3D Secure 2 device fingerprinting result in a Native authentication, unless you specify a frictionless flow.IdentifyShopper: You'll receive this result code if you are using the Native authentication.RedirectShopper: You'll receive this result code if you are using the Redirect authentication.When you make a payment request with these cards, you'll receive the following result codes depending on your integration: For web and mobile browser integrations, use password: password.For native mobile integrations, use password: 1234.When prompted for 3D Secure 2 text challenges, use the following credentials: To test how your integration handles different 3D Secure 2 authentication scenarios, use our test card numbers. You can either set your default dynamic 3D Secure rule to Always or force 3D Secure by passing authenticationData.attemptAuthentication in your API request. If your default dynamic 3D Secure rule is set to Prefer Not, then the following test cards will not trigger 3D Secure. Cartes Bancaires Card NumberĮxpressPay Credit Card ( cup) Card Numberįor online Maestro payments, 3D Secure is mandatory. American Express (Amex) Card Numberġ Depending on your payment method setup, transactions with this test card are routed to Bancontact or Visa. To test how your integration responds to other payment scenarios, such as refused or invalid payments, see Result code testing. When you make a test payment with these card details you'll receive a resultCode of Authorised. These are tagged with security code optional. Some test cards do not require a security code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |