Choose your integration
Native Fanvue sales (tips, PPV posts, paid messages, profile subscriptions) need no integration; observe them with the
creator.* webhooks. A third flow, fan experiences (a fan paying inside a fan-facing app), runs on its own rails via the Experiences token endpoints.Option 1: Create a checkout link in the dashboard
In the Fanvue dashboard, open the Checkout links page, create a product with a price (one-off or subscription), and copy the link:Option 2: Create checkout links via the API
Requires thewrite:creator scope.
url:
source.kind:new_product,existing_product, orexisting_price- Amounts are minor units: free is
0, paid is300to250000($3 to $2,500) - Subscriptions:
isRecurring: truepluscycleLengthandcycleUnit(day,week,month,year) redirectUrl: your own post-purchase page- Agencies:
POST /creators/{creatorUserUuid}/checkout-links
GET, PATCH (enable/disable), and DELETE.
Attach your own references
Append attribution to the link you share; it’s echoed on every related webhook, including refunds and disputes:Handle webhooks
Every sale, refund, and payout is delivered to your endpoint. Subscribe via the Developer Area Events tab or Configure webhooks in the dashboard (includes a no-code Zapier path), then branch ontype:
Verify the signature on every delivery, and don’t count BNPL installments as new revenue: the sale arrives paid in full upfront.
See it work end to end
1
Create a test link
Small amount (minimum $3), on your test creator account.
2
Buy it
Open the link in a private window and pay. There’s no sandbox; this is a real charge.
3
Watch the events arrive
checkout_link.payment.pending then .succeeded, with your client_reference_id echoed.4
Check the ledger
The payment appears in the Payments tab of the Checkout links page.
Next steps
Checkout event reference
Every event, with full field tables and payloads.
Checkout Attribution
client_reference_id and metadata in depth.Configuring webhooks
Receive events via API, app, or Zapier.
App Payments
Charge creators for your Fanvue app.