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.

Basic invoice and fixed-amount payment-link collection remains available without a current paid billing period, subject to account, wallet and payment-detection checks. Paid Starter enables its subscription features, including the WooCommerce connection and basic CSV export; general API access and custom webhooks require active Pro or Business access. An expired term does not cancel previously issued payment obligations.

Annual billing includes 2 months free. Monthly billing has no free months. The monthly allowance counts successful live payments, not payment volume, and does not block payment requests or customer checkouts. The dashboard shows usage and warns when the allowance is reached. Monthly usage follows your billing start date, including on annual plans; accounts without a current billing period use calendar months. Contact support if you regularly need a larger plan or want to change tiers during an active paid term.

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.

Match the contract shown on checkout, not just the wallet symbol. Native USDC and bridged USDC.e/USDbC are different assets. The registered USDT contracts on Arbitrum and Polygon are displayed as USDT0; Optimism uses its legacy bridged USDT contract, not the separate USDT0 contract. Avalanche DAI is DAI.e. Other bridged representations carry bridge risk and may not be supported by your exchange. Confirm the selected network and contract before receiving funds.

Checkout and the payment-link form disclose whether an EVM token is issuer-native, bridged, or omnichain. Circle's USDC registry, Tether's supported protocols, and USDT0 deployments are the primary references. The public GET /api/checkout/assets endpoint returns supported EVM contracts, decimals, display symbols and disclosure text.

Solana USDC/USDT checkout requires an initialized, unfrozen associated token account for that mint and owner wallet. In Wallet settings, choose Check token accounts. Initialize missing accounts in your wallet; account storage and transaction fees require SOL. SettleBolt only checks readiness and never creates accounts or moves funds. Native SOL does not require a token account.

Every supported asset uses a locked checkout quote. Stablecoin amounts include the EUR exchange rate. Send the exact amount shown, on the specified network.

Automatic recovery or credit is not supported for payments sent on a different network or in a different token, including look-alike or bridged tokens with the same symbol. Contact the merchant with the transaction hash, actual network, token contract and amount. Do not send another payment until the merchant has reviewed the transfer. SettleBolt cannot move funds from the merchant wallet or guarantee recovery; a refund must be arranged separately with the merchant.

For Bitcoin, a transfer observed by our watcher before quote expiry can confirm within the following 24 hours. Checkout shows that confirmation is pending; Bitcoin settlement requires six confirmations, usually about an hour and sometimes longer. Receipts are periodically rechecked against the canonical chain. Receipts less than 144 blocks deep require verification within the last hour; older verified receipts remain in a bounded rotating audit. Any detected mismatch pauses Bitcoin acceptance. A detected reorganization pauses Bitcoin acceptance for review while retaining the original payment and order history; it does not reverse fulfilled orders or issue refunds. Acceptance resumes only after the same transaction output, address and amount are canonical with at least six confirmations and all scan and verification checks are current. If the watcher missed the broadcast, the transfer arrives later, or a replacement transaction was not observed in time, the merchant must review the receipt. Do not send a second payment while waiting.

Bitcoin quote amounts are reserved against earlier quotes. If no unused amount is available within the small rounding allowance, checkout asks you to use another payment method or contact the merchant. Bitcoin outputs that return funds to the sending wallet require review instead of automatic order completion.

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 creation does not require a real receiving wallet or consume the live link allowance. Demo amounts use fixed fixture rates, not market quotes: EUR/USD 1.10, ETH EUR 3,000, BTC EUR 60,000, SOL EUR 150 and TRX EUR 0.25.
• 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, switch to the selected network and sign the challenge. EOA, ERC-1271 and ERC-6492 ownership proofs are supported when that network's RPC is available. 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}.

Reusable live payment links offer an optional email receipt. Check ?Send one receipt to this email after this payment is verified? and choose ?Save receipt preference? before paying. The preference belongs to that checkout quote and session; it is not a marketing subscription or a saved customer profile. A receipt is attempted only after verified, attributed payment. Single-use store orders and invoices keep their existing store or invoice receipt flow. Receipt delivery is not guaranteed: successful or uncertain delivery attempts are not automatically repeated. The receipt preference expires after 7 days. The email address is cleared after the attempt or by scheduled cleanup when it expires; scheduled cleanup removes minimal deduplication and rate-limit records after 30 days from creation. This receipt is not a tax invoice.

