Practical guide · Payment links
A payment link starts with a clear request.
A hosted payment link gives a customer a place to pay an invoice. The useful work starts before you share it: agree what is being paid for, check the payment setup, and decide how your team will confirm the outcome.
Before you share the link
Confirm the customer, invoice details, amount, and payment currency. Keep your invoice reference connected to your own order or service record so your team can identify the request later.
- Describe the goods or service clearly and check the amount with the customer.
- Confirm the payment methods enabled for your account and intended workflow.
- Decide who will answer questions and how you will communicate a changed or cancelled request.
- Review account eligibility, pricing, and payout terms separately from the invoice.
An illustrative workflow
A service business agrees the scope of a project with a customer. It creates an invoice, shares the hosted payment link through its usual customer conversation, and reviews the resulting payment activity before marking the order paid. This is an example workflow, not a claim about a particular merchant.
- Create the request. Use the supported invoice workflow in your integration; consult the documentation for the actual operations and credentials.
- Check the checkout. In sandbox, test the same hosted document you intend to share, including a successful and an unsuccessful payment.
- Share with context. Include your business identity, the invoice reference, and a way to contact you. Do not ask customers to send card details by message.
- Confirm the record. Review the payment status in merchant records. A customer opening a link is not evidence that payment completed.
Make the handoff reliable
Where enabled, Apple Pay and Google Pay depend on the account, domain, browser, and device. Check the customer devices and payment methods you expect to support before inviting a live payment.
If you use HTTPS webhooks, connect updates to the correct invoice or order and test your handling of repeated notifications. Keep the merchant workspace available for your team to review activity and receipt records.
A successful payment does not establish when funds will reach your payout destination. Use the payout timing checklist to plan that separately.
Common questions
Does a payment link replace my website?
It can provide a direct way to pay an invoice alongside your existing sales process. Your customer still needs clear information about what they are buying and how to reach your business.
Can every customer use a digital wallet?
No. Wallet availability depends on the enabled payment method, account and domain setup, browser, and device. Confirm the methods for your workflow before sharing links.
How should I confirm that an invoice is paid?
Use the payment status in the merchant workspace or the relevant merchant API records and supported notifications. Do not treat a link click or a customer message as a successful payment record.
Turn the plan into a setup.
Explore SecurePayAPI online payments and pricing and eligibility. Confirm the features and terms for your business before going live.
Product references: Online payments, platform overview, and developer documentation. These describe supported capabilities; your account configuration and agreed terms determine availability.