Paid features

Feature passes

Native QuickBooks/Xero connectors and new Pro purchases are disabled. Use the payment API, signed webhooks and CSV/JSON exports to build your own accounting integration. Growth includes branding, analytics, Webhook Pro, Team and Audit.

Confirmed refund receipts

In the workspace refund list, choose Download receipt after confirmation. API clients use GET /v1/refunds/{id}/receipt with refunds:read. The free JSON download includes the exact USDC amount, original payment reference, network, token, sender, recipient, transaction and confirmation time. New confirmations also include the canonical block hash; older records may omit it. Downloads read stored evidence and do not make new blockchain requests.

A transaction can confirm only one refund per workspace and network. Pending or ambiguous refund proof returns HTTP 409. This record is not a signed certificate or tax document; the transaction can be independently checked on its network.

Advanced merchant capabilities are activated from the same prepaid credit balance for 30 days. There is no automatic renewal or wallet debit. Core payment status, receipts, basic customer/AR tools, refunds, credit notes, security controls and the primary webhook do not require a premium pass.

Purchase or extend any pass through the single FeaturePass endpoint:

POST /features/branding/purchase
Idempotency-Key: branding-period-001

Then configure the capability separately. For Branding:

PUT /branding
{"name":"Example Studio","accent":"#2558ed"}

Growth includes Branding, Advanced Analytics, Webhook Pro, Team and Extended Audit. Retired Pro included those capabilities plus both accounting connectors. At most one year of a SKU can be prepaid. Editing settings during an active entitlement does not spend extra credits.

Data boundaries

We retain payment records, wallet and recipient addresses, API authentication data, webhook settings and feature settings needed to operate the payment service. Descriptions and order references are payment metadata, not encrypted storage. Never upload product contents, private keys or license codes into those fields. Seller fulfillment and its recovery are the seller’s responsibility.