Testing in Sandbox

Overview

The sandbox environment lets you exercise the full API without moving real funds:

https://app2test.infiniaweb.com/infinia_api/v1

Sandbox credentials are separate from production credentials — see Authentication for details.

To make testing deterministic, the sandbox supports magic values: specific amounts that trigger a predefined outcome. Any amount not listed below results in the default (successful) behavior.

---

Accounts

Account creation is currently synchronous: the account's status is returned directly in the Create Account response. By default, accounts created in the sandbox are ACTIVE immediately. To test how your integration handles the other account statuses, create the account with one of these magic label values — the account is created directly in that status:

No status webhook is sent in these cases: the account starts in that status rather than transitioning into it.

To test status transitions and your status_callback_url receiver, create the account with the label SIMULATE_PROVISIONING_FLOW: it is created as PROVISIONING and automatically transitions to ACTIVE a few seconds later, firing the status change webhook.

---

Deposits

Use the [Sandbox] Create Deposit endpoint to simulate incoming funds on a virtual account. This endpoint only exists in the sandbox.

These amounts work on sandbox accounts in any country. The simulated third-party payer document is always in Brazilian format (CPF/CNPJ); in production, the payer document reflects the sender's jurisdiction (for example, RFC in Mexico).

---

Payouts

In the sandbox, payouts are executed against a mock provider. Use these amounts to simulate each lifecycle outcome:

---

Internal Transfers

Internal transfers succeed in the sandbox by default, so a successful transfer needs no magic value. Use these amounts to reach the failure branches, which the sandbox never produces on its own:

The numbering is deliberately parallel to the payout amounts above: 302 behaves like 202 and 303 like 203.

The rejection comes from the same simulated rail that would settle the transfer, so the failure is the real one, not a shortcut: the transfer is quoted (for cross-currency transfers), the funds are debited and then given back. That means:

• The source account must be funded: if it cannot cover the amount, the transfer fails with the usual insufficient-funds reason instead, exactly as it would for any other amount.
• Both legs show up in List Account Movements, with operation.type INTERNAL_TRANSFER and then INTERNAL_TRANSFER_REFUND sharing the transfer's operation.operation_id. The refund leaves the balance exactly where it started.
• The refund can land a few seconds after the transfer is reported FAILED, so read the balance after the refund movement appears rather than immediately.

---

Bank Account Validation

In the sandbox, this product returns pre-defined responses, so you can test your request and response handling end to end without hitting real registries. Use the values below to trigger each outcome. Unless noted otherwise, any input not listed leaves the validation in IN_PROGRESS.

Argentina

For QR_CODE validations, these payloads return SUCCESSFUL; any other QR code returns ERROR:

• Closed QR (holder JUAN CARLOS LOPEZ, CUIL 20123456789, amount 5000):

  00020101021243650016com.mercadolibre340130636f0f8b322-550d-3b3d-56b0-68d537d0997850150011273805090705204970053030325802AR5914John Doe      6004CABA6304ACF9

• Open QR (holder MARIA GARCIA, CUIL 27123456789, no amount):

  00020101021243650016com.mercadolibre340130636f0f4b421-310d-3b3d-46c1-48f542f0493850150011273805090705204970053030325802AR5914John Doe      6004CABA63041924

Brazil

Colombia

Mexico

Uruguay

United States

---

Identity Validation

In the sandbox, this product returns pre-defined responses too. Use these document numbers to get a SUCCESSFUL validation with pre-defined identity data. Any other document number results in a FAILED validation with an empty response.

Identity validations resolve synchronously in the sandbox: the final status is available immediately, and if you provide a callback_url the callback is sent right away.