Optional cookies require your permission.Privacy & cookies

Settlement technical reference

Make the payment state inspectable.

Which event permits a merchant to release an order? An invoice can exist before any payment arrives. Decide how the system will detect payment, verify its status, and match it to the order before relying on a webhook to trigger fulfillment.

01 / Settlement technical reference

Start with the decision.

Separate a technical reference from a service commitment.

BitSettle is our Bitcoin and USDT settlement rail, built on BTCPay Server with additional USDT payment-method integrations. Merchant deployments are agreed individually. Managed setup, hosting, monitoring, and maintenance must be identified in the merchant’s written scope. The existence of a configuration option is not a promise that every wallet, storefront, or network combination has been tested for a new merchant.

Bitcoin Lawyer’s own checkout supports card, Bitcoin on-chain, and USDT. Lightning remains deferred. The Lightning material here explains a separate implementation decision; it does not offer Lightning payment on the corporate website. Commercial fees for a merchant deployment are quoted after the strategy session.

Back to contents

02 / Settlement technical reference

Limits, responsibilities and the next step.

Compare the receiving model before the software.

Managed receiving, a custodial processor, and a manual wallet workflow assign different work to your team. Compare the actual proposal and provider contract. Product names alone do not establish custody, price, or settlement terms.

Manual receiving can be workable for a small number of invoices with a disciplined review process. Automation becomes more valuable when orders, networks, or staff handoffs make that process difficult to inspect. A custodial arrangement may provide a payout or service the business needs; assess that benefit alongside the control it requires you to give up.

Compare the complete operating cost and the failure you can recover from. Do not apply a historical competitor percentage, a universal settlement-time promise, or “no chargebacks” language to every product. A blockchain payment does not erase contractual disputes, token issuer powers, or the obligation to handle a customer problem.

Scroll to compare all columns

Compare the receiving model before the software.
DecisionManaged receiving to your walletCustodial processorManual wallet workflow
Who controls the funds?The receiving destination belongs to the merchant. Confirm that the server configuration cannot sign transfers and that the merchant can recover and spend independently.The provider controls the balance or payout process under its agreement. Check withdrawal, review, reserve, and suspension provisions.The merchant controls the wallet and must also protect the process used to issue destinations and identify receipts.
What does it cost?Price setup, hosting, monitoring, maintenance and support, plus network costs. A proposal without a percentage charge still has operating costs.Read transaction, conversion, withdrawal, and payout charges together. Obtain the actual schedule for the product, country, and settlement method.Price staff time, reconciliation, support, and error handling alongside wallet and network costs. A free wallet is not a cost-free payment operation.
When is an order ready?The application checks the configured invoice and settlement rule, then records one fulfillment decision.The provider’s payment status and payout availability can be different milestones. Define which one the business needs before fulfillment.Someone checks the chain, amount and destination, matches the invoice, and authorizes release. Document who can make that decision.
Which assets are accepted?Only the methods and exact contracts or mints configured and tested for the deployment.Only the assets, networks, and customer locations accepted by the current product and account.Only what the wallet can receive and the team can identify reliably. Supporting an asset in a wallet does not create invoice matching.
How are refunds handled?A receive-only integration cannot sign refunds. The authorized merchant wallet controller completes the agreed refund process.Follow the provider’s available refund mechanism, fees, and terms. Confirm whether refunds return the original asset or another amount.The wallet controller sends the transfer and the team reconciles it to the original order and customer instruction.
What can interrupt receipt?Endpoint failure, exhausted address capacity, chain conditions, or a software fault. Assign monitoring and reconciliation ownership.Provider outages, account restrictions, payout holds and supported-network changes, alongside the underlying asset risks.Missed payments, reused destinations, spreadsheet errors, unavailable staff, and wallet-access problems.
What remains your responsibility?Wallet recovery, commercial terms, support decisions, refund authorization, and a verified handover from the operator.Understanding the provider agreement, account compliance, customer support, and a usable export of payment records.All of those business decisions plus the invoice, monitoring, and reconciliation workflow itself.

Decision

Who controls the funds?

Managed receiving to your wallet
The receiving destination belongs to the merchant. Confirm that the server configuration cannot sign transfers and that the merchant can recover and spend independently.
Custodial processor
The provider controls the balance or payout process under its agreement. Check withdrawal, review, reserve, and suspension provisions.
Manual wallet workflow
The merchant controls the wallet and must also protect the process used to issue destinations and identify receipts.

Decision

What does it cost?

Managed receiving to your wallet
Price setup, hosting, monitoring, maintenance and support, plus network costs. A proposal without a percentage charge still has operating costs.
Custodial processor
Read transaction, conversion, withdrawal, and payout charges together. Obtain the actual schedule for the product, country, and settlement method.
Manual wallet workflow
Price staff time, reconciliation, support, and error handling alongside wallet and network costs. A free wallet is not a cost-free payment operation.

