Questions answered. Payments made clearer.

MochiPay is crypto payment infrastructure for individuals, creators, communities, businesses, developers and automated applications. It combines payment links, on-site and HPP checkout for plugins/custom integrations, dashboard records and API workflows. Classic SaaS uses HPP only.

MochiPay is designed for online businesses, creators, communities, fundraisers, developers, SaaS platforms, independent stores and applications that need structured crypto payment capabilities.

No. Anyone with a MochiPay account can create a payment request and copy its hosted link directly from the dashboard. Developers can use the API when deeper automation is required.

An account holder creates a payment request through the dashboard or API and shares the generated link. The payer sends the exact amount using the asset and network shown on checkout.

Yes. You can share the MochiPay hosted payment link on social media, in a message, by email or on a campaign page instead of publishing your wallet address directly. The payer will still see the assigned payment address after opening the checkout page, and the resulting blockchain transaction remains public.

Yes, provided the activity is lawful and complies with the MochiPay Terms. You can create separate payment requests for tips, fundraising, donations, community projects or temporary collections and review each received payment in the dashboard. MochiPay does not determine whether a contribution is tax-deductible.

No third-party payment processor receives the funds first. The payer sends cryptocurrency on-chain to one of the account holder's enabled receiving wallets. MochiPay monitors the transaction, matches the exact amount to the order and updates its status.

A MochiPay HD wallet is controlled by its BIP-39 recovery phrase. Back it up during creation, then import that phrase into a compatible wallet application when you need to view or move funds.

1. Install a trusted wallet from its official website or app store. MetaMask supports Ethereum-compatible networks; Phantom or another Solana-compatible wallet can be used for SOL; choose a wallet that explicitly supports Bitcoin or TRON when those networks are required.
2. Select Import wallet or Import using recovery phrase, then enter the 12 words in the exact order shown when the MochiPay wallet was created.
3. Add or select the correct blockchain network and token contract. The asset, network and contract must match the corresponding record in MochiPay.
4. Compare the receiving address displayed by the wallet application with the address shown by MochiPay for that network before moving funds.
5. Keep enough native network coin for transaction fees, such as ETH for ERC20 transfers or TRX for TRC20 transfers.

Security: Never paste the recovery phrase into a website, support chat or browser page. Anyone with the phrase can control the funds. Test with a small amount before making a larger transfer.

First confirm that your wallet supports the exact asset and network displayed on the MochiPay checkout page. For a MetaMask-compatible network, follow these steps:

1. Open MetaMask and switch to the network shown on checkout.
2. Select the required token, choose Send, and paste the payment address from checkout.
3. Enter the exact payment amount shown by MochiPay. Do not round or change it.
4. Check the token, network, address and amount again, then confirm the transaction in your wallet.
5. Return to the MochiPay checkout page and wait while the blockchain transaction and required confirmations are detected.

Important: Keep enough of the network's native coin to pay the blockchain fee. If MetaMask does not support the displayed network, use a wallet that does. Never send through a different network, and never share your recovery phrase or private key with MochiPay, the recipient or anyone else.

Available currencies and networks depend on the assets currently enabled by the MochiPay platform. Always use the asset and network displayed on the payment page.

Blockchain transactions are network-specific. Sending through a different network may prevent the payment from being detected correctly.

On-site and HPP interfaces automatically check payment status through the integration’s server-side verification. Account holders can also view the order in the dashboard or query it through the API.

Yes. Developers can create payment orders and query order status through authenticated API endpoints. Request formats and examples are available in the developer documentation.

Yes. You can create an order in the dashboard and share the hosted payment link directly with the payer.

The developer area offers 19 separate plugin ZIPs for 12 store families: WooCommerce, OpenCart, Zen Cart, Magento, PrestaShop, Shopware, Drupal Commerce, EC-CUBE, Bagisto, Sylius, osCommerce and thirty bees. Choose the matching core branch and PHP environment. Every ZIP includes English instructions; all offer ON_SITE and HPP. Classic SaaS uses HPP only.

ON_SITE displays the payment dialog, exact amount, receiving address, QR code and status on your own checkout page. HPP (Hosted Payment Page) redirects the customer to a payment page hosted by MochiPay, then returns them to your configured URL. Both modes use the same payment order and send funds directly to your receiving wallet. Your backend verifies payment before marking the order paid. All standalone plugins and custom API/PHP integrations support both modes; Classic SaaS and dashboard payment links use HPP only.

Yes. Download our free English skill for plugin selection, exact core/PHP requirements, ON_SITE/HPP API integration and troubleshooting. It includes optional offline Python checks. Install it through your AI tool's supported skills workflow; it does not grant account access or replace your private merchant configuration. MochiPay subscriptions and AI-tool requirements are separate.

Download the skill and follow the installation guide →

ON_SITE keeps customers in your familiar store and removes the extra redirect to a separate payment page. This can reduce checkout abandonment and improve payment completion. It is the default for the standalone plugins and PHP Demo. The actual improvement depends on your checkout, traffic and customers; compare completed payments in your own funnel. HPP remains available when you prefer a ready-made hosted payment page.

Yes. All standalone store plugins support on-site and HPP, with on-site as the default. Custom API integrations and the PHP Demo support both experiences using the same payment order. Classic SaaS integrations use HPP only. The on-site browser displays payment instructions while your own backend signs API requests and verifies the result.

Yes. An AI-backed service can create and track payment requests through server-side authenticated APIs. This can support human-to-AI and AI-to-AI workflows where another agent or its approved wallet process completes the crypto payment. API secrets must remain outside the agent's public interface.

MochiPay offers monthly, quarterly and yearly subscription periods. Current prices are shown on the pricing page.

Yes. During renewal you can keep the current plan or select another available subscription period before making payment.

Recovery phrases are shown during wallet creation and stored encrypted on the server. The application has decryption capability for wallet functions. API secrets are protected in server-side configuration; keep all recovery material and credentials private. Read the current wallet and security model →