Receiving workflows
PayIn vs MoonPay Commerce
Both offer direct-wallet payments. Choose between focused USDC receiving and broader crypto commerce tools.
Keep USDC in your wallet.
You need USDC links, a counter display and payment records alongside your existing sales process.
Add commerce tools.
You need Shopify, subscriptions, embedded checkout or reporting exports.
What changes in practice
| Decision | PayIn | MoonPay Commerce |
|---|---|---|
| Product focus | USDC receipts on Base, Polygon and Solana. | A broader crypto commerce toolkit with multiple assets and payment products. |
| Wallet destination | Your chosen receiving address. No PayIn merchant balance. | Peer-to-peer merchant payments; routing, swaps or offramps add their own steps and terms. |
| Starting point | Create a QR or link and protect its private management URL. | Configure a payment in the dashboard or build with APIs and SDKs. |
| Operations | Counter display, optional device audio and merchant payment history. | Dashboard transactions, CSV exports and webhook notifications. |
| Refunds | Arrange a separate transfer with the customer. | Merchant-managed refunds through the dashboard; blockchain payments cannot simply be reversed. |
| Commerce integration | Custom integration for order association and fulfillment. | Checkout widget, Shopify and subscription products are documented. |
From Helio to MoonPay
MoonPay’s official FAQ identifies the service as formerly Helio. Some documentation and product links still use hel.io. This page compares its documented workflows with PayIn; it does not claim a hands-on benchmark or a shared checkout speed test.
MoonPay describes merchant payments as peer-to-peer. PayIn therefore does not claim that direct-wallet receiving is unique. If you enable swaps, routing or an offramp, inspect that specific flow rather than treating every path as an identical wallet-to-wallet transfer.
Official sources: MoonPay Commerce: official FAQ and operating workflows
From request to record
In PayIn, create a request with a receiving address, merchant name and fixed or customer-entered amount. Share the link or show the counter QR. The customer reviews the page and approves in a compatible wallet. You check the merchant record before fulfilling the sale.
MoonPay paylinks are configured with product details, price and networks. Its dashboard provides transactions, CSV exports, refunds and webhooks.
Official sources: MoonPay Commerce: official FAQ and operating workflows
Commerce tools
MoonPay documents embedded checkout, Shopify and subscriptions. Check each product’s terms, verification and supported setup for your store.
PayIn does not include a storefront, recurring billing, built-in ticketing or stock management. A reusable payment link needs manual matching or a custom integration to associate a receipt with an order. Completion callbacks can help that integration, but verification, duplicate handling and reconciliation remain part of your system.
Official sources: MoonPay Commerce: product documentation
Refunds, fees and cash-out
For PayIn, refunds are separate transfers arranged with the customer, and bank cash-out is your own process. MoonPay’s documentation describes merchant-managed refunds and optional bank offramp services. Check availability and requirements for the exact service you need.
Compare the complete cost of your selected payment path, including transaction, network, swap, conversion and cash-out costs where applicable. We do not publish a universal savings claim or rank the products by unmatched timing measurements.
Choose PayIn when its narrow direct-USDC workflow is enough. Choose a broader platform when the additional commerce operations replace work your team would otherwise have to build or perform.
Official sources: MoonPay Commerce: official FAQ and operating workflows
Start receiving
QR or payment link.
Prepare a compatible wallet and test before serving customers.