Public checkout and analytics
Resolve a Payment Link, create isolated Checkout Sessions and inspect attribution.
The Paybytoken-hosted page uses the public token in the Payment Link URL. These endpoints do not accept a merchant secret key:
| Method | Endpoint | Purpose |
|---|---|---|
GET | /public/v1/payment_links/:publicToken | Resolve customer-safe link content. |
POST | /public/v1/payment_links/:publicToken/visits | Record an anonymous attributed visit. |
POST | /public/v1/payment_links/:publicToken/checkout_sessions | Create one isolated Checkout Session. |
A customer-entered link requires amount when creating its Checkout Session. You can also provide
customer_email, client_reference_id, and the payment_link_visit_id returned by visit tracking.
Do not use public endpoints to fulfill an order.
Merchant analytics
| Method | Endpoint | Purpose |
|---|---|---|
GET | /api/v1/payment_links/:id/analytics | Read totals, conversion, time series, sources and recent activity. |
GET | /api/v1/payment_links/:id/analytics/export | Export the selected period. |
Analytics are directional product metrics, not a financial ledger. Reconcile money using Payment Intents, balance transactions and signed webhooks. Visit identifiers must be anonymous; do not put email addresses, wallet addresses or secret values in attribution fields.
Did this page answer your question?
Your feedback helps us improve the integration path.