Skip to main content

Embedded Checkout

Customize the embedded checkout UI with the appearance prop:

Identity Verification Screens

When an order requires KYC, the identity verification screens render inside the checkout and read the same appearance object, so your theme applies to them without extra configuration. There is no separate theme key: an opaque dark backgroundPrimary switches the screens to their dark defaults. See the identity verification UI customization guide for the settings that apply, the default colors, and how to place the screens on your page.

Customization Options

Background Customization

The embedded checkout component has a transparent background by default. The backgroundPrimary color only affects internal components (inputs, cards) within the iframe, not the iframe body itself. To customize the overall background, wrap the component in a div with your desired background styling:
The backgroundPrimary color in your appearance configuration should complement your wrapper background for the best visual result.

Custom Fonts

Load custom fonts using the fonts array:

Global Variables

Control the overall look and feel with global variables:

Component Rules

Style individual components through appearance.rules. Each rule accepts borderRadius, font, colors, plus state overrides like hover, focus, selected, and disabled.
Hide specific inputs:
When hiding inputs, provide the corresponding values via props: recipient.walletAddress for a hidden DestinationInput, and payment.receiptEmail for a hidden ReceiptEmailInput.
Input, Label, and Tab rules accept borderRadius, font (family, size, weight), and colors (text, background, border, boxShadow, placeholder), with hover, focus, and selected state blocks.
Style the primary button, including hover and disabled states:

Common Examples

Hosted Checkout

The hosted checkout exposes a smaller appearance surface: button theming, checkout display mode, and overlay behavior.

Headless Checkout

Headless checkout has no built-in UI — you design your own purchase preview, payment-method selection, wallet connection, and status screens. Follow the order lifecycle in How Checkout Works and reuse the status catalog in Error & Status Codes to drive your UI states.

Next Steps

Localization

Translate the checkout and set the payment currency

Hooks & Events

React to order updates in your own UI