Collections
Manage sales in the dashboard or integrate hosted checkout with your application.
Collections brings together your catalog, customers, discounts, subscriptions, invoices and incoming collections. Use the dashboard to manage sales or integrate hosted checkout with your application.
Operate from the dashboard
Select the active account and environment and check your role's access before making changes. Start with Products and prices, then create a Payment Link for a reusable offer or an invoice for a customer.
| Task | Guide |
|---|---|
| Prepare what you sell | Products and prices |
| Manage contacts and billing information | Customers |
| Offer a code-based discount | Coupons |
| Offer automatic benefits | Promotions |
| Understand several benefits together | Combine discounts |
| Manage recurring billing | Subscriptions |
| Create invoices and record payments | Invoices |
| Investigate unpaid collections | Collection recovery |
| Give customers self-service access | Customer portal |
Find your use case
Use Payment Links
Use Payment Links when an operator manages a reusable offer and shares one URL through a site, message, campaign or QR code. They require catalog products and prices; API access is optional.
Cart Checkout
Use Cart Checkout when your backend owns the cart and creates a Checkout Session for each purchase attempt. It can use catalog prices or inline pricing. Keep the API key on your server; the browser receives the hosted checkout URL.
Both paths use hosted checkout and the same commercial processing after session creation. An API cart can be edited while open and unprepared, using Idempotency-Key and If-Match. Payment Link edits affect later sessions; an existing attempt retains its snapshot.
Before you start
- Configure a payment connection and valid routes for the intended countries and currencies.
- Decide whether the offer is one-time, recurring, a trial or a compatible mixed cart.
- Test in Sandbox before publishing.
- For an integration, configure signed Webhooks and fulfill only after verifying
invoice.paid.
Checkout Session status describes the buyer flow and paymentStatus describes collection. A completed page or redirect does not prove payment; a processing payment can finish later. For dashboard operations, review the invoice's actual paid and outstanding amounts.