Run your crypto payments workflow.

SettleBolt lets businesses create payment links and invoices for crypto payments. The customer pays on-chain. Funds settle directly to the merchant wallet that is verified in the dashboard.

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.

Annual billing includes 2 months free. Monthly billing has no free months. Successful-payment allowances are shown in usage and are not payment-volume caps. SettleBolt does not hard-block customer checkouts because one payment is large; repeated plan overages may require an upgrade.

Availability depends on the token, chain, and the merchant's verified wallet setup. Checkout always shows the exact asset, network, amount, and recipient address before payment.

Native ETH, BTC, SOL, and TRX use a live quote at checkout. Stablecoins are shown at the fixed checkout amount.

Every SettleBolt account has two modes, switched from Settings, LIVE / TEST Mode. The current mode is stored per account, and only an owner or admin can change it. Switching modes never converts or deletes anything. It only changes which records you see and what new links or invoices are created as.

Live mode

The default. Payment links, invoices, hosted checkout, webhooks, and revenue records are all real. Customers pay your verified wallet directly on-chain.

Test mode

For product demos, WooCommerce test setups, and integration testing. 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.

What stays isolated

• Live and demo data never mix. Lists, KPIs, payment counts, and recent activity are filtered by the active mode.
• Demo invoices never send real customer emails.
• Demo checkout confirmation only works for demo links and invoices, never a live one.
• Demo payments are rate-limited, idempotent, and excluded from live payment accounting.
• On-chain settlement only ever attaches real payments to live links and invoices. Demo targets are never settled with real funds.
• Every webhook event carries a mode field (live or demo) so integrations can ignore demo events in production.

In the Agent API, set "mode":"demo" when creating a payment link or invoice, and filter list endpoints with ?mode=live or ?mode=demo. An unrecognized mode value is rejected with 400 Invalid mode.

Your wallet is your settlement destination. A payment link or invoice only works when the selected chain has a verified primary receiving wallet.

Add a wallet

1. Open Wallet in the dashboard.
2. Choose a chain and enter a wallet name if you want one.
3. For browser wallets, sign the challenge. For receive-only addresses, paste the exact address and confirm it.
4. Set a primary wallet per chain when you have more than one verified address.

Payment links are reusable hosted checkout URLs for fixed EUR amounts. Customers pay in the token and chain you select, and SettleBolt records the on-chain payment when it confirms. Hosted checkout can appear as /l/{slug} or /checkout/?kind=l&slug={slug}.

Create a payment link

1. Go to Payment Links and click New payment link.
2. Enter title, optional description, amount, token, and chain.
3. Save the link and copy the checkout URL.
4. Share it with your customer.

You can edit a link, deactivate it, reactivate it, copy it, view its payments, or delete it. Deleting is a soft delete: the link is hidden and its active quotes are expired. If an existing link displays Open amount, the customer enters the amount at checkout; otherwise the amount is fixed.

Invoices are customer-specific bills with line items, due dates, and a hosted pay page. They start as drafts, then become sent invoices when emailed to the customer.

Create and send an invoice

1. Open Invoices and click New invoice.
2. Add customer name and email. If you already added the customer, use the customer record.
3. Use the suggested invoice number or enter your own unique number.
4. Choose currency EUR, token, chain, due date, and line items.
5. Click Save draft to keep editing, or Save and send to email the pay link.

The invoice amount must match the line item total when line items are present. Invoices can be viewed, duplicated, downloaded as PDF, and cancelled when unpaid. Draft invoices can be edited and sent; sent or overdue invoices can be resent.

Customers appear automatically when you invoice them. You can also add manual contacts before billing them.

Tax status

Business customers can be marked as Taxable, Exempt, or Reverse charge. Use the status your accountant expects for that customer's location and tax relationship.

Customer detail pages show total billed, paid, outstanding, average invoice, invoices, and payments. Removing a manual contact removes the saved contact profile, not historical invoices or payments.

The Payments ledger shows confirmed, pending, underpaid, overpaid, failed, invoice, link, and direct payments. You can filter by date, status, token, chain, source, transaction hash, or payer address.

Refunds

Because SettleBolt is non-custodial, refunds are manual on-chain transfers from your wallet back to the customer. The payment detail view shows the payer address and transaction hash to help you refund correctly.

Basic payment CSV export is available on Starter and higher. Customer, analytics, and advanced exports may require Pro, Business, or Enterprise.

Branding controls how checkout, invoices, receipts, and the customer portal look. It is available on Pro and Business.

Custom checkout domain

1. Use Pro or Business.
2. Open Branding, enter a domain you own, such as pay.yourbrand.com.
3. Add the CNAME record shown in the dashboard. The default target is settlebolt.pages.dev.
4. If the dashboard shows TXT validation, add that TXT record too.
5. Wait for Cloudflare certificate validation to complete.

