What advances it
What announces it
The account’s own events are in Account opening. These are the deposit’s:
A deposit is announced once compliance approves it. Its
virtual_account.deposit_funds_received arrives with status completed for a bank transfer to a fiat account, and pending when the deposit still has to settle: on a crypto account, or for stablecoins being converted. Its created_at is when the money arrived, not when it was approved. A bank deposit compliance rejects sends no notice; a crypto inbound sends virtual_account.deposit_funds_failed.
virtual_account.deposit_funds_received is the rail-independent signal. Balance behaviour is not uniform across rails, so an integration that watches the balance instead will work on one rail and quietly fail on another.
Corridors
A bank deposit to a fiat account has no settlement step. It waits in
pending until compliance clears it. A crypto one starts pending and the settlement pipeline advances it.Where an RFI interrupts it
A compliance check on a deposit can raise a request for information against it. While the request is open, the deposit reportsstatus of NEEDS_ACTION and does not advance. It continues from the same stage when the request closes. A request about the sub-client holds their verification instead and leaves the deposit alone. Both raise the same events.
Making one arrive in sandbox
You do not have to wait for a real payer. Simulate a deposit credits the account for real and fires the same webhooks a real deposit does, which is what makes it worth testing against. It exists in sandbox only. It works on accounts on a bank that still opens accounts; one on a discontinued bank answers409.
A simulated deposit is a bank transfer. A crypto inbound cannot be tested in sandbox yet.
Payout
Money leaving, to a counterparty you saved.