Skip to main content
Pick the money-in path that matches your product. You use the same organisation, API keys, settlement, and webhooks either way.

​
Decision guide

  • Customer pays a known amount for goods or services
  • You share a link or redirect to hosted checkout
  • You fulfill when you receive a successful payment webhook
Start with Cookbook: Sell a Product. If you create those links for merchants on your PSP, use Cookbook: Offer Crypto as a PSP.

​
Subscriptions

  • Create a recurring plan / paylink
  • Customer renews on interval; invoices may open and become overdue
  • Handle Subscription.* and Invoice.* events
Start with Subscriptions and Cookbook: Recurring Billing.

​
Deposit accounts

  • Issue a permanent crypto address per user (reference = your user id)
  • Deposits are swept to your parent virtual account
  • Credit your ledger only after verified payment events
Start with Cookbook: User Balance Deposits and Create a Deposit Address.

​
Platform integrations

If you already bill in Stripe, Chargebee, WooCommerce, or WHMCS, add crypto pay links via Integrations Overview.

​
PSP / acquirer

  • You are a BoomFi merchant; each merchant on your platform is also a merchant
  • You hold their API keys and run the paylink flow on their behalf
  • Use variant URLs when the amount or currency changes per invoice
Start with Cookbook: Offer Crypto as a PSP. One organisation with many settlement wallets is Account-Specific Paylinks.
Only accept assets and networks enabled for your settlement / virtual account. Funds sent on the wrong network or with an unsupported token may not be credited. See Networks and Currencies and Pricing and Fees (including recovery fees when recovery is possible).

​
Shared setup checklist

Before go-live on any path: