Introduction - Payment link

The payment link allows you to provide a payment page hosted by Asaas so the customer can enter their details and complete the payment.

This feature is recommended when your integration does not have all the customer data at the time of sale or when you want to share a simple link through channels such as website, e-mail, WhatsApp, or social media.

With the payment link, you can create one-time, installment, or recurring charges, either by defining the amount in advance or allowing the customer to enter how much they want to pay.

When to use payment link

Use payment link when your integration needs to:

• sell without previously registering the customer;
• share a payment page with multiple customers;
• allow the customer to fill in their own details;
• allow the customer to choose the amount or the number of installments;
• provide a hosted page without building your own checkout;
• create a simple payment flow for campaigns, services, or one-time sales.

If your integration already has the customer data and needs to control the entire charge creation through the back-end, use the Charges flow.

Differences between charge and payment link

Main settings

When creating a payment link, evaluate the main flow settings:

• charge type: one-time, installment, or recurring;
• payment method available to the customer;
• fixed amount or open amount;
• maximum number of installments, when applicable;
• expiration date or link usage period;
• description displayed on the payment page;
• redirection after payment, when configured.

These settings directly impact the customer experience, payment reconciliation, and operational control of the sale.

Basic flow

Create payment link
↓
Receive the link URL
↓
Share the link with the customer
↓
Customer fills in the details and pays
↓
Track the generated charge
↓
Reconcile the payment in the source system

Usage example

A service system can create a payment link for a one-time sale and send the URL to the customer through WhatsApp.

In this scenario, the customer accesses the link, enters the requested details, chooses the available payment method, and completes the payment on the page hosted by Asaas.

After the payment is created, the integration must track the generated charge to identify whether it was paid, overdue, canceled, or whether there was a payment failure.

Important precautions

• Use charges via API when you need to create the payment for an already registered customer.
• Use payment link when it makes sense to let the customer fill in their own details.
• Avoid using the same link for flows that require previous identification or individualized control before payment.
• Check whether the configured payment methods are suitable for the charge type.
• Track the charges generated by the link to keep financial reconciliation updated.
• If you need to split amounts between accounts, use the split feature in charges, not in payment link.

Next steps

After understanding the use of payment link, also see:

• Create payment link
• Charges
• Redirection after payment
• Notifications
• Webhooks