Decision

When is an order ready?

Managed receiving to your wallet
The application checks the configured invoice and settlement rule, then records one fulfillment decision.
Custodial processor
The provider’s payment status and payout availability can be different milestones. Define which one the business needs before fulfillment.
Manual wallet workflow
Someone checks the chain, amount and destination, matches the invoice, and authorizes release. Document who can make that decision.

Decision

Which assets are accepted?

Managed receiving to your wallet
Only the methods and exact contracts or mints configured and tested for the deployment.
Custodial processor
Only the assets, networks, and customer locations accepted by the current product and account.
Manual wallet workflow
Only what the wallet can receive and the team can identify reliably. Supporting an asset in a wallet does not create invoice matching.

Decision

How are refunds handled?

Managed receiving to your wallet
A receive-only integration cannot sign refunds. The authorized merchant wallet controller completes the agreed refund process.
Custodial processor
Follow the provider’s available refund mechanism, fees, and terms. Confirm whether refunds return the original asset or another amount.
Manual wallet workflow
The wallet controller sends the transfer and the team reconciles it to the original order and customer instruction.

Decision

What can interrupt receipt?

Managed receiving to your wallet
Endpoint failure, exhausted address capacity, chain conditions, or a software fault. Assign monitoring and reconciliation ownership.
Custodial processor
Provider outages, account restrictions, payout holds and supported-network changes, alongside the underlying asset risks.
Manual wallet workflow
Missed payments, reused destinations, spreadsheet errors, unavailable staff, and wallet-access problems.

Decision

What remains your responsibility?

Managed receiving to your wallet
Wallet recovery, commercial terms, support decisions, refund authorization, and a verified handover from the operator.
Custodial processor
Understanding the provider agreement, account compliance, customer support, and a usable export of payment records.
Manual wallet workflow
All of those business decisions plus the invoice, monitoring, and reconciliation workflow itself.
Back to contents

Prepare the deployment in six steps.

  1. Describe the order

    Record the store, order currency, typical amount, fulfillment event, and customer support owner. Agree what happens to partial, late, or excess payments before configuring the checkout.

  2. Identify the deployment

    Record the BTCPay instance, store, software and plugin versions, enabled payment-method identifiers, endpoint provider, and owner of maintenance. Use the target instance’s API documentation because installed plugins can change the available methods.

  3. Verify receiving control

    Supply only the public receiving information required by the selected method. Compare a derived or reserved destination with the merchant’s own wallet. Preserve the merchant’s independent recovery and signing arrangements.

  4. Approve the exact assets

    Pin the chain, contract or mint, decimals, receiving mode, expiry, and settlement rule. Enable only the methods approved for this deployment. A ticker alone is insufficient to identify an asset.

  5. Test the full order

    Use an agreed small test, inspect the invoice, and wallet evidence, and verify the downstream fulfillment. Include duplicate delivery and payment exceptions in the acceptance record.

  6. Hand over operation

    Name the people who handle endpoint alerts, unsettled orders, refunds, and customer communication. Record backup, restore, and credential-replacement procedures before increasing volume.

Back to contents

Use explicit network and asset identifiers.

These method identifiers and decimal precision describe the BitSettle configuration reference. They identify integration settings, not receiving addresses. Verify the active invoice and deployed allowlist before sending or accepting funds.

Scroll to compare all columns

Use explicit network and asset identifiers.
Network / methodAdapter and precisionAsset distinction to retain
TRON / USDT-TRONTRON chain API; 6 decimalsMatch the configured TRC-20 contract and its confirmed transaction record.
Ethereum / USDT-ETHEREUMEVM JSON-RPC; 6 decimalsMatch the mainnet contract and Transfer logs on the selected chain.
Polygon / USDT-POLYGONEVM JSON-RPC; 6 decimalsVerify the exact deployed token representation; do not infer it from a USDT label.
Arbitrum One / USDT-ARBITRUMEVM JSON-RPC; 6 decimalsVerify the exact contract and any bridge or representation assumptions.
BNB Smart Chain / USDT-BSCEVM JSON-RPC; 18 decimalsDo not apply the six-decimal assumption used by the other listed methods. Verify issuer or pegged-asset provenance separately.
Avalanche C-Chain / USDT-AVALANCHEEVM JSON-RPC; 6 decimalsKeep the configured USDT contract distinct from legacy USDT.e.
Solana / USDT-SOLANASPL token adapter; 6 decimalsMatch the mint, destination token account, owner, and required commitment.

Network / method

TRON / USDT-TRON

Adapter and precision
TRON chain API; 6 decimals
Asset distinction to retain
Match the configured TRC-20 contract and its confirmed transaction record.

