Docs

Merchants

What a merchant record represents in your account, and what it owns.

Your account can own one or many merchants. A merchant is the unit of integration — one merchant, one API key, one webhook URL, one set of invoices.

What a merchant owns#

  • A display name and basic metadata.
  • One API key — use on every server-to-server call. Rotatable from the dashboard.
  • One webhook URL where every event for this merchant's invoices is dispatched.
  • One webhook secret for HMAC-SHA256 signing. Also rotatable.
  • A set of withdrawal addresses (per network) where confirmed invoice proceeds are paid out.
  • All invoices, webhook events, and payouts created for this merchant.

One account, several merchants#

It's common to split by:

  • Environment — acme-staging and acme-prod with different webhook URLs, keys, and withdrawal addresses.
  • Brand — one merchant per storefront.
  • Region — separate merchants when local accounting or compliance requires it.

All merchants roll up to a single login.

What you configure#

  • Name — shown in your dashboard and in your emails.
  • Webhook URL — where events land. Must be HTTPS in production.

What the platform manages#

  • Deposit addresses — derived from a per-merchant HD wallet. You never pick an invoice address manually.
  • Exchange rate source — the platform's rate source is used for every invoice.
  • Commission — set at onboarding; surfaced on every invoice as commission_amount.

See also#