Skip to main content

Testing your integration

The credit card numbers to be used in the test can be generated from any card generator site, and the behavior must follow the following rule:

Credit cardAuthorized?Status
Final 0, 1 ou 4YESAuthorized
Final 2NONot Authorized
Final 3NOCard expired
Final 5NOCard bloqued
Final 6NOTimeout
Final 7NOCard canceled
Final 8RANDOM YES/NOAuthorized / Timeout

Transactions in the sandbox environment involving tokenization normally work on test cards. Each card saved during the tokenization process is treated as a normal card and can be used in the simulation process.

The Security Code (CVV) information respects the following sandbox validation rule, for a CVV ending in zero "0" the card is validated, for any other value the status returns as not validated.

If you have managed to insert the credit card data into your client application, create a token, send the data to your server, and create a charge, then your integration is finished.


If you want to test anti-fraud scenarios, the value analyzed in the sandbox will be the end of the document sent in the anti-fraud node (fraudAnalysis) when creating the transaction. The status returned for anti-fraud will follow the rules set out in the table below:

DocumentStatusDeclined Code
Final 0PendingNull
Final 1ApprovedNull
Final 2FailRandom timeout ou processing_error
Any other valueRepprovedNull