Apply deposit to invoice
Puts the deposit against one of your invoices.
- Paid: the payment is applied to the invoice now.
200, andappliedis true. - Processing: a bank debit the customer has confirmed and that has not landed
yet, which takes 2 to 4 business days. The deposit is queued against the
invoice and applied automatically when the money arrives.
202, withapply_to_invoice_uuidset andappliedstill false until then.
Any other status has collected nothing and is refused.
While queued, the invoice lists the deposit as a pending payment, and automatic card or bank charges on the invoice take it into account, so the customer is not charged again for money already on its way. Nothing is credited to the invoice until the money lands: a bank debit can still be returned. If it is, the queue is dropped with it and the link reopens.
A deposit larger than the invoice is applied in full, and the remainder stays as credit on that invoice, the same as any overpayment.
Safe to retry: applying a deposit to the invoice it is already applied or queued to returns the same result.
Authorizations
App ID for authentication
API Key for authentication
Path Parameters
Body
The invoice to apply the deposit to. It must belong to the same customer as the deposit, be in the same currency, and not be voided.
Response
Applied. Returns the link with applied true.
A request for money from a customer before any invoice exists.
The customer pays the URL by card or bank debit. The money lands as an unapplied
payment and posts to no accounting system until someone applies it to an invoice,
at which point applied turns true.
Identifies the link everywhere in this API.
Where the link is in its life.
processing means a bank debit was taken and is still settling, 2 to 4 business
days. The money has not arrived; it becomes paid on its own.
failed is terminal. The customer cannot retry the same link and you issue a new one.
A lapsed link reports expired even before the sweeper rewrites it, so this always
agrees with whether the URL still works.
open, processing, paid, failed, expired, canceled, refunded Amount requested, in cents.
Currency to collect in. Defaults to the customer's, then the company's, then USD.
Narrower than the currencies elsewhere in this API: a deposit must be payable by card or bank debit, and every one of these is two-decimal.
USD, CAD, EUR, GBP, AUD The payable URL. Always present and always works.
Shortened form of the same URL. Null when the shortener was unreachable at
creation, so fall back to url rather than treating null as an error.
Shown to the payer.
Your own reference.
Whether the money has been applied to an invoice.
Separate from status, and not a problem state: paid with applied: false is
where a deposit sits until someone maps it to an invoice. When the deposit was
collected the invoice did not exist, so nothing picks one on its own. Apply it with
PUT /deposit_links/{uuid}/invoice, or in the Streamlined app.
The invoice a processing deposit is queued against, via
PUT /deposit_links/{uuid}/invoice. It is applied there when the money lands, at
which point this goes null and applied turns true. Null when nothing is queued.
The money that settled this link. Null until it has been paid.