First 30 Days After Going Live with Crypto Checkout: An Operations Playbook for Merchants

Most merchants treat crypto checkout go-live as the finish line. It isn’t. The first 30 days are when you find the edge cases your gateway docs glossed over, build the SOPs that turn a payment surface into an ops process, and decide whether to roll crypto out further or quietly turn it off.

This is a four-week playbook for the merchant ops lead, or the solo founder doing ops on a Tuesday afternoon. By day 30 you should have a daily reconciliation routine, a support script library, a metrics dashboard, and a kept-or-killed call backed by data instead of vibes.

Why the first 30 days set your operational baseline

A crypto checkout button is roughly 10% of the integration. The other 90% is whether callbacks land reliably, whether your bookkeeper knows where income posts, whether your support agents can handle a wrong-network refund, and whether you can prove the conversion lift to your CFO. Most merchants who quietly disable crypto in month two are killing the ops process, not the payment surface.

The four weeks map to four things you need to nail, in order: monitoring, reconciliation, customer support, and metrics. If you used the selection framework before launch, this is the operational follow-on that turns the choice into a real workflow.

Week 1: monitoring, alerts, and the first transaction

Week one has one job: prove the plumbing works before real customers find the cracks. Don’t run a launch announcement yet. Test, instrument, and watch.

Callback health check

Callbacks are the heartbeat of the integration. If they fail silently, your store shows “unpaid” on orders that already settled on chain, and your inbox fills up. The first time a callback quietly fails at 2am, you find out by being yelled at by the customer at 9am. Set the alert on day one.

Verify three things end-to-end:

1. Delivery confirmation. Every test order should produce a callback your store actually receives. Cross-check your server’s inbound request log against the order list in the gateway dashboard.
2. Retry behavior. Deliberately return a 500 from your endpoint on a test order. Confirm that you can recover the order, either by waiting for the gateway’s retry or by re-pulling the order status via the API.
3. Signature verification. Aurpay signs callbacks with HMAC-SHA256 over {date} | {callback_url} using your callback secret, delivered in the Callback-Token, Date, and Signature headers. Reject anything with a bad signature and log the rejection so an attack would actually show up.

Realistic expectation: callbacks occasionally fail. Network blips, brief deploys, rate limits all happen. The goal is automatic retry plus a fallback that polls the order status via the API for anything that did not get a callback.

First test order from a friendly user

Do not let your first real transaction be a stranger. Run a checkout end-to-end with a small live amount — $5 to $20 in USDT TRC-20 is plenty — using your own wallet, then a co-founder’s, then a beta customer who knows you’re testing. Check that:

• The order moves to paid in your admin within the expected confirmation window.
• The order confirmation email goes out, and the wallet address shows up correctly in records.
• Your fulfillment workflow (download link, shipping label, calendar booking) triggers exactly like it would for a card order.
• You can find the on-chain transaction hash from your order detail page in under 30 seconds. If you can’t, your support agents won’t be able to either.

Routing alerts to your ops team

Configure two alert channels before any volume hits the system. First, a dedicated #crypto-ops Slack channel (or Discord) wired to your own callback receiver, so every successful payment, every callback your endpoint rejected, and every manual refund you initiate produces an in-channel ping. Quiet on day one, useful on day fifteen. Second, an email distribution list like [email protected] for daily digest summaries and high-severity events: a refund over $500, a callback failure rate above 5%, or a large order over your AOV threshold. Two people minimum on the list.

End-of-week-one deliverable: a server log with at least 10 successful test callbacks, a documented procedure for re-pulling order status via the API when a callback is missed, and a one-page runbook your support lead can read in five minutes.

Week 2: building the daily reconciliation routine

Once callbacks are stable, week two shifts from watching every transaction to watching the daily totals. The goal is a 10-minute morning routine your bookkeeper can run without asking you a question.

Daily wallet balance vs gateway report

Each morning, pull two numbers and compare them. First, the previous day’s net new inflow into your destination wallet, from the block explorer or wallet UI. Second, the previous day’s “settled” total in the gateway dashboard report. These should match within rounding. Any meaningful gap means a callback did not arrive, an order didn’t sync, or a customer overpaid and triggered a partial reconciliation hold. Investigate same day. Week-old gaps are nightmares to unwind.

Tagging crypto income in QuickBooks Online or Xero

