Skip to main content
Every payment flow starts from the same two things: an authenticated customer (see Choose an onboarding path) and an executable quote. From there, you choose how much of the payment UI you want to own. Call getPaymentMethods() to see which methods are available for the customer right now, then pick the guide that matches your experience. Guest checkout removes the first requirement: new customers buy with Apple Pay or Google Pay before they have a MoonPay account, and verification steps up only when a purchase requires it.

​
Compare payment methods

Which features a customer can use depends on their country and on the capabilities enabled for your partner account. Availability also shifts over time with MoonPay's compliance decisions. The capabilities object on the connection gives the live answer; the regions and payment methods named on a docs page are for planning, not a contract. Gate each feature on its capability being present instead of keeping your own region list.
Every method can require a challenge when a transaction needs extra verification. You handle it the same way in each flow: render the Challenge frame at the URL you receive. See Handle challenges.

​
Payment guides

Guest checkout

Let new customers buy with Apple Pay or Google Pay before they have a MoonPay account.

Pay with Apple Pay

Let customers buy crypto with Apple Pay from the buy button.

Pay with Google Pay

Let customers buy crypto with Google Pay from the buy button.

Pay with card

Let customers buy crypto using stored credit and debit cards.

Pay with bank transfer

Let customers pay with SEPA (EUR) and render the deposit details natively.

Pay with the buy button

Add a single express checkout button that renders the payment method set on your quote.

Pay with widget

Render the MoonPay-hosted buy widget for all payment methods and regions.

Handle challenges

Render the Challenge frame when a transaction needs extra verification.