Introduction
A U.S. business evaluating crypto payments needs more than a list of token logos. The payment solution has to fit checkout, bank settlement, operations, customer support, finance and compliance requirements. The merchant should also understand the exact token and network combinations available in its approved MiraclePay configuration rather than assuming that support for a token means support on every blockchain.
1. Merchant eligibility and onboarding
Start by confirming that the business and intended payment use case can be onboarded. Merchant verification, account configuration and banking requirements should be completed before relying on a particular payment or settlement route.
2. Online, QR, POS and e-commerce routes
Choose the channels that match where customers actually pay. Depending on the merchant setup, this can include online checkout, dynamic QR, WooCommerce or POS-oriented payment experiences. The goal is to make crypto another familiar checkout option rather than a separate technical process.
3. Supported tokens and networks
Ask for exact token/network combinations rather than only token names. For example, current production infrastructure used by MiraclePay can support USDC routes across networks including Algorand, Aptos, Arbitrum, Avalanche, Base, BNB Smart Chain, Celo, Ethereum, Hedera, Hyperliquid, Monad, OP Mainnet, Polygon, Solana, Sui, Tempo, Stellar, zkSync and World Chain. The actual list shown to a merchant should match that merchant's enabled configuration. This distinction is important because USDC on Ethereum, USDC on Solana and USDC on Base are separate network-specific payment routes.
4. USD settlement and bank payout
If the business does not want to retain crypto, confirm whether its approved MiraclePay configuration supports USD settlement to a designated business bank account. Confirm which payment routes feed that settlement, how settlement is recorded and what finance sees in the resulting payout.
5. Payment status and fulfilment
Ask how pending, confirming, completed, expired and exception states are represented and which status should trigger fulfillment. A customer wallet screenshot should not replace the merchant's payment status.
6. Refunds and exceptions
Crypto payments do not use the same built-in card-network chargeback process. Merchants still need clear customer-service, refund and exception policies. Ask what happens when a customer pays late, sends the wrong amount or uses an unsupported token/network route.
7. Reconciliation and reporting
Finance should be able to trace the order, token, network, payment status, conversion where applicable, settlement, bank payout and any refund or adjustment. Good reporting prevents crypto payments from becoming a separate manual spreadsheet process.
8. Security and permissions
Review staff access, authentication, payment creation, refund authorization, audit records and escalation controls. In normal checkout, staff should not need to copy wallet addresses or interpret blockchain explorers.
9. U.S. compliance and tax considerations
U.S. legal, tax and regulatory treatment depends on the merchant's facts and activities. Businesses should review their own obligations with qualified legal, tax and accounting professionals. Public-facing product copy should describe MiraclePay's merchant payment service and approved configuration without making broader claims about a merchant's legal or tax position.
10. Implementation and support
Ask how test transactions work, who owns implementation, what documentation is available and how incidents are escalated after launch.
A good payment method is one the business can operate on an ordinary day and troubleshoot on an unusual one.
Frequently asked questions
What should a U.S. business look for in a crypto payment gateway?
Evaluate merchant eligibility, checkout channels, exact token/network support, payment status, settlement, refunds, reconciliation, security and implementation.
Can a U.S. business accept crypto and receive USD?
Eligible merchants may use an approved MiraclePay configuration in which supported crypto payments result in USD settlement to a designated business bank account.
Can a U.S. business accept USDC?
Yes, where USDC and the selected network are enabled for the merchant's MiraclePay configuration.
Should a merchant publish every technically supported network?
No. Merchant-facing checkout and documentation should show only the token/network combinations actually enabled for that merchant.
Sources & context
This article is published by MiraclePay. Product availability, supported assets, networks and settlement terms should be confirmed for the relevant merchant account before launch.
Related merchant paths: Explore stablecoin payments · Explore the WooCommerce crypto payment gateway · Explore the ecommerce crypto payment gateway · Explore crypto QR code payments.