Don’t dump crypto income into your generic “Sales” account. Set up a chart-of-accounts pattern that lets you slice crypto separately for the rest of the year:

1. Income: a sub-account of Sales called Sales — Crypto, broken into USDT, USDC, BTC, ETH if volume warrants.
2. Asset: a current-asset account per wallet you hold, e.g. Crypto Wallet — USDT (TRC-20) on the balance sheet.
3. Fees: the 0.8% per transaction processing fee posts to a Crypto Processing Fees expense account, parallel to your Stripe fees line.

If your bookkeeper has never handled crypto, share the actual fee math vs cards as background. The fee structure is simpler than a card processor, but the asset-side treatment is unfamiliar to most generalist accountants.

Currency-of-record decision

Decide once, in week two, whether your books record the USD-equivalent at receipt or whether you hold the native asset and revalue. There is no universally correct answer, but there is a wrong move: deciding case by case. Two clean patterns:

• USD-equivalent at receipt (most common for small and mid-size merchants). Snap fair-market value at the moment of chain confirmation. Future revaluation only matters when you actually sell or convert. Simple and IRS-aligned.
• Hold native (for merchants who treat stablecoins as a working balance). Record the asset in its native unit. Revalue at month-end against a documented source.

Aurpay does not auto-convert to fiat. Funds settle directly to your wallet on chain confirmation; conversion to fiat is something you do manually at an exchange, when and if you choose. Pick a pattern, write it into your month-end close checklist, and stick to it.

Week 3: customer support patterns you’ll see

By week three you’ll have enough volume to see real customer questions repeat. Train one support agent as the crypto lead and give them four scripts. The four patterns below cover roughly 90% of inbound tickets in the first month.

“I sent it to the wrong network”

The most common and most stressful ticket. A customer pays USDT but sends ERC-20 to a TRC-20 address, or vice versa. Funds aren’t lost. They’re on the wrong chain at an address you may or may not control. The clean refund procedure:

1. Acknowledge fast. Customer panic on a misrouted $500 USDT is high. Tell them the order is on hold while you sort it.
2. Ask them to send a fresh payment for the original order on the correct network, with a screenshot of the new transaction.
3. Once the new payment confirms, mark the wrong-network order as cancelled — wrong network and refund whatever the gateway rules allow on the wrong-network amount.
4. If the wrong-network funds reached an address you control on that chain, refund to the customer’s wallet on the same chain. If not, document and decline. This is exactly the scenario your refund SOP needs to spell out in writing.

Do not manually credit the order without seeing the new on-chain payment confirmed.

“Payment confirmed but my order isn’t marked paid”

Callback delay or failure. Customer sees the on-chain confirmation; your order page still says “awaiting payment.” Workflow:

1. Ask for the transaction hash.
2. Look up the order in the gateway dashboard or via the order-detail API call. If the gateway has it as paid but your store hasn’t synced, run the manual reconcile step in your store (mark paid against that order ID).
3. If the hash isn’t in the dashboard, paste it into the block explorer to confirm it’s on chain and landed at the right address.
4. If everything is right and the callback still won’t deliver, mark the order paid manually against the verified on-chain hash and log an incident.

“Can I get a USD invoice for my accountant?”

B2B customers want a paper trail in dollars. Template a PDF invoice that lists: order ID, goods or services, USDT amount paid, USD-equivalent at confirmation, and the on-chain transaction hash as the equivalent of a wire reference. One-click generation from your order admin prevents the most common B2B follow-up.

“Can I pay with USDT on Polygon?”

Politely decline. Aurpay’s verified stablecoin support today is USDT on ERC-20 and TRC-20, plus USDC on ERC-20 and TRC-20, and DAI on ERC-20. If a customer asks for USDT on Polygon, Arbitrum, or BSC, the script is: “We support USDT on Ethereum (ERC-20) and Tron (TRC-20). TRC-20 will likely be the cheapest option for you. Please send on one of those two networks.” Don’t improvise. Sending to an unsupported chain is exactly how the wrong-network ticket above gets generated.

Week 4: review the metrics that matter

Three weeks of clean data is enough to run a CFO-grade review. Pull these four numbers and frame them honestly. Rigor gets you the right kept-or-killed decision; vanity metrics get you a default-yes.