Do not use settlebolt.com or a *.settlebolt.com hostname as your custom domain.

Invites are emailed to teammates. Removing a teammate revokes their sessions for this merchant account. Starter includes 1 seat, Pro includes 3, and Business includes 10.

Billing is for the SettleBolt SaaS subscription only. Merchants pay SettleBolt with a one-time quoted crypto transfer. This is separate from customer payments.

• Change plan: choose Starter, Pro, or Business and monthly or annual billing.
• Crypto subscription payment: merchants pay SettleBolt from their own wallet with a quoted one-time transfer.
• Pay with crypto: send the exact quoted amount before the payment window expires. This pays SettleBolt's SaaS subscription only.
• Cancel subscription: cancellation stops renewal immediately, and you will not be charged again for that subscription.
• Reactivate: available when a cancelled subscription can still be resumed.
• Receipts: view SettleBolt receipts and invoices for crypto subscription payments. Legacy card receipts may remain visible for older accounts.
• Billing history: admins can view purchases, downgrades, checkout starts, plan changes, and receipts from the admin dashboard.

The dashboard sidebar includes Help and Feedback near the bottom.

Ticket categories are General, Billing, Payments, Wallets, Technical, Security, and Privacy. Priorities are Normal, Low, High, and Urgent. Ticket subjects can be up to 140 characters and messages up to 4,000 characters.

Analytics is available on Pro and Business. It shows total volume, payment count, average payment, average invoice, time series, by-token breakdown, by-chain breakdown, top customers, and top payment links.

Supported ranges include 7D, MTD, 30D, 90D, YTD, 12M, and Custom. Empty states stay quiet when there is no activity in the selected range.

The production API base is:

https://api.settlebolt.com

Dashboard routes use the authenticated dashboard session token:

Authorization: Bearer <dashboard-session-token>
Content-Type: application/json

Starter can still use WooCommerce through the dedicated plugin key created by the Connect SettleBolt flow. That key is limited to payment_links:create and webhooks:write.

Pro and Business can pair Telegram or WhatsApp senders to scoped agent actions. These channels are for quick operations, not account administration.

Telegram and WhatsApp cannot manage wallets, payout changes, billing, team access, sessions, account deletion, custom domains, or dashboard settings.

The SettleBolt WooCommerce gateway creates a hosted checkout payment link for each WooCommerce order, redirects the customer to SettleBolt, and marks the order paid only after a signed payment.confirmed webhook arrives.

How checkout works

1. The shopper chooses SettleBolt at WooCommerce checkout.
2. The plugin creates a SettleBolt payment link through /api/agent/payment-links.
3. The shopper pays on SettleBolt hosted checkout.
4. SettleBolt watches the selected chain and records the payment after confirmation.
5. A signed webhook reaches WordPress and the WooCommerce order is marked paid.

WooCommerce plugin settings currently expose USDC, USDT, DAI, and ETH on supported EVM chains. BTC, SOL, TRX, Solana, Tron, Bitcoin, and Avalanche are broader platform capabilities and may not appear in the plugin settings yet.

Webhooks are available only during an active paid Pro or Business billing period. Add an HTTPS endpoint in Developers, copy the signing secret once, and verify every delivery.

payment.confirmed is the currently delivered merchant webhook event. Ignore other event labels unless this API reference lists them as delivered.

X-SettleBolt-Event: payment.confirmed
X-SettleBolt-Event-Id: evt_...
X-SettleBolt-Timestamp: 1783100000
X-SettleBolt-Signature: t=1783100000,v1=<hmac>

The signature is HMAC-SHA256 over:

<timestamp>.<event_id>.<raw_json_body>

Webhook URLs must be public HTTPS endpoints on port 443. Internal, loopback, link-local, metadata, credentialed, IPv6 literal, and non-443 URLs are rejected.

• Verify your email before using the dashboard.
• Enable 2FA in Settings.
• Name wallets clearly so payout destinations are easy to inspect.
• Use separate support/admin accounts instead of shared logins.
• Keep API keys and webhook secrets in server-side secret storage.
• Verify webhook signatures and reject stale timestamps.
• Use HTTPS-only webhook endpoints.
• Review Billing and Support history after plan or access changes.

Payment is not showing

Check that the customer paid the exact token and chain on the checkout page, that the recipient address is your verified primary wallet for that chain, and that enough confirmations have passed.

Invoice cannot be sent

The invoice chain needs a verified wallet before sending. Draft invoices can be saved before a wallet is connected.

Custom domain is pending

Confirm the CNAME target and any TXT validation records exactly match the Branding screen. Certificate validation can take time after DNS propagation.

Customer did not get an invoice email

Use Resend on sent or overdue invoices. Also confirm the customer email is valid and check spam/quarantine filters.

Need help

Open Help in the dashboard, create a ticket, and include invoice IDs, link URLs, wallet addresses, transaction hashes, and screenshots when relevant.