Browse wiki · Reusable payment links

Reusable payment links

Reusable payment addresses

Publish a stable address in the Reusable payment links section below Invoice history. Use an existing invoice as the starting point. Link management is free; any new invoice costs creation credits and reserves its success fee.

One payer per cycle

The link points to one existing invoice. After it is paid, cancelled or expired, publish the next invoice to the same address. All visitors share that invoice. Opening the link does not spend credits or extend its expiry. An invoice being verified cannot be replaced.

Separate invoice per buyer

Select Separate invoice per buyer and set a lifetime creation budget of 1–10,000 credits and a limit of 1–20 active buyer invoices. The selected invoice supplies the fixed amount, recipient, description and payment window. Its own payment is separate; selecting it as a template does not create another charge or cancel it.

Visitors see a Continue to payment button. Clicking it creates a separate invoice. The browser reuses its session key after a retry; concurrent requests with that key do not charge twice. Creation credits count toward the link budget even if the invoice is never paid. Success fees reserve additional available credits and are outside the creation budget. A link can create at most 1,000 buyer invoices in total. The amount and recipient template cannot be changed after publication; create a different link for different terms.

Public creation is limited per IP and per link. These limits reduce abuse but do not identify real buyers: someone with the link can consume its explicitly enabled creation budget. Start with a small budget. Pausing stops new buyer invoices; already-issued checkouts remain payable. Cancel individual invoices separately if needed. New sessions stop after an operator pricing change until you publish the link again with the current terms. Existing invoices retain their original terms.

Merchant API

GET {API_BASE}/payment-links requires invoices:read. PUT {API_BASE}/payment-links/{id} requires invoices:create. Choose a random UUID as the ID. The key's receiving wallet must match the template invoice. There are at most 25 links per workspace.

{
  "name": "Service payment",
  "invoiceId": "YOUR_INVOICE_ID",
  "enabled": true,
  "revision": 0,
  "mode": "sessions",
  "budgetCredits": 10,
  "maxActive": 3
}

For one payer per cycle, omit mode and the two limits. For changes, send the last returned revision; conflicting updates return HTTP 409. Used credits and created-session counts are cumulative and cannot be reset by republishing. Do not share your merchant API key with buyers.

The public address is {WORKSPACE_BASE}/l/{id}. In buyer mode, its page calls POST /l/{id}/sessions with a persistent random Idempotency-Key and a same-origin request. This returns the individual checkout URL. The public endpoint cannot choose a different amount or recipient. A reusable address is not proof of payment: reconcile each individual invoice and receipt.

Scheduled invoices are available in Invoices → Scheduled invoices. Automatic wallet debits are not supported. Goods and fulfillment stay in the seller's system.

← All topics