Choose an order that resembles the business.
Choose a product the merchant sells in the ordinary course of business. The first person to judge the pilot should be able to see the price on the order, the payment on the invoice, the delivery record, and the entry the accountant receives. A QR code establishes only that the customer saw a payment request.
Consider a hypothetical consultancy that sells a fixed-scope research session to overseas business customers. Its invoices are denominated in US dollars, its staff work in the UK and its customers ordinarily receive a written confirmation before booking a time. The proposed pilot concerns one order through a specifically configured Bitcoin payment path. It does not establish that every customer location or payment method is supported.
Write the order’s commercial facts first: supplier entity, customer context, service description, price, currency, cancellation terms, and delivery process. Identify the applicable contract and record requirements for review. If the payment integration changes what the customer sees or when delivery becomes available, the commercial and technical descriptions must agree.
Choose a representative amount without making an unnecessary live payment. Initial development can use synthetic records or an approved test environment. Any later live acceptance exercise needs its own authority and defined exposure. The acceptance sheet should identify the environment clearly so a simulated result cannot be mistaken for evidence that a production payment succeeded.
Name the people involved. The merchant owns the customer promise. The implementation team owns the integration work within its scope. The person responsible for the receiving arrangement handles its operational controls. The bookkeeper or accountant specifies the handoff information. One successful developer demonstration should not stand in for acceptance by all of them.
BitSettle belongs in this process as a discussion scoped to the individual merchant. Confirm the proposed merchant’s availability, configuration, support, and written scope. Upstream software capability, a local implementation, and a service available to a particular merchant are different facts. The pilot should establish the relevant facts instead of borrowing a broad catalog of possible payment methods.
Keep capability, configuration, tests, and availability in separate columns.
Start with what the underlying software supports, using its current documentation. Then record what the proposed installation has enabled. Next record what was actually tested and the observed result. Finally, state what the merchant is authorized and operationally ready to offer. These columns prevent a feature mentioned in documentation from becoming an unsupported checkout promise.
For an on-chain Bitcoin pilot, identify the receiving arrangement, invoice expiry, confirmation policy, and relevant permissions. Do not publish sensitive details in the acceptance sheet. The operator should confirm that the configuration matches the intended custody and security model. A claim about where signing keys are held must describe the actual setup.
If Lightning is proposed, it needs a separate availability and operational review. Receiving capacity, access, recovery, and the actual integration cannot be inferred from an on-chain test. The same applies to USDT: name the network, supported asset configuration, and relevant issuer exposure. A successful Bitcoin order does not verify another asset or network.
BTCPay’s wallet documentation describes different capabilities, including arrangements that can spend funds. This is why a general non-custodial description should not replace a configuration review. The merchant needs to understand who controls what, what the software can do, and which responsibilities remain with the business and its operators.
Identify the boundary of the pilot. It might cover one currency, one asset, one network, one service, and one delivery action. That is a legitimate starting point. Record excluded methods and unresolved conditions so the result is not later described as an all-rails launch. A small test is useful when its limits are clear.
Define the release rule before testing. What evidence must exist before the order is treated as paid and delivery is permitted? Who may review an exception? What happens when the provider cannot be reached? The business should choose the policy with its responsible team rather than letting the first convenient event name decide when a customer receives the service.
Trace the order through payment and fulfillment.
Give the merchant order a stable reference before requesting a provider invoice. Preserve the server-authoritative price and currency. The provider invoice should be linked to that order and the intended payment method. A customer’s browser may display progress, but it should not be the source of truth for the amount owed or the final payment decision.
Test invoice creation and recovery. If the customer refreshes or returns later, can the integration recover the existing order rather than create a second payable invoice? If a network request times out, can staff identify whether an invoice exists? An uncertain response should lead to recovery or review, not an automatic instruction to start again and risk duplicate payment.
Then test the observation and verification path. The system must distinguish a reported payment from the evidence required by the configured release policy. The official BTCPay integration guide describes validating notifications and checking relevant invoice information. The installed integration needs its own evidence that those checks are present and work as intended.
Keep fulfillment as a separate action. For the hypothetical consultancy, payment may permit access to scheduling, but a paid order is not a booked appointment. A calendar interaction is not a confirmed appointment unless the responsible system verifies it. The acceptance sheet should record payment, scheduling access, and booking confirmation as separate milestones.
Test repetition at the boundaries. Deliver the same synthetic payment notification twice and confirm that the order receives only the intended single release. Refresh the paid view and confirm that it does not create another entitlement. Lose the browser callback and check whether the user can recover the authoritative status without paying again.
Capture evidence at every stage: order reference, invoice reference, relevant state, verification result, and fulfillment identifier. Use redacted logs and controlled test data. A screen recording shows what the customer saw. Keep the server decision and the fulfillment record with it.
Include one exception and the accountant’s handoff.
A pilot that only tests the easiest successful payment leaves the support process largely unexamined. Choose one controlled exception that matters to the business, such as a late payment, or a duplicate notification. Write the expected result first: whether fulfillment remains held, who reviews it, and what the customer is told.
For a late-payment exercise, preserve the original quote and expiry, the actual payment evidence, and the customer terms. The software state does not by itself decide the customer’s entitlement or the merchant’s commercial response. The support person needs a clear route to an authorized decision, with no unsupported claim that funds are lost, refundable automatically, or available for the merchant to keep.
Test the customer message using only known facts. A useful message can state that the payment is under review, identify the order, and explain the next check. It should not claim that a refund has been sent when only a request exists. Set the update expectation according to the actual support arrangement rather than inventing a round-the-clock commitment.
Now give the bookkeeper the pilot record. Can they connect the customer order, provider invoice, payment quantity, relevant currency value, fees, and delivery status? Can they distinguish a refund or internal wallet movement from a new sale? Ask for a practical acceptance response, including any missing fields or unclear date conventions.
Preserve the source export and a short field dictionary. Record whether a date is invoice creation, payment observation, settlement, or another event, and identify the time zone. The accounting professional should determine the relevant period and treatment for the merchant. A CSV export is supporting evidence, not a completed set of accounts or a tax return.
Add the exception outcome to the handoff. If the payment remains under review, it should remain visibly unresolved in the accountant’s pack. Do not force a balanced total by classifying an unexplained amount as revenue. The pilot has taught something useful if it reveals a missing record or policy before real customer volume makes the gap expensive.
Decide what passed and what happens next.
Use three outcomes for each acceptance item: passed with evidence, failed with an assigned correction, or unresolved because the necessary test or decision has not occurred. Avoid a single green label for the entire project. An invoice can display correctly while recovery, support, or accounting remains unfinished.
The acceptance sheet should identify the exact version and configuration tested, the environment, the date, and the responsible reviewer. A later change to payment methods, provider permissions, expiry policy, or delivery integration may invalidate part of the result. Record which tests need repeating when those assumptions change.
Set expansion criteria. Before adding another asset, network, service, or customer market, identify the additional configuration, legal, operational, and accounting questions. The original pilot can supply a reusable method, but it does not automatically prove the expanded arrangement. Treat a new feature as a defined increment with its own evidence.
Agree the operating handoff. Who monitors unresolved orders? Who can disable a payment option if it stops behaving as expected? Who authorizes refunds and handles customer questions? Where are the records and escalation contacts? These responsibilities should appear in the written scope and operating procedure, with availability matching the actual service commitment.
Rehearse an unavailable-provider response as part of readiness. The customer should see a clear status and a safe recovery path. Staff should preserve existing orders and avoid improvising new receiving instructions. Any alternative payment method should be pre-approved and tested for the relevant order, especially where a customer may already have sent funds.
A successful pilot ends with a modest but valuable statement: this defined workflow passed these checks in this environment, with these responsibilities and these remaining limits. Wider merchant availability requires the additional decisions and verification actually needed. That is a firmer basis for accepting customer money than a feature list or a promising first screenshot.
| Stage | Required evidence | Pass condition | Unresolved example |
|---|---|---|---|
| Order and invoice | Stable references, price, and configured method | Correct binding and safe recovery | Timeout without recoverable status |
| Payment | Authoritative invoice and payment checks | Release policy met once | Observation without required verification |
| Fulfillment | Delivery or appointment record | Intended action completed once | Paid but no confirmed booking |
| Exception | Decision record and customer message | Held and resolved under approved policy | No assigned reviewer |
| Accounting | Source records and field definitions | Bookkeeper can reconstruct the order | Unexplained difference remains |
The whole picture
The Bitcoin Lawyer take
Approve the pilot for the order and exception that actually passed. Name the person responsible for any untested refund or delivery step before extending the result to other products.
For a BitSettle (opens in a new tab) discussion, bring that order and its acceptance sheet. A bounded pilot can reveal whether the proposed arrangement works and what still needs attention. The useful outcome is an evidenced operating decision, including a decision to wait, rather than a claim that every possible payment method is ready.


