Record Payment
POST/api/vendor-deposits/:vendorDepositId/payments
Record a payment against a vendor deposit (full or partial), with the payment date, currency rate, and optional reference.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Payments can also be recorded on a draft deposit — useful for capturing a payment that was already made in the past. The deposit then moves directly to Partially Paid / Paid without a payment request or approval step.
The payment amount cannot exceed the deposit's outstanding balance (deposit amount minus payments already recorded). Deposits whose payee bank details differ from the supplier profile must have those details verified before payments can be recorded. Payments cannot be recorded against cancelled, void, refunded, or written-off deposits.
Approval policy:
While the vendor-deposit approval policy is enabled a payment can be recorded only on an approved deposit — 422 approval_pending while its request awaits approval, approval_required when none was approved.
Request
Responses
- 401
- 403
- 404
- 422
- 429
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.