Demo links simulate one successful payment per link; repeated simulation returns the existing result. Create another demo link to test another payment. Fixed positive amounts are required. Merchant-editable link expiry is not currently offered; checkout quote expiry is separate.

WooCommerce and Shopify order requests are single-use and keep their original amount, asset and network. Manage their cancellation in the store. They do not consume the reusable-link allowance. After a verified payment, WooCommerce checkout offers a return link to the store. Closed or replaced orders require merchant review of late receipts.

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 its line items. Quantities must be positive whole numbers. Sending requires a verified receiving wallet and a healthy payment watcher. Due dates expire at the end of the named day in UTC.

Sent means the invoice has been issued. Its separate email status shows whether the email provider accepted the message, failed, or has an uncertain result. Provider acceptance does not confirm arrival in the customer's inbox. Failed messages can be resent from the invoice detail page or POST /api/agent/invoices/:id/resend.

Invoice email limits: one attempt per invoice per 10 minutes, five per invoice per rolling day, and 500 per account per rolling day with active Pro or Business access (20 otherwise). Failed attempts also count.

Use the printable invoice view and your browser's Print to PDF action. Newly issued invoices preserve seller and customer billing details at issue time; older invoices identify when current profile details are being shown. Tax is not calculated or itemized, and no PDF attachment is emailed.

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, customer refunds are transfers you arrange from your wallet. Confirm the refund address and network with the customer; the displayed payer address may belong to an exchange or contract. Recording a refund in SettleBolt does not send funds.

Payment CSV export is available on Starter and higher. Customer CSV and analytics exports require Pro or Business. Business uses the same export formats as Pro.

Branding controls supported checkout, invoice, and receipt presentation. Custom branding is available on Starter, Pro and Business; one custom checkout domain requires Pro or 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.

Invoice and payment-link commands first show a preview with the amount, recipient and crypto network. Confirm or cancel within 10 minutes. Telegram has confirmation buttons; WhatsApp shows the exact confirm command to reply with. Repeated taps reuse the same request. Receiving must be available before a request is issued.

For example: send invoice to Alex alex@example.com for EUR 120.50 due 2027-07-16 using USDT on Tron. Use a complete email address or an exact saved customer name. Write amounts as 1234.50 or 1 234,50; ambiguous three-decimal/grouped values such as 1.234 are rejected. Use ISO dates or a written month, such as 16 July 2027.

Recent payments shows live receipts with their raw crypto amounts, network and invoice or link. A missing EUR valuation is marked unavailable. 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 settings expose the configured EVM, Bitcoin, Solana and Tron asset pairs. Each store selects one pair, and checkout is offered only when that pair and the store's registered webhook are ready.

General webhook creation requires paid Pro or Business access; paid Starter stores connect through WooCommerce. Existing endpoint recovery and delivery history remain available on every plan. Copy the signing secret once and verify every delivery.

POST /api/agent/invoices/:id/issue requires invoices:send and activates a draft without emailing the customer. It checks receiving readiness, snapshots invoice details, and returns the payable checkout URL with email.sent=false, email.skipped=true, and email.code=email_not_requested. Replays for sent, overdue or paid invoices do not send email or create another invoice.

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

For new live Solana receipts, payer_address is the verified transfer source or null, and payer_role is sender or unknown. fee_payer_address separately records the transaction fee payer, which may be a sponsor. Existing live Solana ledger rows with unproven source identity are marked unknown; historical immutable webhook payloads retain their original contents. Never infer a refund destination from these fields.

A Solana receipt's log_index is the recipient index in the complete transaction account-key list: static keys, then loaded writable and readonly addresses. Receipt identity also includes chain, token and transaction signature. External /payments/ingest is disabled; callers must not synthesize alternate receipt indexes.

X-SettleBolt-Event: payment.confirmed
X-SettleBolt-Event-Id: <opaque-event-id>
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.