Create one in the dashboard
1
Open Payment Links
Log in to the dashboard and choose
Payment Links in the left sidebar.
2
Name it and set the price
Give the link a name your customer will recognise on the checkout page, then
choose how the amount works:
3
Choose how they can pay
Enable the payment methods you want to accept. Only methods enabled for your
account and currency will appear.
4
Set how many times it can be used
Single use expires after one payment — good for invoices. Limited use
caps it at a number you choose. Multi use stays open until you deactivate
it or it reaches its expiry date.
5
Decide what to collect
Ask for name, email or phone — each one required, optional, or off. Collect
only what you actually need; every extra field costs you completions.
6
Share it
Copy the URL, or download the QR code to print or put on a screen. Both are on
the link’s page in the dashboard.
Link types
After the payment
Each payment against a link becomes a normal deposit on your account, so your payout balance is credited the same way as any other collection. From the link’s page in the dashboard you can:- See every payment made through it, and its status
- Download a PDF receipt for an individual payment
- Deactivate the link to stop accepting payments, and reactivate it later
- Export the transactions
transaction.deposit.status.updated. See Webhooks.
Amounts on these deposits follow the same fee rules as the rest of your account.
Check Fees & Billing before reconciling — the fee
may be added on top of what your customer paid rather than taken out of it.
Creating links from the API
If you need a link per order rather than one you share repeatedly, links can be created programmatically with the same options as the dashboard form — type, pricing, enabled payment methods, usage limit and which customer details to collect. You can also list your links, fetch the payments and totals for one, and deactivate it.These endpoints aren’t in the API reference yet. Ask your account manager for the
current contract rather than working from a path written down here — the reference
is the only place we keep those in step with the API.
Related
- Fees & Billing — who pays the fee, and rounding
- Webhooks & Events — get told about payments automatically