Network / method

Ethereum / USDT-ETHEREUM

Adapter and precision
EVM JSON-RPC; 6 decimals
Asset distinction to retain
Match the mainnet contract and Transfer logs on the selected chain.

Network / method

Polygon / USDT-POLYGON

Adapter and precision
EVM JSON-RPC; 6 decimals
Asset distinction to retain
Verify the exact deployed token representation; do not infer it from a USDT label.

Network / method

Arbitrum One / USDT-ARBITRUM

Adapter and precision
EVM JSON-RPC; 6 decimals
Asset distinction to retain
Verify the exact contract and any bridge or representation assumptions.

Network / method

BNB Smart Chain / USDT-BSC

Adapter and precision
EVM JSON-RPC; 18 decimals
Asset distinction to retain
Do not apply the six-decimal assumption used by the other listed methods. Verify issuer or pegged-asset provenance separately.

Network / method

Avalanche C-Chain / USDT-AVALANCHE

Adapter and precision
EVM JSON-RPC; 6 decimals
Asset distinction to retain
Keep the configured USDT contract distinct from legacy USDT.e.

Network / method

Solana / USDT-SOLANA

Adapter and precision
SPL token adapter; 6 decimals
Asset distinction to retain
Match the mint, destination token account, owner, and required commitment.

A configured token is not necessarily issued directly by Tether on that network. Check Tether’s protocol documentation and the relevant network’s asset provenance for the actual contract.

Back to contents

Read token identifiers as a dated reference.

This table comes from the BitSettle documentation, retrieved on 17 October 2026. That documentation is labeled as verified on 1 July 2026, so treat each entry as a dated reference, not a fresh check. The values are token contracts or a token mint. They are not merchant receiving addresses and are never instructions for sending a payment.

This snapshot does not establish current issuer support, current bridge arrangements, or the asset enabled on a particular invoice. Compare the exact network and identifier with the deployed allowlist and the current issuer or network documentation. In particular, a BNB Smart Chain pegged representation must not be described as interchangeable with direct Tether issuance; its custody and backing require separate review. Polygon and Arbitrum representations also need their own provenance check.

A customer pays the receiving destination shown on the approved invoice, using its specified asset and network. Sending funds to a token contract or mint from this table is not a payment to the merchant. Historical confirmation ranges are deliberately omitted: the installed adapter, observed chain state, and agreed release policy govern a deployment.

Scroll to compare all columns

Read token identifiers as a dated reference.
NetworkContract or mint (dated reference)Recorded decimals
TRONTR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t6
Ethereum0xdAC17F958D2ee523a2206206994597C13D831ec76
Polygon0xc2132D05D31c914a87C6611C10748AEb04B58e8F6
Arbitrum One0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb96
BNB Smart Chain0x55d398326f99059fF775485246999027B319795518
Avalanche C-Chain0x9702230A8Ea53601f5cD2dc00fDBC13d4dF4A8c76
SolanaEs9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB6

Network

TRON

Contract or mint (dated reference)
TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
Recorded decimals
6

Network

Ethereum

Contract or mint (dated reference)
0xdAC17F958D2ee523a2206206994597C13D831ec7
Recorded decimals
6

Network

Polygon

Contract or mint (dated reference)
0xc2132D05D31c914a87C6611C10748AEb04B58e8F
Recorded decimals
6

Network

Arbitrum One

Contract or mint (dated reference)
0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9
Recorded decimals
6

Network

BNB Smart Chain

Contract or mint (dated reference)
0x55d398326f99059fF775485246999027B3197955
Recorded decimals
18

Network

Avalanche C-Chain

Contract or mint (dated reference)
0x9702230A8Ea53601f5cD2dc00fDBC13d4dF4A8c7
Recorded decimals
6

Network

Solana

Contract or mint (dated reference)
Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB
Recorded decimals
6
Back to contents

Receiving modes have different recovery requirements.

Address pools

Reserve a receiving destination for an invoice and retain that association. Coordinate allocation across applications using the same wallet; two independent stores must not silently assign the same pool entry. Monitor available capacity and fail clearly when the pool cannot supply a destination.

EVM public-key derivation

The BitSettle configuration reference describes an account public key at m/44'/60'/0' and receive derivation below m/44'/60'/0'/0/n. Confirm the actual wallet can derive and later spend from each proposed address before using this mode. These paths are a configuration reference, not a universal hardware-wallet compatibility claim. Public keys can reveal transaction relationships even though they cannot sign.

Solana token accounts

A wallet owner and an SPL token account are different addresses. The receiving configuration must identify the mint, token account, and its owner. A pre-created pool of appropriate associated token accounts is one design; check account creation and recovery responsibilities. Do not import EVM derivation assumptions into Solana.

