Written by DROPS.ST.
Choose a clear catalogue pricing currency and distinguish it from the amount requested at crypto checkout. A product price, an approximate conversion and a current payment request do different jobs. DROPS combines the catalogue with BTC/XMR checkout and order status, helping customers move from a product decision to the payment instructions for that particular order.
Keep three numbers from becoming one vague price
The catalogue price tells a customer what the product costs on your stated basis. A displayed conversion can help them understand its approximate coin value. The actual payment request tells them what to send for an order under the conditions shown there.
If those numbers are presented as interchangeable, customers may copy an old amount from a product page or support message. Label the currency explicitly and make the current order instructions the place to resolve the payment amount.
The Bitcoin developer guide on pricing orders describes why pricing in a national currency and accepting Bitcoin requires a conversion. It does not mean every shop uses the same quote duration, rate source or update behaviour.
See the difference in a worked example
The following figures are illustrative and are not current cryptocurrency prices.
| Stage | Example | Meaning |
|---|---|---|
| Catalogue | Accessory pack: CAD 48 | The shop’s stated product price |
| Informational conversion | At CAD 60,000 per BTC, CAD 48 equals 0.0008 BTC | Arithmetic based on an example rate |
| Final order | Products CAD 48 plus delivery CAD 6 | Order value CAD 54 before any separately applicable tax |
| Payment calculation | CAD 54 ÷ CAD 60,000 per BTC | 0.0009 BTC under that example rate |
A customer who copied 0.0008 BTC from the product example would not be using the final order amount in this scenario. The difference is delivery, even before any rate change enters the picture.
State what the final total includes. The cart-total guide covers the product, discount and fulfilment breakdown before conversion.
Choose a basis your team can explain
Pricing directly in coin units may suit a particular operation, but it means the catalogue-currency equivalent changes as the exchange rate changes. Pricing in a conventional currency keeps that displayed product basis familiar, while the coin payment amount may vary between requests.
This is an operating and customer-explanation choice, not a reason to speculate on an asset. Consider the currency used for product costs, accounting and customer expectations, then get the relevant commercial advice for your shop.
Do not publish “locked price” wording unless the actual payment request defines what is locked and for how long. Where a request has a validity period, show the real period and explain the next step if it ends. Avoid turning an illustrative countdown into a platform promise.
Give customers wording they can act on
A useful explanation might say: “Product prices are shown in CAD. At crypto checkout, follow the current amount and instructions for your order.” Add the actual treatment of delivery, fees and quote validity where relevant.
Do not bury the asset name in a QR image alone. Customers should be able to identify BTC or XMR and read the amount. DROPS’s payment panel includes a QR display and separate copying of the address and amount, helping the customer use the current instruction rather than transcribing a message.
Review one product all the way to payment
In a demo, inspect a product price, add a fulfilment charge where applicable and read the payment request. Ask how the configured setup handles quote refreshes and expired instructions before writing customer-facing promises.
Use the crypto fee examples to keep additional costs distinct from the product price.
See DROPS catalogue, checkout and payment status together and make the amount customers are asked to pay clear at every step.