Turn a request into a payment route.
Use a secure link when the sale starts in an invoice, message, support conversation or offline workflow rather than a shopping cart.
Payment requestInvoice #SL-2048
Amount and customer context travel with one trackable reference.
Simple on the surface
Built for the operation behind the link.
A payment link should still connect to the right customer, invoice or order. Define expiry, amount behavior, customer fields, status updates and the route for a refund before sharing it.
- Unique merchant and transaction reference
- Fixed or controlled amount behavior
- Expiration and reuse rules
- Authoritative status notification
- Reconciliation and refund trail
Useful where a full cart is unnecessary.
InvoicesRemote ordersSocial sellingAccount balancesDepositsEvent registration
Availability and permitted use depend on merchant underwriting and the approved business model.
Define the first link workflow.
Tell us what triggers the request, which data identifies the sale and how your team confirms payment.