Bitcoin and Lightning

BTCPay’s Bitcoin wallet configuration can use public receiving information while the merchant retains signing control. Lightning has a separate node and channel model, including receiving capacity and recovery. A watch-only Bitcoin wallet does not by itself make Lightning available.

Back to contents

Create the invoice on the server and retain the link.

Create an invoice with POST to /api/v1/stores/{storeId}/invoices. Read one with GET on the same path followed by /{invoiceId}. Confirm the payload, permissions, and plugin-specific payment-method fields against the target instance’s /docs. Keep credentials on the server and scope them to the required store and operations.

Persist your order reference before handing the customer to the returned checkoutLink. Retain the provider invoice ID, store, currency, expected amount, and selected payment method with that order. An uncertain create response needs reconciliation before retrying a write; do not create a second payable invoice simply because the first request timed out.

A return URL improves navigation after checkout. It must not mark an order paid. The server should decide payment state independently and show an honest pending or review state while confirmation remains incomplete.

Back to contents

Treat webhooks as authenticated input.

Register an HTTPS callback for the intended store and keep its secret separate from the API credential. Verify the BTCPay HMAC-SHA256 signature against the exact raw request body before using the event. Reject an invalid signature. Do not reconstruct JSON and then verify a different byte sequence.

Relevant invoice events include InvoiceReceivedPayment, InvoiceProcessing, InvoiceExpired, InvoiceSettled, InvoiceInvalid, and InvoicePaymentSettled. They report different points in the lifecycle. A payment observed or processing is not automatically a completed order. Retain delivery identifiers and make processing safe when the same event arrives twice or arrives out of order.

Bind the notification to an existing order and the expected store. Reconcile against the provider invoice when deciding fulfillment, including status and additionalStatus. A shared store can emit events for other businesses or applications; never create a corporate order merely because a callback arrived.

Back to contents

Write down the release rule.

For a USDT invoice, compare the selected method, contract or mint, destination, quoted amount, detected payments, and settlement state. The configured decimal precision matters to every amount comparison. A transaction hash on its own does not establish that the correct invoice was paid.

Check chain-specific confirmation settings, including TRON solidification and Solana finalized commitment, against the deployed adapter and the merchant’s accepted policy. Do not apply an old confirmation range from a marketing page to a new deployment. Record how the adapter handles chain reorganizations, conflicting endpoint responses, and delayed indexing.

Keep partial, late, overpaid, invalid, and manually marked cases visible. Define whether a case can be released automatically or needs review. Persist the release decision so a repeated webhook cannot trigger a second receipt, booking link, or shipment. Reconciliation should restore a missing notification without inventing a second payment.

Back to contents

Preserve the records that make recovery possible.

Preserve the records that make recovery possible.
Operating concernEvidence or procedure to retain
Endpoint failureMonitor the chain endpoint and invoice processing separately. Use bounded retries, alert on stalled invoices and avoid treating a timeout as proof of non-payment.
Order reconciliationRetain order, invoice, store, method, token identity, amount, destination, transaction reference, and fulfillment status in a consistent export.
Backup and restoreTest restoration of application records, invoice data, and receiving configuration. Wallet recovery is a separate responsibility; a website backup is not a wallet backup.
RefundsReceive-only infrastructure cannot sign an outgoing USDT refund. Confirm the intended recipient and network under the refund process, then have the authorized wallet controller execute it.
Token riskKeep issuer, bridge, network, and wallet risks visible. Self-custody does not remove the powers or limitations of a centrally administered token.
ChangesRecord versions, asset allowlists, and confirmation settings. Test the affected method before changing the production fulfillment rule.

Keep the approved deployment record with the operating procedures. A public technical reference does not change an existing service agreement, authorize a configuration change, or establish compatibility for a new merchant.

Back to contents

Before you decide

Common questions.

Is BitSettle’s public documentation a complete API specification?

No. Use the Greenfield documentation on the target BTCPay instance and the installed plugin’s versioned contract for request and response details. This reference explains the integration decisions and example method identifiers; it does not invent a separate public Bitcoin Lawyer payment API.

Can a single webhook support several USDT networks?

Yes, when the application maps each invoice to the expected store and exact payment method and validates the appropriate settlement data. Separate network labels do not require separate callback URLs, but each enabled method still needs a clear acceptance rule.

Does a receive-only setup eliminate the need for a refund procedure?

No. Customer support and any applicable refund obligations still exist. The merchant’s wallet controller must handle an outgoing transfer through the agreed process because a receive-only integration cannot sign it.

Does this guide mean Lightning is available on Bitcoin Lawyer?

No. Lightning remains deferred on the corporate site. Enabling it requires a separate operational decision and verified receiving capacity.

Official sources and further reading8 references