Browse wiki · Paid features

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 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, refunds, security controls and the primary webhook do not require a premium pass.

PassCredits / 30 days
Advanced Analytics1,000
Webhook Pro1,000
Team / RBAC1,500
Extended Audit1,000
Growth bundle2,500

Purchase or extend any pass through the single FeaturePass endpoint:

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

Growth includes Advanced Analytics, Webhook Pro, Team and Extended Audit for 2,500 credits (25 USDC) per 30 days, compared with 4,500 credits individually. Existing prepaid periods keep their expiry. Branding is retired: its API, appearance settings and new purchases are unavailable. Remaining value from an old individual Branding pass is frozen when its workspace first initializes after retirement and can reduce an explicitly confirmed Growth upgrade, even after the original expiry. No automatic charge or refund occurs. At most one year of a SKU can be prepaid.

Extended Audit

Finance → Activity audit traces retained changes to people, API keys and requests. The newest 100 events are free. Extended Audit adds actor/name/role, action, resource and request filters, UTC date ranges, cursor pagination and CSV exports. Export the current page or all retained matching events; large exports can be stopped. Expand an event for correlation identifiers and an invoice timeline when available.

At most 10,000 operational events are retained; buying a pass does not extend retention. Events are not immutable or cryptographically signed and this is not a compliance archive or financial ledger. Event rows can include both domain changes and request records for the same operation. After pass expiry, unfiltered recent activity remains free.

GET /audit-events?limit=100
GET /audit-events?limit=500&actor=finance&from=2026-09-01&to=2026-09-28
GET /audit-events?limit=500&cursor=NEXT_CURSOR
GET /audit-events?format=csv&limit=500

Requires an owner key with audit:read. Keep the same filters when using nextCursor. A sparse filter may yield an empty page with a continuation cursor; continue until the cursor is absent. Pages are bounded by a scan budget and exclude events newer than the first page snapshot. CSV responses expose X-Next-Cursor. Retention can remove records during export; keep external copies if you need permanent history.

Team API access and roles

Team / RBAC costs 1,500 credits (15 USDC) for 30 days, or is included in Growth. The pass enables separate identities for colleagues and services, role-bounded API keys and central revocation. Human members can also accept a wallet-bound invitation and open a shared workspace view for invoices, receipts, refunds and billing according to their role. The workspace owner remains the wallet that signed in.

A member name is only a label: a member named admin with the Finance role has Finance permissions. Both human and service members can use Bearer API keys. Human members can additionally accept a wallet invitation; service members use keys. Permissions are limited by both the role and the scopes selected for the key.

RoleAccess
AdminMost merchant API scopes, including team, billing and integration settings. Owner-only activity audit and accounting export are excluded. Cannot replace the owner wallet or sign wallet transactions.
DeveloperCreate/cancel invoices and payment intents, manage webhooks, read billing. No team management or refunds.
FinanceRead invoices, receipts and billing; cancel invoices and prepare/confirm refunds. Cannot create invoices, manage webhooks or buy passes.
SupportRead invoices, payment records and refunds. No mutations or billing access.
Read onlyRead invoices, payment records, refunds and billing. No mutations.

Owner is reserved for the workspace wallet and cannot be assigned through Team. Accounting connector scopes do not enable the retired QuickBooks/Xero routes. Other paid capabilities still require their own entitlement or a covering bundle.

Use a team key

In API → Team & roles, create a member and select Create key. Select only the permissions needed and an expiry of 1, 7, 30 or 90 days (default 30). The API also supports explicit scopes and expiry. Store the secret on your server, not in browser JavaScript or a public link.

GET {API_BASE}/invoices?limit=10
Authorization: Bearer YOUR_TEAM_KEY

GET {API_BASE}/accounting/export
Authorization: Bearer YOUR_FINANCE_KEY

Use the same workspace API base URL shown in the portal. HTTP 403 means the key lacks the required scope; 401 covers invalid, expired or revoked keys and disabled members. A missing or expired Team entitlement returns 402 for otherwise authorized team requests. Revoking a key or disabling its member takes effect on subsequent requests; requests already admitted can finish. The owner can revoke access even after the pass expires.

A refund API request creates a record; it does not move USDC. The merchant must separately sign the transfer, and confirmation verifies blockchain evidence. No team key contains signing authority. Current roles cover the whole workspace; custom roles and object-level restrictions are not available. Access policies can impose a creation-credit budget, an invoice amount cap and owner approval for sensitive actions.

Wallet invitations

In Team & roles, choose Invite wallet for a human member and enter their EOA address. The colleague signs in with that wallet, selects the invited workspace and explicitly accepts access. No email or shared API secret is required. An invitation cannot silently change its wallet: disable the member and create a new invitation if necessary. Every delegated request rechecks the active membership, role, wallet binding and Team entitlement. Disabling a member blocks their next shared-workspace request as well as their API keys. Their personal workspace remains separate.

Limits and audit

Each workspace supports 25 active team members, 200 retained member records and 10 new members per hour. Each member supports 5 active keys, 100 retained keys, 3 new keys per hour and 10 per day. Revocation does not reset issuance counters. Approvals & access audit shows the latest access lifecycle records and workspace mutations, with actor and target information. Secrets and signed authorization headers are never included.

Agent budgets

Access policy can cap total creation credits and each invoice's USDC amount. Zero credits or an empty amount cap disables that constraint. The budget counts successful creations while enabled, is stored across restarts and is not refunded by cancellation. Idempotent invoice retries do not spend it again. Updates preserve the spent counter and use a revision to prevent lost updates. Success-fee reserves and charges remain separate from this creation budget.

Budgeted members must use direct invoice creation. Alternate spending paths (payment intents, feature purchases and delegated key issuance) are blocked, so they cannot bypass the budget. The wallet recipient remains fixed to the workspace.

Owner approval

When enabled, invoice cancellations, refund mutations and credit-note mutations return HTTP 202 with code: approval_required and an approval record. Send an Idempotency-Key for these requests. A 202 is not a completed cancellation or refund. The owner reviews the exact request in Approvals & access audit, then approves execution or rejects it. Pending requests expire after 24 hours. Other sensitive configuration changes must be performed by the owner directly.

The server rechecks the member and entitlement before execution. Decisions cannot be replayed. A crash after execution begins leaves an executing record for operator reconciliation, not an automatic retry. At most 25 unexpired pending requests and 1,000 retained approval records are allowed per workspace. Approval never signs a USDC transfer; the merchant wallet still signs separately. This is one-owner approval, not a configurable multi-person approval chain.

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.

← All topics