MoonPay released a rebuilt Crypto Deposits product on October 27, 2026, giving partners a single integration that combines fiat funding, cross-chain transfers and connections to more than 600 wallets and centralized exchanges. The original product launched in February to let users fund applications with crypto they already held. The upgrade adds funding options, including purchases made inside a partner's app.
Merchants choose the token they receive, and MoonPay handles routing, conversion and delivery. The product supports Bitcoin and stablecoins, plus all tokens on chains including Solana, Ethereum, Arbitrum, Polygon, Base, BNB Smart Chain, Robinhood Chain, HyperEVM and Hypercore.
What merchants actually get
The headless onramp runs inside the partner's app without redirects. Users can connect an existing DeFi wallet or transfer directly from centralized exchanges including Coinbase and Binance. Fiat funding covers Apple Pay, Google Pay, credit and debit cards, Revolut Pay, bank transfers and local payment methods.
For merchants who want fiat settlement, MoonPay points them to MoonPay Enterprise, which is a separate integration. That distinction matters for teams scoping the work: Crypto Deposits handles the crypto side, Enterprise handles the off-ramp into fiat.
There's a gap between the announcement and the product page. The announcement describes support for all tokens on the listed chains. The product page gives a narrower description: 13 tokens across 10 blockchains. Developers will need to check at the implementation level whether a particular deposit can reach the merchant's chosen payout currency, beyond what either page describes.
The integration checklist
Setting up a deposit requires a configured recipient currency, customer-specific deposit addresses, route checks and backend confirmation of settled deposits via webhooks. Developers query Get Deposit Currencies for available assets and networks. Deposited funds are bridged and swapped into the recipient currency.
The Get Deposit Customer response returns a swapRoutes array describing paths into the recipient currency. Each route carries an available flag and a minAmountUsd threshold. Developers have to strip unavailable routes and either display or enforce the minimums.
A merchant creates a deposit through the dashboard or the Create Deposit endpoint. The resulting depositId identifies the configuration: recipient blockchain, currency and enabled funding methods. Documented funding methods include manual transfers, wallet connections, exchange connections, Add Money and bank transfers. Email notifications can report successful deposits, and merchants can disable the cash-payment option.
Add Money requires API keys from MoonPay Ramps or Onramper under integration settings. MoonPay Ramps must approve the application's domains before Add Money can run in inline or button mode; new-tab mode skips domain whitelisting. Bank Transfer creates a virtual account for the user with support for rails such as SEPA and ACH where available, with availability dependent on the user's region.
Customer records and address reuse
Each customer needs a Deposit Customer record. The API requires a unique customerId and a recipientWallet, with optional metadata in additionalJson, and generates associated deposit addresses across SVM, EVM and Bitcoin networks. Developers must store the returned customer token to reuse the same customer's address for later transactions. Separate endpoints retrieve or update the record.
Addresses can be served through the developer's own interface or by embedding MoonPay's deposit widget. The headless path retrieves the customer's depositWallets array. Recording wallet activity through the customer token or specified public keys increases balance polling so incoming payments are detected more quickly. The widget route includes a React package and a demo where developers can paste a customer token to test display configurations.
Webhooks are configured in dashboard settings or through the deposit-webhook endpoint. DEPOSIT_TX_* events confirm settled deposits, and the documented integration handles settlement through those events.
Who can't use it
The product webpage states it is not intended for EEA or New York users. That's a notable carve-out for a product pitched at global partners, though MoonPay hasn't said whether that restriction is temporary or tied to licensing.
The next concrete step for interested developers is to query Get Deposit Currencies for the assets and networks they intend to support, then verify swap route availability and minimums against the payout currency they've configured.
