Documentation Index
Fetch the complete documentation index at: https://dev.moonpay.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
This page defines the acceptance criteria that apply to all MoonPay Platform integrations. Meeting these requirements is a condition of going live. They address usability, legal accuracy, and regulatory compliance. MoonPay may update these criteria at any time. When changes are required, MoonPay will provide reasonable written notice to allow time for implementation.How to read this page
Each requirement is annotated with a geo tag identifying where the customer must be located for the rule to apply: Customer location is returned on the capabilities object of an active connection.Universal requirements
All information you present to the customer must be true, accurate, and not misleading.Apple Pay
Applies when rendering the Apple Pay frame.Disclosures - US (New York and Washington)
Display the following exact text directly above the Apple Pay frame for customers located in NY or WA:
Raw text
Raw text
I agree to MoonPay’s Terms of Use and understand that, once executed, this transaction cannot be cancelled, recalled, refunded, or otherwise undone. Fraudulent transactions may result in the loss of funds with no recourse.
HTML
HTML
Disclosures - EEA
A disclosure must be displayed directly above the Apple Pay frame for all customers located in the EEA.The exact EEA disclosure verbiage is being finalized. It will be published
here once available. Plan space for it directly above the Apple Pay frame.
Disclosure rendering rules
The disclosure must be visible without any interaction. It must not be hidden behind expandable menus, tooltips, or secondary screens. The Terms of Use must be a tappable link. The full text must be rendered without truncation.Fees
When using Apple Pay you don’t need to display fees before a transaction - the Apple Pay sheet shows them on the customer’s device. The total amount displayed to the customer must exactly match the amount charged via Apple Pay.Cards
Applies to card payment methods.Attribution
“Powered by MoonPay” must be displayed on the Buy screen.Required line items
You must display all fees and quoted amounts to the customer before the transaction is completed. Every transaction quote must surface the following line items in your UI:| Line item | Description |
|---|---|
| You pay | The total fiat amount charged to the customer |
| Network fee | The on-chain gas fee |
| Ecosystem fee | Any fee applied by your platform |
| MoonPay fee | MoonPay’s transaction fee |
| Amount used to buy [token] | The fiat amount used for the crypto purchase after fees |
| At the exchange rate | The fiat-to-crypto rate applied to the transaction |
| Total crypto you’ll get | The crypto amount the customer will receive |
Waived fees
If any fee is waived, it must still appear in the UI with a displayed value of $0.00. Do not omit a line item because the fee is zero.Amount consistency
The total shown to the customer must exactly match the amount charged. Any discrepancy between the quoted total and the final payment will block go-live approval.Identity API
Applies when integrating the Identity API for KYC.Phone verification freshness
You must have verified the user’s phone number within 30 days of the user initiating the KYC flow. If verification falls outside the 30-day window, you must re-verify the phone number before KYC can proceed. Verification must use the SMS method.Persona consent
Before collecting identity information from the user, you must request explicit consent by rendering the following exact verbiage:Raw text
Raw text
By clicking [Continue], you consent to Persona and its service providers collecting and processing your biometric data for identity verification and fraud prevention, per its Privacy Policy. Your biometric information will be stored up to 3 years.
Terms acceptance
This requirement only applies if you’re integrating the Identity API. You must satisfy the End User terms-acceptance requirement using one of the two methods below, at your election.Option A - Incorporation by reference
A consolidated acceptance flow in which the End User agrees to your terms of service, which expressly incorporate the MoonPay Terms of Use by reference with a conspicuous link to the full text and a list of key terms. The following language must be included in your terms of service:Raw text
Raw text
MoonPay Services and Legal FrameworkAll regulated services, including but not limited to digital asset purchase and sale transactions, fiat currency payments, and related services, are provided exclusively by our partner, MoonPay. By using our platform for such services, you are engaging directly with MoonPay which will conduct such services under its applicable licenses and regulatory approvals. Accordingly, your use of these specific services is governed by MoonPay’s Terms of Use.Applicable Terms & PoliciesBy accessing these services, you agree to be bound by MoonPay’s Terms of Use, Privacy Policy, and other applicable terms. We strongly encourage you to review these documents in full.
HTML
HTML
Option B - Simultaneous acceptance
A single-step acceptance in which the End User is presented with both your terms and the MoonPay Terms of Use for simultaneous acceptance. MoonPay’s then-current Terms of Use must be embedded alongside your own terms (or equivalent agreement). They may be presented on the same page, modal, or interface, before or after your terms, provided it is clearly distinguishable where your terms end and MoonPay’s begin (and vice versa). MoonPay’s terms must be displayed in full, without modification or omission.Presentation and record-keeping
- The terms must be presented to the End User prior to their first transaction, and again whenever either MoonPay’s terms or your terms are materially updated.
- You must maintain a record evidencing each explicit acceptance of the terms by the End User, including a timestamp, and provide this record to MoonPay upon request.