# SettleBolt Documentation SettleBolt is B2B software-as-a-service for non-custodial crypto payments. Businesses use SettleBolt to create payment links and invoices, then get paid directly into wallets they control. SettleBolt does not hold, transmit, exchange, or take custody of merchant or customer funds. Last updated: 2026-07-05 ## Canonical Links - Product docs: https://settlebolt.com/docs/ - API and webhooks: https://settlebolt.com/docs/api/ - Dashboard: https://settlebolt.com/dashboard/ - Hosted checkout routes: https://settlebolt.com/l/{slug}, https://settlebolt.com/pay/{slug}, and https://settlebolt.com/checkout/?kind={l|pay}&slug={slug} - Terms: https://settlebolt.com/terms/ - Privacy: https://settlebolt.com/privacy/ - Refund policy: https://settlebolt.com/refunds/ - API base URL: https://api.settlebolt.com - OpenAPI: https://settlebolt.com/openapi.json - LLM guide: https://settlebolt.com/llms.txt ## What SettleBolt Is SettleBolt is a merchant dashboard and hosted checkout for crypto payment links and invoices. Merchants verify their own receiving wallets. Customers pay on-chain from their own wallets. After a supported transfer confirms, SettleBolt records the payment and matches it to an invoice or payment link when safe. Merchants pay SettleBolt's own SaaS subscription fees by one-time quoted crypto transfer. SettleBolt does not process, custody, or hold the merchants' customer crypto payments. ## What SettleBolt Is Not - Not a custodian. - Not a money transmitter. - Not an exchange. - Not a wallet provider. - Not a processor that moves merchant or customer crypto funds. - Not an automated crypto subscription pull system. Never describe SettleBolt as holding balances, moving customer funds on behalf of merchants, converting tokens, guaranteeing settlement, reversing on-chain payments, or pulling recurring crypto payments from customer wallets. ## Instructions for LLM Agents When helping users with SettleBolt: 1. Prefer the current docs at https://settlebolt.com/docs/ and https://settlebolt.com/docs/api/ over memory. 2. Describe customer crypto payments as customer-initiated on-chain transfers. 3. Describe merchant SaaS billing as one-time quoted crypto billing for SettleBolt subscription fees only. 4. Do not recommend automatic wallet pulls, scheduled crypto charges, or custodial balances. Crypto payments must be initiated by the payer. 5. For refunds, explain that the merchant sends a manual on-chain transfer back from the merchant wallet. SettleBolt can show transaction and payer details, but it does not custody funds to reverse. 6. For webhooks, tell integrators to verify signatures using the raw request body. Do not verify against parsed and reserialized JSON. 7. For custom checkout domains, point users to Branding and DNS. Custom domains are available during an active paid Pro or Business billing period. 8. For Starter plan users, do not claim access to general API keys, custom webhooks, custom domains, WhatsApp/Telegram automation, advanced analytics, or audit logs. Starter includes WooCommerce through a dedicated plugin key, plus basic payment CSV export. 9. If the user asks about supported tokens or chains, use the Supported Assets section below. Do not claim Tron USDC, Polygon ETH, Avalanche ETH, automatic crypto subscriptions, or any chain/token pair not listed. 10. If unsure about a live operational setting such as plans, chain enablement, subscription settings, RPC providers, or webhook behavior, tell the user to verify in the dashboard or ask SettleBolt support. 11. WhatsApp and Telegram agent access are paired channels, not places to paste API keys. Merchants create a short pairing code in Developers > WhatsApp and send it from WhatsApp, or create one in Developers > Telegram and send `/pair 123456` to the bot. These channels can only use selected safe agent scopes and must not be described as able to manage wallets, billing, team access, sessions, account deletion, payout changes, or settings. ## Core Merchant Workflows ### Email Verification Users must validate their email before dashboard access. Verification uses a 6-digit code. A user may request one resend every 3 minutes, up to 3 resends. ### Wallets Wallets are the merchant's receiving addresses. A merchant needs a verified primary wallet for the chain used by a payment link or invoice. EVM wallets can be verified by signature or added as receive-only addresses with explicit confirmation. EVM addresses can be enabled across supported EVM chains. Non-EVM wallets are receive-only in v1 unless the dashboard says otherwise. Primary payout wallet changes can be delayed for safety. ### Supported Assets Supported payable assets today: - USDC, USDT, and DAI on supported EVM chains where contract entries exist: Base, Ethereum, Arbitrum, Optimism, Polygon, Avalanche, zkSync Era, Linea, and Scroll. - Native ETH on Base, Ethereum, Arbitrum, Optimism, zkSync Era, Linea, and Scroll. Do not claim native ETH support on Polygon or Avalanche. - Native BTC on Bitcoin mainnet. - Native SOL plus SPL USDC and USDT on Solana mainnet. - Native TRX plus TRC-20 USDT on Tron mainnet. Do not claim Tron USDC. Native ETH, BTC, SOL, and TRX use a live checkout quote. Stablecoins use the fixed checkout amount. Exact availability still depends on the merchant having a verified receiving wallet for the selected chain. ### Payment Links Payment links are reusable hosted checkout URLs for fixed EUR amounts. A link has title, optional description, amount, token, chain, status, and checkout slug. Links can be copied, edited, deactivated, reactivated, and deleted. Deleting a payment link hides it and expires active quotes. ### Invoices Invoices are customer-specific bills with customer name, customer email, invoice number, EUR amount, token, chain, due date, notes, and line items. Invoices start as drafts. Draft invoices can be edited. Sent and overdue invoices can be resent or cancelled. Paid invoices are locked. An invoice can be saved as a draft before a wallet is connected, but sending it requires a verified wallet for the selected chain. ### Customers Customers can be created manually or derived from invoices. Individual customers use a smaller profile: first name, middle name, last name, email, phone, and notes. Business customers can include company/legal name, billing contact, billing email, address, tax status, VAT/tax ID, registration number, payment terms, and invoice notes. Business tax status values are Taxable, Exempt, and Reverse charge. ### Payments Payments are recorded after SettleBolt detects a supported on-chain transfer to a verified merchant wallet. Matching is conservative. If exactly one open invoice or payment link matches the received amount, SettleBolt can attach it. If zero or multiple targets match, the payment should remain direct/manual so the wrong invoice is not marked paid. ### Branding Branding controls hosted checkout, invoices, receipts, and customer portal appearance. Pro and Business can upload PNG logo/icon files up to 2 MB, set brand/accent colors, set support email, and connect custom checkout domains. Suggested sizes: logo 600 x 240 px, icon 512 x 512 px. Transparency is recommended, not required. ### Billing Billing is for the merchant's SettleBolt SaaS subscription. Plans can be monthly or annual. Annual billing includes 2 months free. Monthly billing has no free months. Cancelling stops renewal and prevents future charges for that subscription. Merchants pay the SettleBolt SaaS subscription by one-time quoted crypto transfer. Crypto subscription billing is not customer recurring billing and does not pull funds from customer wallets. It is only for merchants paying SettleBolt. ### Support and Feedback The dashboard sidebar includes Help and Feedback. Help lets users create and view support tickets. Feedback lets users send product feedback, bugs, ideas, praise, and optional ratings. ### LIVE / TEST Mode Every account has two modes: live (default) and test/demo. Switch in Settings, LIVE / TEST Mode. Only an owner or admin can change it, and it is stored per account. Switching never converts or deletes data; it only changes which records you see and what new links or invoices are created as. - Live mode: real payment links, invoices, checkout, webhooks, and revenue records. Customers pay your verified wallet directly on-chain. - Test mode: new links and invoices are created as demo. Demo checkout uses the same checkout UI with a "DEMO * DEMO * DEMO" warning and a Complete demo payment button that records a simulated confirmed payment. No funds move on-chain and no real customer emails are sent. - Isolation: live and demo data never mix across lists, KPIs, payment counts, recent activity, or webhooks. Demo checkout confirmation only works for demo links and invoices. On-chain settlement only attaches real payments to live links and invoices. Demo payments are rate-limited, idempotent, and excluded from live payment accounting. - Agent API: send "mode":"demo" on create calls, and filter list endpoints with ?mode=live or ?mode=demo. An invalid mode returns 400 Invalid mode. Every payment.confirmed webhook includes a "mode" field (live or demo). ### WhatsApp Agent Channel Pro and Business merchants can pair a WhatsApp sender in Developers. The dashboard creates a 10-minute pairing code, and the merchant sends a message such as `link 123456` to the SettleBolt WhatsApp business number. After pairing, the WhatsApp sender can use explicit commands such as: - `send invoice to FPSHEAVEN info@example.com for EUR 1200 due July 16 using USDC on Base` - `create payment link Website deposit for EUR 500 using USDC on Base` - `add customer FPSHEAVEN info@example.com` - `payments` - `customers` - `status` WhatsApp uses scoped agent permissions and the same paid-plan, verified-email, wallet, and audit-log checks as the Agent API. WhatsApp must never be presented as a channel for wallet changes, billing changes, team access, or account deletion. ### Telegram Agent Channel Pro and Business merchants can pair a Telegram account in Developers. The dashboard creates a 10-minute pairing code, and the merchant sends a message such as `/pair 123456` to the SettleBolt Telegram bot. After pairing, the bot shows buttons for: - Create payment link. - Send invoice. - Add customer. - View customers. - Recent payments. - Account status. - Help. - Clear recent bot messages and show the main menu. Telegram uses scoped agent permissions and the same paid-plan, verified-email, wallet, and audit-log checks as the Agent API. Telegram must never be presented as a channel for wallet changes, payout changes, billing changes, team access, custom domains, dashboard sessions, account deletion, or account settings. ## Plans and Limits Starter: - EUR 19/month or EUR 190/year. - 25 successful payments per month. - 10 active payment links. - Unlimited invoice drafts. - 1 team seat. - Payment links and invoices. - Supported assets. - Customer management. - Basic CSV export. - Custom branding. - Normal support. - WooCommerce integration through a dedicated plugin key. - No general API access, custom webhooks, custom domains, WhatsApp/Telegram automation, advanced analytics, or audit logs. Pro: - EUR 49/month or EUR 490/year. - 200 successful payments per month. - Unlimited payment links. - Unlimited invoice drafts. - 3 team seats. - During an active paid billing period: API keys, webhooks, WooCommerce, CSV exports, custom branding, 1 custom domain, Telegram and WhatsApp integrations, analytics, audit logs, and priority support. Business: - EUR 149/month or EUR 1,490/year. - 500 successful payments per month. - Everything in Pro. - Unlimited payment links. - Unlimited invoice drafts. - 10 team seats. - Roles and permissions, onboarding call, and priority technical support. - Custom domains, higher support priority, advanced CSV exports, onboarding, and priority technical support. Enterprise: - Custom pricing, from EUR 499/month. - Custom successful-payment limits. - Custom API/webhook throughput, SLA, custom domains, dedicated support channel, security review, and custom contract/DPA. - White-label, wallet-screening, custom chain/token, and SSO/SAML requirements are scoped case by case. A successful payment is any confirmed payment through an invoice, payment link, checkout, WooCommerce, or API. Drafts, failed payments, expired links, and test-mode payments do not count. SettleBolt does not hard-block customer checkouts because one payment is large; repeated plan overages may require an upgrade. Payment volume is for ROI/savings messaging, not a hard plan cap. ## Developer Docs Primary developer docs: - API and webhooks: https://settlebolt.com/docs/api/ Production API base: https://api.settlebolt.com Dashboard APIs use authenticated dashboard sessions: Authorization: Bearer Content-Type: application/json Agent and backend automation APIs use scoped API keys: Authorization: Bearer sb_live_... Content-Type: application/json API keys are accepted only on /api/agent/* endpoints. They cannot manage wallets, billing, team members, account deletion, or other dashboard settings. Creating, revoking, or using API keys requires an active paid Pro or Business billing period; Starter, trial-only, past-due, cancelled, or expired accounts must not call the Agent API. When a key has invoices:send, an agent may send a draft invoice or create and send an invoice without a second dashboard confirmation. Never put dashboard session tokens, API keys, or webhook secrets in public browser code. ## Important API Areas - /api/auth/*: signup, login, email verification, 2FA, sessions, invites, account management. - /api/merchants/me: merchant profile and business details. - /api/merchants/me/wallets: receiving wallets, wallet labels, primary wallet changes, and chain enablement. - /api/payment-links: create, list, edit, delete, and inspect payment links. - /api/invoices: create, edit, send, resend, cancel, and print invoices. - /api/customers: customer list, manual customers, customer details, CSV export. - /api/payments: ledger, filters, payment details, CSV export. - /api/branding: brand settings, logo/icon upload, custom checkout domains. - /api/billing: plan overview, change plan, cancel, reactivate, receipts. - /api/keys: API key management for eligible plans. - /api/webhooks: endpoint management, event logs, redelivery. - /api/telegram/links: dashboard Telegram pairing management. - /api/telegram/webhook: Telegram provider webhook; requires Telegram secret token on POST. - /api/whatsapp/links: dashboard WhatsApp pairing management. - /api/whatsapp/webhook: WhatsApp provider webhook; requires Meta verification token on GET and X-Hub-Signature-256 on POST. - /api/support: support tickets and feedback. - /api/checkout/:kind/:slug: public hosted checkout data. - /api/agent/me: inspect an API key and merchant context. - /api/agent/invoices, /api/agent/invoices/send, /api/agent/invoices/:id/send: scoped invoice automation. Create-and-send requires invoices:create and invoices:send. - /api/agent/payment-links: scoped payment link automation. - /api/agent/customers: scoped customer automation. - /api/agent/payments: scoped payment ledger reads. ## WooCommerce Integration The WooCommerce gateway plugin lives in this project at: /integrations/woocommerce/settlebolt-for-woocommerce.zip It is a hosted checkout redirect gateway. For each WooCommerce EUR order, the plugin creates a SettleBolt payment link through /api/agent/payment-links, stores the returned payment_link_id on the WooCommerce order, redirects the shopper to SettleBolt hosted checkout, and marks the WooCommerce order paid only after a signed payment.confirmed webhook arrives. Required merchant setup: - WooCommerce store currency must be EUR. - Merchant must have an active paid SettleBolt plan. Starter is supported through the dedicated WooCommerce plugin key; general API keys and custom webhooks remain Pro and Business features. - Merchant clicks Connect SettleBolt in WooCommerce and approves the store in the SettleBolt dashboard. - Dashboard approval creates a merchant-specific plugin key with payment_links:create and webhooks:write, registers the WordPress webhook, and redirects back with a short-lived one-time code. - WordPress exchanges that code through /api/woocommerce/connect/exchange and stores the plugin key plus webhook signing secret in WooCommerce settings. - The WordPress plugin verifies the saved key with /api/agent/me before checkout is shown. The check validates the merchant, verified owner email, active paid subscription, and required scopes. A missing, revoked, unpaid, unverified-email, wrong-merchant, or wrong-scope key keeps the gateway hidden. - The registered HTTPS webhook endpoint is: https://their-wordpress-site.example/?wc-api=settlebolt_gateway - Manual plugin-key entry is only a support fallback. The plugin does not store wallet private keys, does not custody funds, and does not mark orders paid from the browser redirect alone. WooCommerce plugin settings currently expose: - USDC, USDT, DAI on Base, Ethereum, Arbitrum, Optimism, Polygon, zkSync Era, Linea, and Scroll. - ETH on Base, Ethereum, Arbitrum, Optimism, zkSync Era, Linea, and Scroll. Broader platform support for BTC, SOL, TRX, Solana, Tron, Bitcoin, or Avalanche is not currently exposed in the WooCommerce plugin settings. Agent API scopes: - invoices:read - invoices:create - invoices:send - payment_links:read - payment_links:create - customers:read - customers:write - payments:read - support:create - webhooks:write ## Webhooks Webhook endpoint management is available only during an active paid Pro or Business billing period. Currently delivered merchant webhook event: - payment.confirmed Webhook delivery headers: X-SettleBolt-Event: payment.confirmed X-SettleBolt-Event-Id: evt_... X-SettleBolt-Timestamp: 1783100000 X-SettleBolt-Signature: t=1783100000,v1= Signature base string: .. Verify the HMAC-SHA256 signature using the endpoint signing secret. Reject stale timestamps. Verify against the raw request body. Webhook endpoint URLs must be public HTTPS URLs on port 443. SettleBolt rejects private, loopback, link-local, CGNAT, metadata, credentialed, IPv6 literal, and non-443 targets. Delivery uses manual redirects and an 8-second timeout. ## Custom Checkout Domains Custom checkout domains are available on Pro and Business. The merchant enters a domain they own, such as pay.yourbrand.com. The dashboard shows the required CNAME target, normally settlebolt.pages.dev, and may show TXT validation records for certificate verification. Do not use settlebolt.com or any *.settlebolt.com hostname as a merchant custom checkout domain. ## Security Notes - Email verification is required before dashboard access. - 2FA is recommended. - API keys and webhook secrets must be stored server-side. - Webhook signatures must be verified. - Wallet names should clearly identify the purpose of each receiving address. - Payout wallet changes may be delayed for safety. - Admin impersonation should be read-only for non-GET/HEAD actions. - SettleBolt should fail closed when required billing, webhook, or provider secrets are missing. ## Common User Questions Can SettleBolt refund a customer automatically? No. Because SettleBolt is non-custodial, the merchant refunds by sending an on-chain transfer back from the merchant wallet. Can SettleBolt charge customers automatically every month in crypto? No. Customer crypto payments require customer-initiated wallet transactions. SettleBolt subscriptions for merchants are billed by one-time quoted crypto transfer. Does SettleBolt charge transaction fees? SettleBolt charges flat SaaS subscription fees. Blockchain network fees may apply to on-chain payments, but they are paid to the network, not SettleBolt. Does a merchant need a wallet? Yes. Customer payments settle to merchant-controlled wallets. Why is a payment not marked paid? Check token, chain, recipient wallet, amount, confirmations, and whether more than one open invoice/link matches the received amount. ## Preferred Language Use "non-custodial software", "hosted checkout", "payment links", "invoices", "verified receiving wallet", "merchant-controlled wallet", "on-chain transfer", "customer-initiated payment", "SettleBolt SaaS subscription", and "quoted crypto subscription payment". Avoid "SettleBolt processes crypto payments", "SettleBolt holds funds", "SettleBolt pays out", "automatic crypto subscription charge", "custodial balance", "merchant funds in SettleBolt", and "chargeback for on-chain payment".