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.

Deposits

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

`amount`	Behavior
`101`	Creates a deposit whose refund will fail: the refund is initially reported as `SUCCESS`, then a callback with `status = FAILED` is sent. Use it to test the Refund Deposit failure flow.
`102`	Creates a deposit that includes third-party payer data with an individual document (CPF).
`103`	Creates a deposit that includes third-party payer data with a business document (CNPJ).
`104`	Creates a deposit that includes crypto metadata (sender address, network, and transaction hash).
Any other amount	Creates a standard completed deposit.

Payouts

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

`amount`	Behavior
`99997`	The payout is accepted as `IN_PROGRESS` and later transitions to completed. Use it to test the asynchronous happy path, including the status webhook.
`99998`	The payout is accepted as `IN_PROGRESS` and later transitions to failed, with an error callback. Use it to test asynchronous failures.
`99999`	The payout fails immediately with an error response.
Any other amount	The payout completes immediately.

📘
In production, a payout that is IN_PROGRESS may still fail (for example, if the destination account is closed). Once a payout reaches COMPLETED, it can only transition to REFUNDED or PARTIALLY_REFUNDED, when the rail supports refunds. We recommend building your integration against the asynchronous scenarios (99997 and 99998) rather than relying on immediate completion.

Bank Account Validation and Identity Validation

In the sandbox, these products run against mock providers that return successful, pre-defined responses, so you can test your request and response handling end to end without hitting real registries.

Notes

Magic values only work in the sandbox environment; in production they are treated as regular amounts.
Sandbox data is isolated from production and may be purged periodically.