Conversion lift on crypto vs card

Look at the segment of customers who saw both options. A 1% to 3% bump in completed checkouts on a meaningful traffic slice is real. A 0.1% bump is launch-announcement noise.

Average order value delta

Crypto AOVs commonly run 1.5x to 3x your card AOV in the first month, especially on cross-border traffic. Customers paying in crypto often skew higher-net-worth, and the 0.8% flat fee is more attractive on larger tickets. That is why the 2026 comparison reference recommends running breakeven against your specific AOV before scaling.

Chargeback delta

Crypto chargebacks are zero on the payment side because blockchain transactions are irreversible. Multiply your card chargeback rate by your crypto revenue this month; that’s the dollar savings for the CFO slide. One caveat: if you also still accept cards, you’ll still get card chargebacks on card transactions. Crypto removes the risk only on the crypto leg of revenue.

Country and region mix shift

Pull a geographic breakdown of crypto orders versus historical card orders. New regions mean the option opened a market segment that wasn’t paying you before. Existing regions mean it substituted for cards. Both are fine outcomes, but they imply different next steps. The industry fit guide covers which verticals see real geographic expansion versus pure cannibalization.

Tax and accounting checklist for month one

You are responsible for your own tax compliance. Aurpay does not calculate, withhold, or remit sales tax. That stays with you. At month-end of week four, run this checklist:

1. Fair-market-value at receipt. The IRS treats crypto as property. Taxable income equals the USD-equivalent at the moment of receipt. For 1:1 stablecoins this is straightforward; for BTC and ETH, snap the price from a documented source.
2. Sales tax still applies. If your jurisdiction collects sales tax on the goods or services you sold, you owe sales tax in fiat-equivalent regardless of how the customer paid. Calculate on the USD value of the order, not the crypto unit.
3. Year-end aggregation. Export the gateway transaction list as CSV and reconcile against your accounting system at month-end. Save the export. By December you’ll have twelve clean monthly exports instead of one frantic year-end pull.
4. Accountant memo. Draft a one-page note for your CPA explaining how you record crypto income, which wallet addresses are yours, and which exchange (if any) you use to convert. Update it whenever any of those change.

The 30-day decision: keep, expand, or pull back

At day 30 the data is in. Make an honest call against three exit criteria.

1. Pull back if you got 0 crypto orders. The segment isn’t there. Disable cleanly, document why, and revisit in twelve months.
2. Keep current setup if volume was steady but small (under 1% of revenue). The option is paying its way and a small audience uses it. Don’t expand to new chains or product categories yet. Run another 60 days.
3. Expand if crypto cleared 5%+ of order volume. Add coverage for the assets your customers requested most: Bitcoin Lightning for low-AOV digital orders, USDC if your audience leans U.S. enterprise. Roll out to other product lines and brand sites. Consider adding the Payment Button on landing pages outside your main store.

The middle case, steady but small, is where most disciplined merchants land at day 30. Crypto checkout doesn’t have to be your number-one rail to be worth keeping. It has to pay for the integration cost in saved chargebacks, expanded geography, or higher AOV. Run the numbers, not the narrative.

Common failure patterns and how to avoid them

• Over-promising “no chargebacks” in marketing copy. True on the blockchain side: irreversible. Misleading if you also still accept cards. You can still get card chargebacks on card transactions, and a crypto customer can still file a card-side dispute on a different order with the same email. Frame the benefit precisely.
• Ignoring callback reliability. Callbacks occasionally fail — network blips, brief deploys, transient errors. The merchants who get burned aren’t the ones with bad gateways; they’re the ones who never built the fallback that re-pulls order status via the API when delivery slips. Build it in week one, not after the first lost order.
• Treating crypto income as “free money” without proper tax recording. Stablecoins feel like USD, so it’s tempting to skip the records. Don’t. The IRS treats them as property. Sales tax still applies. Year-one slop turns into year-two audit risk.
• Skipping support training. The wrong-network ticket lands in your inbox in week three whether you’re ready or not. A trained agent resolves it in 15 minutes; an untrained one escalates and burns 90.
• Marketing “Zero KYC” or “anonymous payments.” Don’t. The on-chain record is permanent, and your business still operates under KYC and AML rules at the bank-conversion layer. Crypto checkout is direct, fast, and non-custodial. It is not anonymous.