Skip to main content
Send one of these and the sandbox takes the matching path. Send anything else and it takes the ordinary one. These work in sandbox only. In production the same fields carry real data and the values below mean nothing.

Creating a business

The outcome follows from the business’s tax identifier. For a US business that is the ein. Elsewhere it is the nit, rfc, cnpj or tax_id you send in identifying_information. A Colombian business that sends {"type": "nit", "number": "111111111"} takes the same path as a US business that sends ein: "111111111". The values act at two moments. 111111111 decides the business’s verification. The other three leave verification alone, so the business is approved. They decide what happens when you open an account for it.

Paying out

The outcome follows from the cents of the amount, whatever the whole part is. 10.03, 1250.03 and 7.03 all take the same path. What .04 proves is in A payment that is refused after it was accepted.

Depositing

No amount returns a deposit. The cents work as they do on a payout. .02 holds the deposit and then approves it, and .03 holds it and rejects it, so it is never credited. .04 applies only to payouts. Simulate a deposit is the call. The simulated deposit takes the same path as a real bank deposit, described in Deposit. On a fiat account it arrives PENDING and completes once compliance clears it. On a crypto one it settles first. The account has to be on a bank that still opens accounts. One opened earlier on a discontinued bank cannot be credited this way, and the call answers 400. Open a new account on austin_capital_trust or jp_morgan and simulate there.

What these are not

They are not a mode you switch on, and there is no flag that makes the sandbox behave “normally” again. A value either matches one of the rows above or it does not. They are also not a substitute for handling the real thing. A rejection you forced is the same rejection your customer will meet. A rejection you never forced is a branch you have never run.