The limits this business is subject to
Being refused by a limit nobody will show you is not a control, it is an outage. Setting them is not a business action — they are ours. Pass `currency` to get the whole picture: the tier's own ceiling is derived per currency rather than stored, so without one this can only return the rows an operator has written, and a business would be held to a limit this endpoint never mentioned.
Being refused by a limit nobody will show you is not a control, it is an outage. Setting them is not a business action — they are ours.
Pass currency to get the whole picture: the tier's own ceiling is
derived per currency rather than stored, so without one this can only
return the rows an operator has written, and a business would be held to
a limit this endpoint never mentioned.
Authorization
OAuth2PasswordBearer In: header
Query Parameters
Cookie Parameters
Response Body
application/json
application/json
curl -X GET "https://example.com/api/b/v1/payouts/limits"{ "limits": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "label": "string", "scope": "string", "limit_window": "string", "currency": "string", "max_amount_minor": 0, "max_count": 0, "used_minor": 250000, "remaining_minor": 950000 } ]}How this payout got to where it is GET
Every transition in order, with timestamps and who caused each — E6-10. Ordered by when the event was written rather than by status, because a lifecycle read back in the order the code happens to define is not a record of what occurred.
Quote the fee on a payout GET
InversePay's fee on a payout, from your plan, before you send it. Priced exactly as the payout itself will be, so the quote is the fee. It is added on top, so the recipient receives `amount_minor` in full and `total_minor` leaves your balance. If you charge your own customers for sending money - a payroll run, a transfer - this is your cost per payout. What you charge them on top of it is your margin. A batch is priced line by line in the same way when its file is checked.