Payment Links vs. Checkout Sessions
Understanding the difference helps you pick the right tool for the job.Payment Links
Persistent & reusable. Share once, collect many times. Best for products, subscriptions, donation pages, and invoices you send repeatedly.
Checkout Sessions
Single-use & expiring. Created per transaction, expire after 120 minutes. Best for dynamic carts where amount or line items vary per customer.
Creating a Payment Link
Creating a Link in the Dashboard
If you prefer a no-code approach, you can create and manage payment links directly from the FlareHQ Dashboard without touching the API.Parameters
string
required
Display name for the product or offering shown on the payment page, e.g.
"Developer Tier Pass".string
required
Fixed USDC amount as a decimal string, e.g.
"50.00". Payment links always charge this exact amount.string
required
Must be
"USDC".boolean
When
true, the payment page includes a form for the buyer’s name and shipping address. The collected address is included in the webhook payload. Defaults to false.Response Fields
string
Unique identifier for the payment link, e.g.
lnk_7x9mq2z1a8.string
The shareable checkout URL, e.g.
https://flarehq.xyz/pay/lnk_7x9mq2z1a8.string
The product name you provided.
string
The fixed USDC amount the link will charge.
boolean
true when the link is accepting payments. You can deactivate a link from the Dashboard to stop new payments without deleting it.string
ISO 8601 timestamp when the link was created.
Example Response
Use Cases
Product Sales
Set a fixed price for a digital download, NFT, or physical good and share the link on your website or social media.
Subscription Paywalls
Create a link per subscription tier and gate access to your content or community behind the payment URL.
Donation Pages
Let supporters pay any amount by setting a nominal price and instructing donors to adjust the quantity, or create multiple links for preset donation amounts.
Invoice Links
Generate a named link per client or project and include it in your invoice email — no payment processor account required on the client’s side.
Webhook Events
FlareHQ fires aPOST to your configured webhook URL each time a payment link is successfully paid.
Example Payload — payment.completed
Configure your webhook URL from the Dashboard under Settings → Webhooks. The same webhook endpoint receives events from both payment links and checkout sessions — use the
linkId field to distinguish link-originated payments.
