Written by DROPS.ST.
Compare payment flows by what the customer pays, what the merchant receives, who performs verification and who controls the funds. A checkout method, a settlement asset and a shop account balance are different things.
DROPS brings the payment decision into a working shop with supported Bitcoin and Monero paths, customer context and order records. The website and connected Telegram shop use the same catalogue and order system. That gives you a practical way to assess the customer experience and staff handoff together.
It does not establish automatic CAD settlement, stablecoin acceptance or a particular custody model. Evaluate those separately from the visible shop controls.
Separate acceptance from settlement
Acceptance is the method the customer uses to pay. Settlement or merchant receipt describes what the business receives and where. Another service may perform conversion or transfer after payment.
Also identify the pricing currency used for the order and accounting record. An amount displayed in a currency does not prove that a bank receives that currency.
Avoid choosing a system from a coin logo alone. Follow the payment and responsibility from the customer through to the merchant's actual receipt.
Use a payment-flow comparison
| Decision | Evidence to request | What it prevents |
|---|---|---|
| Customer payment | Supported asset, network and instructions | Assuming every crypto asset works |
| Merchant receipt | Received asset, destination and responsible party | Confusing checkout with bank settlement |
| Conversion | Separate service, approval and stated charges | Inventing automatic conversion |
| Verification | Requester, purpose and approved business scope | Treating signup as provider clearance |
| Fund control | Signing, transfer and recovery responsibilities | Treating settings access as custody proof |
| Order handoff | Matched order and payment evidence | Treating detection as completed fulfilment |
| Receipt timing | Current cadence, minimums and pending amounts | Assuming every paid order becomes an immediate bank deposit |
Record confirmed facts and unresolved questions. This is an original evaluation worksheet, not a description of a specific gateway's terms.
Compare the roles, not just the labels
A gateway may process an invoice, convert an asset or arrange settlement, but its exact services and merchant conditions depend on its documented offering. A shop-controlled interface may give the operator settings without giving them exclusive control of private keys.
Ask who can sign transfers, change receiving destinations, restrict access and recover funds. Obtain evidence appropriate to the proposed arrangement; a marketing label cannot answer those questions.
FINTRAC distinguishes payment intermediaries and virtual-currency services from the specified own-goods payee exception. The actual activities and fund flows matter; neither the word “gateway” nor “wallet” settles the analysis. FINTRAC: money services businesses.
Keep software signup, financial-provider review and buyer eligibility separate. A supported asset or checkout setting does not establish approval for the merchant's products, location and activity.
Hypothetical example: a CAD price, a BTC receipt
A fictional merchant prices an order in CAD, accepts BTC and receives BTC. Its recorded sale and Bitcoin receipt are related, but no CAD bank deposit has occurred.
If the merchant wants conversion, it must identify a separately permitted service and its actual terms. It cannot infer automatic CAD settlement from the original CAD price or completed order.
This comparison does not demonstrate a DROPS conversion feature or recommend a provider.
For relevant taxable Canadian transactions, CRA guidance requires valuation and supporting records appropriate to the transaction. A later conversion or deposit does not substitute for that record. CRA: crypto-asset GST/HST guidance.
Keep account balances and confirmation distinct
A shop's customer account balance is not automatically a blockchain wallet or a cash-out entitlement. Understand the documented credit, top-up, use and refund rules. Wallet-assisted checkout is an adjacent shop decision, not proof of bank settlement.
Likewise, a payment indication does not establish that the correct order can proceed. Inspect the supported evidence and approved exception process. Bitcoin confirmations and Monero confirmations address the customer-status experience; no fixed confirmation timing is promised here.
Refund denomination, authority and completion mechanics require separate evidence. Do not assume a refund button initiates an on-chain transfer or that changing an order status reverses a payment.
Assess the complete shop flow with DROPS
Choose DROPS when BTC/XMR payment paths should sit beside the menu, customer context and order records rather than separate payment conversations. That connected shop experience gives the team concrete information to review while external conversion, provider approval and custody questions remain explicit.
Explore DROPS and open the demo shops. Compare the visible product-to-order journey with this worksheet. Use an approved, unfunded demonstration for payment-state questions and require separate evidence for any settlement or custody promise.