Payment Links
A checkout you can configure, share and follow.
KezaroPay Payment Links brings a product or service description, amount and customer fields into one checkout workflow. Explore link creation, QR sharing and payment records without building a storefront.
Describe what the customer is paying for
Start with a clear product or service name and a useful description. The editor supports a fixed amount or an amount chosen by the customer, with USD as the current currency option.
Set quantity where relevant. A reusable link can remain open for more than one payment; an expiration date can limit when it is available. Test those settings before sharing any example.
Ask for the information the sale needs
The link editor includes customer email, phone and billing-address options. Choose fields for a concrete purpose, such as an invoice or service coordination, rather than collecting extra information by default.
The current checkout displays card, Apple Pay and Google Pay choices as test experiences. They are not live processing methods, and a simulated receipt does not mean an email was delivered.
Share the link or its QR code
The workspace provides a checkout URL and QR sharing workflow. Open the link yourself to review the amount, customer fields and branding before showing it to someone else.
The public sample checkout is an illustration. Do not put real card details into it or present a successful test result as proof of payment.
Follow status without confusing it with settlement
Link details bring the link’s state and its associated payment activity together. The analytics screens help illustrate how views, payments and collected amounts would be reviewed.
The Payments model separates Pending funds from Available funds. A test success, an active link and a settled balance each describe something different.
Use the same merchant requirements
Payment Links shares the Payments account’s Merchant Protection Reserve with Gateway. Creating more links does not create a new $300 reserve for each link.
Live use also requires a connected processor, merchant review and a genuine support route. These requirements are not satisfied by creating a link in the testing workspace.