This sample page simulates the flow in which the users will type their card information for each payment, so you don't need to tokenize anything. However, your customer may have to type it all again when making further payments.

Instructions

1. If you are working on a production environment, change the merchant_id variables on the selectCurrency function to the respective value, as the default value is for sandbox testing. Also look for the proper 'fxapi_url' variable.
2. Enter your Portal/API credentials below and click the button to login
3. With the correct credentials, all customers and bank accounts you have registered that are compatible with the flow will be loaded
4. Choose both IDs for the transaction parameters
• Make sure the selected subject has all the mandatory info for 3DS (check in the documentation)
• Make sure the selected bank account is an internal cash-in or physical USD account
5. Insert the test credit card number; for test purposes, all other information can be randomly generated
6. Enter a value for the transaction and click on Pay. The minumum amount for the OTP validation is 1001.00.
7. If the correct challenge test card is used, a pop-up modal will appear. This indicates that the 3DS worked and represents the OTP code your customer will receive on a real purchase. Enter '1234' to validate it. This confirmation must be done within 5 minutes.
8. You should now have an identified or wired transaction, depending on the response

• If anything goes wrong, the transaction will be canceled and the error may be displayed
• The transaction may also be approved without the challenge step if the proper card is used
• We recommend disabling any ad blocker extensions for the anti-fraud scripts to work