Skip to main content
A payment link lets you generate a public URL that you can send to a customer by email, SMS, WhatsApp, or display in your application.

Use cases

  • invoice payment;
  • payment outside a cart;
  • customer collection;
  • manual payment from a back office;
  • recurring payment triggered by a subscription.
The response contains payment_url. Redirect the customer to that URL or share it.

Manage the amount

The amount field is optional at creation time. If you do not set it, the payer can provide the amount at payment time, depending on your integration rules. If max_usage is 1, the link must be treated as single-use.

Manage fees

A payment link can define who pays fees with feeBearer. The historical aliases customerPaysFees, customer_pays_fees, customerPaidFees, and customer_paid_fees are accepted, but feeBearer remains the recommended form.
This route is public. It returns the information required to display the checkout.
The response contains the transaction reference to track with the corresponding status flow.
Use page and limit pagination to load your links progressively in a back office.