Payment requests
A payment request is a link you share with a customer (over email, message, or any channel you like) that takes them to a secure hosted page where they can pay. Use this when you want money in without sending a full invoice.
URL: /payment-requests. The page has two modes — Amount and Products — selectable as tabs at the top.
"Share payment links with your customers or clients. They will receive an email or message with a link to pay securely."
Two modes: Amount vs. Products
| Tab | When to use | What you specify |
|---|---|---|
| Amount | Ad-hoc charges where price isn't tied to a fixed item | Just the amount + optional reference |
| Products | Sales of catalog items | One or more products from your catalog (price comes from the product) |
The URL reflects the active tab — /payment-requests/no-products is the Amount tab; the Products tab uses a different sub-route.
Click the Products tab and document its sub-route, the product picker, multi-product support, and discount/quantity handling.
Create a payment request (Amount mode)
The Amount form has these fields:
| Field | Required | Notes |
|---|---|---|
| Payment amount | yes | Numeric input. Placeholder € 0.00. Currency follows the account default. |
| Customer reference | no | Free text. Placeholder: "Invoice, purchase order, booking number, …". Surfaces on the resulting transaction so you can reconcile. |
| Your request will expire on | yes | Date + time picker. Defaults to 7 days from now at the current time (e.g., 15/05/2026 @11:20 am). |
| Stored Card Mode | toggle | Optional. (See "Stored Card Mode" below.) |
| Pre-Authorisation | toggle | Optional. (See "Pre-Authorisation" below.) |
There's also an expandable Additional security settings section under the main form for further controls.
Click the section to expand and document each setting — likely fields like 3DS enforcement, max attempts, allowed methods.
Once filled in, click Create payment to generate the link.
What does the next screen show? URL to copy, QR code, "send by email" affordance, list of recently created links?
Stored Card Mode
A toggle on the form. When enabled, the payment link captures the customer's card on file rather than (or in addition to) charging immediately — typically used to set up the customer for future charges.
Does it tokenize the card without charging, or charge + tokenize? When does the merchant see the saved card afterwards?
Pre-Authorisation
A toggle on the form. When enabled, the payment is authorised (a hold) rather than immediately captured — useful when the final amount isn't known at request time (e.g., bookings, hospitality).
After the customer authorises, where does the merchant capture the final amount? Document that flow.
Lifecycle of a payment request
- Create — fill in the form and click Create payment.
- Share — send the link to your customer.
- Pay — customer opens the link and pays through the hosted page.
- Reconcile — the resulting payment lands in Transactions; the customer reference you set is shown on the row.
- Expire — if unpaid by the expiry date, the link stops accepting payments.
Is there a list of previously created links somewhere (status: pending / paid / expired, with re-share and revoke actions)? Find it and add a section here.
Related
- Invoices — for full structured billing rather than a simple link.
- Transactions — where successful payments land.