Payment transactions through a payment link send no webhook events, so step 4 polls.
1. Create the Link
status: active, its checkout page and a qr_code of the page’s URL, usable in a plain <img>.
typeissingle_use, which is paid once, orreusable.expires_atdefaults to 7 days from now, and can be from 60 seconds to 1 year ahead.success_urlandfailure_urlare optional, as a pair.- Without
is_test: true, the link is live, which answers 409LIVE_PAYMENTS_NOT_ALLOWEDfor a merchant that isn’t live yet. - Make one
Idempotency-Keyfor each link you mean to send, and store it with the invoice or order before you send the request. A retry with a new key makes a second link, which a customer can also pay. See Idempotency.
checkout and qr_code can be read again while the link is open, so you can print or resend them. Treat them as secrets all the same: anyone holding the URL can pay.
2. Send the Link
Sendcheckout.url to the customer, by email or message, or show the QR code.
3. The Customer Pays
The customer opens the link, gives their details, chooses their bank and pays. Customer.4. List the Link’s Payment Transactions
is_test=true. Each payment transaction carries the link’s order.
5. Read the Link
view_count and first_viewed_at say whether the customer has opened the page.