Moving Money
Transfer between your own accounts and create payables that go through your approval rules — all from the API.
The API gives you two ways to move money, matching the Advance dashboard:
- Internal transfers — the dashboard's Move Money between your own accounts. Money moves right away.
- Payables — the dashboard's Payables page. A payable waits for approval in the dashboard and is paid on its
payout date.
Internal transfers
An internal transfer moves money between two of your own Advance accounts, instantly. The source account must have
payouts enabled, and closed or locked accounts can't send money.
A transfer starts as pending and moves to completed once the bank settles it. It can also end as failed,
canceled or returned, with the bank's reason attached. You can look up any transfer, or list them by type,
account or recipient — the list also shows the payouts made from the dashboard.
Payables
A payable is an amount you owe a market, producer or vendor. Payables you create through the API work like those
created in the dashboard, with one difference: a person on your team always approves them before any money moves.
- Create a payable with the payee, amount, description and, if you like, a payout date. Without a date, Advance
uses the payee's payout schedule. - It is submitted for review right away and waits for a team member to approve it in the dashboard — at least one
approval, or more if your approval rules ask for it. Once approved, it is scheduled. - On its payout date, Advance pays it automatically.
To change a payable that's already submitted, revert it, edit it, and submit it again — the same as the dashboard.
Reverting clears its approvals. You can also void a payable that hasn't been paid (see Payables).
A paid payable links to the transfer that paid it, so you can follow it until the bank settles it.
Approval rules
Your approval rules decide how many approvals a payable needs, depending on who it is paid to and whether a person or
Advance created it. You can read your rules through the API and make a rule stricter: require more approvals, lower
the amount above which approval is needed, or stop letting a payable's creator approve it. Relaxing a rule is done by
an admin in the dashboard.
Retrying safely
Every request that moves money or creates a payable needs an idempotency key: a unique value you choose for that
request, such as the ID of the statement you're paying. If a request times out or you aren't sure it went through,
send it again with the same key. Advance returns the original transfer or payable instead of creating a second one.
Use a new key for each new request. If a request was refused (for example, the account didn't have payouts enabled),
fix the problem and retry with the same key. If Advance couldn't confirm whether the bank received a request, it
won't accept a retry with that key. Look up the transfer first, or contact support.
For exact endpoints, fields and error codes, see the API reference and Errors.
Updated 6 days ago
