Payment and Subscription Intents

We provide a sandbox so that you can try the Payment Intent or Subscription Intent flow without really having to execute any real transaction, helping you integrate easily and knowing every flow that your users might follow. Using it is easy, just integrate to the product as you would normally, while using the test Secret and Public Keys instead of using the real ones.

Configurations

The bank transfer process has two additional steps (other than the login step) that require the user to enter information: MFA (multi-factor authentication) to add a new contact to their contact list when the recipient isn't registered and MFA to confirm the bank transfer. Every bank works differently, some may ask for the MFA to add a new contact while others may not, but in the sandbox we allow you to try every possible combination so that you can feel the flow that your users will follow and test the integration.

Available MFA types

These are the different MFA that we have available within the sandbox:

  • Security device: electronic device that banks give their clients to authorize transactions. They generally show a number that changes after some time.
  • Mobile application: banks offer to authorize transactions through their mobile apps. In this case, the user must authorize the transaction from their smartphone and we will detect that the transaction was authorized automatically. In the sandbox, we allow you to simulate successful and failed authorizations. The failed authorization will simulate the user rejecting the transaction.
  • SMS: the bank sends a code (generally a numeric code) to the user's phone so that it can be used to authorize the transaction
  • Coordinate card: card that banks give their clients with a table with numbers. The user must insert the numbers located at the coordinates asked by the bank. You can read more about coordinate cards here.

MFA to simulate a new contact (Payments only)

For Payment Intents, the user might need to add the recipients account before confirming the transaction. If you want the widget to ask for some kind of MFA that simulates that the user needs to add the recipient account of the Payment Intent as a new contact, you should use specific last digits for the amount attribute of the Payment Intent. For example, if you create a Payment Intent with an amount of 15001, the user will be asked to authorize the new contact using its Security device. You can see the list of specific digit combinations indicating what type of MFA corresponds to which last digits of the amount and which code to introduce. Introducing a different code will result in a failure of the authorization:

Last digits of the amount

MFA type

Example

Correct code

01

Security device

amount: 10701

0000

02

Mobile Application - Success

amount: 10702

Does not apply

03

Mobile Application - Failure

amount: 10703

Does not apply

04

SMS

amount: 10704

000000

05

Coordinate Card

amount: 17505

['00', '00', '00']

If the amount of the Payment Intent doesn't end with any of the previous digits, the user won't be required MFA to create a new contact and will go directly to confirming the bank transfer.

MFA to confirmate operation

This step is required on every bank, so the sandbox won't allow you to skip it. You can also personalize it, choosing a specific origin bank account when the widget asks you to choose one. The sandbox environment will always show the same accounts.

Here's a list of the sandbox accounts and which type of MFA corresponds to all of them, along with the correct code to enter.

Account number

Type of MFA

Correct code

813990168

Security device

000000

422159212

Mobile Application - Success

Doesn't apply

5233137377

Mobile Application - Failure

Doesn't apply

170086177

SMS

0000

746326042

Coordinate Card

['00', '00', '00']

default

Coordinate Card

['00', '00', '00']


Did this page help you?