> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zbx.boomfi.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose Your Integration

> Decide between checkout paylinks, subscriptions, and permanent deposit accounts.

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

## Decision guide

| If you…                                                           | Use                                                                |
| ----------------------------------------------------------------- | ------------------------------------------------------------------ |
| Sell a fixed-price product or invoice                             | [Payments Overview](/payments/overview)                            |
| Bill on a schedule (membership, SaaS)                             | [Subscriptions](/payments/subscriptions)                           |
| Maintain a **user balance** (deposits of any amount over time)    | [Deposit Accounts Overview](/deposits/overview)                    |
| Are a PSP or acquirer (you and your merchants are both merchants) | [Cookbook: Offer Crypto as a PSP](/payments/cookbook-psp-paylinks) |

## Payment links and checkout

* 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](/payments/cookbook-sell-product). If you create those links for merchants on your PSP, use [Cookbook: Offer Crypto as a PSP](/payments/cookbook-psp-paylinks).

## Subscriptions

* Create a **recurring** plan / paylink
* Customer renews on interval; invoices may open and become overdue
* Handle `Subscription.*` and `Invoice.*` events

Start with [Subscriptions](/payments/subscriptions) and [Cookbook: Recurring Billing](/payments/cookbook-recurring).

## 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](/deposits/cookbook-user-balance) and [Create a Deposit Address](/deposits/create-address).

## Platform integrations

If you already bill in Stripe, Chargebee, WooCommerce, or WHMCS, add crypto pay links via [Integrations Overview](/integrations/overview).

## PSP / acquirer

* You are a ZBX merchant; each merchant on your platform is also a merchant
* You hold their API keys and run the [paylink flow](/payments/paylinks) on their behalf
* Use [variant URLs](/payments/paylink-features#change-amount-and-currency) when the amount or currency changes per invoice

Start with [Cookbook: Offer Crypto as a PSP](/payments/cookbook-psp-paylinks). One organisation with many settlement wallets is [Account-Specific Paylinks](/payments/account-specific-paylinks).

<Warning>
  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](/pricing/networks-and-currencies) and [Pricing and Fees](/pricing/fees-and-pricing) (including recovery fees when recovery is possible).
</Warning>

## Shared setup checklist

Before go-live on any path:

* [ ] API key stored securely
* [ ] Settlement / virtual account configured
* [ ] Webhook URL set and [Verify Webhook Signatures](/webhooks/verify-signatures) implemented
* [ ] Event history reviewed under API & Webhook → Webhooks
* [ ] Dashboard [Payments Settings](/dashboard/payments-settings) matches production wallets
* [ ] Third-party integrations configured if you use them ([Integrations Overview](/integrations/overview))