# Customise appearance Customise your checkout page's colours, fonts, shapes, and more. # Full hosted page > This is a Full hosted page for when payment-ui is stripe-hosted. View the full page at https://docs.stripe.com/payments/checkout/customization/appearance?payment-ui=stripe-hosted. ## Apply branding #### Dashboard You can apply custom branding to Checkout. Go to [Branding Settings](https://dashboard.stripe.com/settings/branding/checkout) to: - Upload a logo or icon - Customise the Checkout page’s background colour, button colour, font, and shapes ### Branding with Connect Checkout uses the brand settings of the connected account destination charges with `on_behalf_of` and for platforms performing direct charges. For connected accounts without access to the full Stripe Dashboard (includes Express and Custom accounts), platforms can configure the brand settings with the [Accounts](https://docs.stripe.com/api/accounts/object.md#account_object-settings-branding) API. #### API You can apply custom branding to a Checkout Session by using the [branding_settings](https://docs.stripe.com/api/checkout/sessions/create.md#create_checkout_session-branding_settings) parameter to: - Set a logo or icon - Customise the Checkout page’s background colour, button colour, font, and shapes - Change your brand name By default, we apply the custom branding set in the Dashboard to your Checkout Sessions. If you omit a field in `branding_settings`, Checkout applies the default value from the Dashboard. If you pass in both [logo](https://docs.stripe.com/api/checkout/sessions/create.md#create_checkout_session-branding_settings-logo) and [icon](https://docs.stripe.com/api/checkout/sessions/create.md#create_checkout_session-branding_settings-icon), the Checkout page displays the logo and uses the icon as the favicon. If you only pass in `logo`, the Checkout page displays the logo and Checkout uses your icon from [Branding Settings](https://dashboard.stripe.com/settings/branding/checkout) as the favicon. If you only pass in `icon`, the Checkout page displays the icon and also uses it as the favicon. > Invoices for [subscriptions](https://docs.stripe.com/receipts.md#invoice-and-subscription-payment-receipts) and invoices for [one-time payments](https://docs.stripe.com/payments/checkout/receipts.md?payment-ui=stripe-hosted#paid-invoices-hosted) from a Checkout Session still use the branding settings set in the Dashboard. Make sure to use branding settings that are consistent and recognisable by your customers to reduce confusion and the risk of chargebacks. ```curl curl https://api.stripe.com/v1/checkout/sessions \ -u "<>:" \ -d "line_items[0][price]={{PRICE_ID}}" \ -d "line_items[0][quantity]=1" \ -d mode=payment \ -d "branding_settings[icon][type]=file" \ -d "branding_settings[icon][file]={{FILE_ID}}" \ -d "branding_settings[logo][type]=file" \ -d "branding_settings[logo][file]={{FILE_ID}}" \ -d "branding_settings[display_name]=Powdur" \ -d "branding_settings[font_family]=roboto" \ -d "branding_settings[border_style]=rectangular" \ --data-urlencode "branding_settings[background_color]=#7D8CC4" \ --data-urlencode "branding_settings[button_color]=#A0D2DB" \ --data-urlencode "success_url=https://example.com/success" ``` ### Branding with Connect Checkout uses the brand settings of the connected account for destination charges with `on_behalf_of` and for platforms performing direct charges. For connected accounts without access to the full Stripe Dashboard (includes Express and Custom accounts), platforms can configure the brand settings with the [Accounts](https://docs.stripe.com/api/accounts/object.md#account_object-settings-branding) API. To override the brand settings of the connected account, set [branding_settings](https://docs.stripe.com/api/checkout/sessions/create.md#create_checkout_session-branding_settings) when you create the Checkout Session. ## Change your brand name You can change a Checkout page’s name by modifying the **Business name** field in [Business details settings](https://dashboard.stripe.com/settings/business-details) or setting [branding_settings.display_name](https://docs.stripe.com/api/checkout/sessions/create.md#create_checkout_session-branding_settings-display_name). You can also [customise the domain name](https://docs.stripe.com/payments/checkout/custom-domains.md) of a Stripe-hosted Checkout page. > Make sure to use a business name that is consistent and recognisable by your customers to reduce confusion and the risk of chargebacks. Network rules also generally require you to use accurate and consistent business name and logo. ## Font compatibility Each custom font is compatible with a [subset of locales](https://docs.stripe.com/js/appendix/supported_locales). You can either explicitly set the locale of a Checkout Session by passing the locale field when creating the Session, or use the default `auto` setting where Checkout chooses a locale based on the customer’s browser settings. The following table lists unsupported locales for each font. Languages in these locales might fall outside the supported character range for a given font. In those cases, Stripe renders the Checkout page with an appropriate system fallback font. If you choose a Serif font but it’s unsupported in a locale, Stripe falls back to a Serif-based font. | Font family | Unsupported locales | | --------------- | ---------------------------------------------------------------------------------------------------------- | | Be Vietnam Pro | `bg`, `el`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Bitter | `el`, `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Chakra Petch | `bg`, `el`, `ja`, `ko`, `ru`, `zh`, `zh-HK`, `zh-TW` | | Hahmlet | `bg`, `el`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Inconsolata | `bg`, `el`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Inter | `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Lato | `bg`, `cs`, `el`, `hr`, `ja`, `ko`, `lt`, `lv`, `mt`, `ro`, `ru`, `sl`, `th`, `vi`, `zh`, `zh-HK`, `zh-TW` | | Lora | `el`, `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | M PLUS 1 Code | `bg`, `el`, `ko`, `lt`, `lv`, `ru`, `sk`, `sl`, `th`, `tr` | | Montserrat | `el`, `hr`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Nunito | `el`, `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Noto Sans | `ja`, `ko`, `th` | | Noto Serif | `th` | | Open Sans | `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | PT Sans | `el`, `ja`, `ko`, `th`, `vi`, `zh`, `zh-HK`, `zh-TW` | | PT Serif | `el`, `ja`, `ko`, `th`, `vi`, `zh`, `zh-HK`, `zh-TW` | | Pridi | `bg`, `el`, `ja`, `ko`, `ru`, `zh`, `zh-HK`, `zh-TW` | | Raleway | `el`, `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Roboto | `ja`, `ko`, `zh`, `zh-HK`, `zh-TW` | | Roboto Slab | `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Source Sans Pro | `bg`, `el`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Titillium Web | `bg`, `el`, `ja`, `ko`, `th`, `vi`, `zh`, `zh-HK`, `zh-TW` | | Ubuntu Mono | `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Zen Maru Gothic | `bg`, `cs`, `el`, `hr`, `ko`, `lt`, `lv`, `pl`, `ro`, `ru`, `sk`, `th`, `vi` | # Full embedded page > This is a Full embedded page for when payment-ui is embedded-page. View the full page at https://docs.stripe.com/payments/checkout/customization/appearance?payment-ui=embedded-page. ## Apply branding #### Dashboard You can apply custom branding to Checkout. Go to [Branding Settings](https://dashboard.stripe.com/settings/branding/checkout) to customise the embedded form’s background colour, button colour, font, and shapes. ### Branding with Connect Checkout uses the brand settings of the connected account destination charges with `on_behalf_of` and for platforms performing direct charges. For connected accounts without access to the full Stripe Dashboard (includes Express and Custom accounts), platforms can configure the brand settings with the [Accounts](https://docs.stripe.com/api/accounts/object.md#account_object-settings-branding) API. #### API You can apply custom branding to a Checkout Session by using the [branding_settings](https://docs.stripe.com/api/checkout/sessions/create.md#create_checkout_session-branding_settings) parameter to: - Customise the Checkout page’s background colour, button colour, font, and shapes - Change your brand name By default, we apply the custom branding set in the Dashboard to your Checkout Sessions. If you omit a field in `branding_settings`, Checkout applies the default value from the Dashboard. > Invoices for [subscriptions](https://docs.stripe.com/receipts.md#invoice-and-subscription-payment-receipts) and invoices for [one-time payments](https://docs.stripe.com/payments/checkout/receipts.md?payment-ui=stripe-hosted#paid-invoices-hosted) from a Checkout Session still use the branding settings set in the Dashboard. Make sure to use branding settings that are consistent and recognisable by your customers to reduce confusion and the risk of chargebacks. ```curl curl https://api.stripe.com/v1/checkout/sessions \ -u "<>:" \ -d "line_items[0][price]={{PRICE_ID}}" \ -d "line_items[0][quantity]=1" \ -d mode=payment \ -d "branding_settings[display_name]=Powdur" \ -d "branding_settings[font_family]=roboto" \ -d "branding_settings[border_style]=rectangular" \ --data-urlencode "branding_settings[background_color]=#7D8CC4" \ --data-urlencode "branding_settings[button_color]=#A0D2DB" \ -d ui_mode=embedded_page \ --data-urlencode "return_url=https://example.com/return" ``` ### Branding with Connect Checkout uses the brand settings of the connected account destination charges with `on_behalf_of` and for platforms performing direct charges. For connected accounts without access to the full Stripe Dashboard (includes Express and Custom accounts), platforms can configure the brand settings with the [Accounts](https://docs.stripe.com/api/accounts/object.md#account_object-settings-branding) API. To override the brand settings of the connected account, set [branding_settings](https://docs.stripe.com/api/checkout/sessions/create.md#create_checkout_session-branding_settings) when you create the Checkout Session. ## Change your brand name You can change the name in the embedded form by modifying the **Business name** field in [Business details settings](https://dashboard.stripe.com/settings/business-details) or setting [branding_settings.display_name](https://docs.stripe.com/api/checkout/sessions/create.md#create_checkout_session-branding_settings-display_name). > Make sure to use a business name that is consistent and recognisable by your customers to reduce confusion and the risk of chargebacks. Network rules also generally require you to use accurate and consistent business name and logo. ## Font compatibility Each custom font is compatible with a [subset of locales](https://docs.stripe.com/js/appendix/supported_locales). You can either explicitly set the locale of a Checkout Session by passing the locale field when creating the Session, or use the default `auto` setting where Checkout chooses a locale based on the customer’s browser settings. The following table lists unsupported locales for each font. Languages in these locales might fall outside the supported character range for a given font. In those cases, Stripe renders the Checkout page with an appropriate system fallback font. If you choose a Serif font but it’s unsupported in a locale, Stripe falls back to a Serif-based font. | Font family | Unsupported locales | | --------------- | ---------------------------------------------------------------------------------------------------------- | | Be Vietnam Pro | `bg`, `el`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Bitter | `el`, `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Chakra Petch | `bg`, `el`, `ja`, `ko`, `ru`, `zh`, `zh-HK`, `zh-TW` | | Hahmlet | `bg`, `el`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Inconsolata | `bg`, `el`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Inter | `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Lato | `bg`, `cs`, `el`, `hr`, `ja`, `ko`, `lt`, `lv`, `mt`, `ro`, `ru`, `sl`, `th`, `vi`, `zh`, `zh-HK`, `zh-TW` | | Lora | `el`, `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | M PLUS 1 Code | `bg`, `el`, `ko`, `lt`, `lv`, `ru`, `sk`, `sl`, `th`, `tr` | | Montserrat | `el`, `hr`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Nunito | `el`, `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Noto Sans | `ja`, `ko`, `th` | | Noto Serif | `th` | | Open Sans | `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | PT Sans | `el`, `ja`, `ko`, `th`, `vi`, `zh`, `zh-HK`, `zh-TW` | | PT Serif | `el`, `ja`, `ko`, `th`, `vi`, `zh`, `zh-HK`, `zh-TW` | | Pridi | `bg`, `el`, `ja`, `ko`, `ru`, `zh`, `zh-HK`, `zh-TW` | | Raleway | `el`, `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Roboto | `ja`, `ko`, `zh`, `zh-HK`, `zh-TW` | | Roboto Slab | `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Source Sans Pro | `bg`, `el`, `ja`, `ko`, `ru`, `th`, `zh`, `zh-HK`, `zh-TW` | | Titillium Web | `bg`, `el`, `ja`, `ko`, `th`, `vi`, `zh`, `zh-HK`, `zh-TW` | | Ubuntu Mono | `ja`, `ko`, `th`, `zh`, `zh-HK`, `zh-TW` | | Zen Maru Gothic | `bg`, `cs`, `el`, `hr`, `ko`, `lt`, `lv`, `pl`, `ro`, `ru`, `sk`, `th`, `vi` | # Embedded form > This is a Embedded form for when payment-ui is checkout-form. View the full page at https://docs.stripe.com/payments/checkout/customization/appearance?payment-ui=checkout-form. > Learn more about [the embedded form integration](https://docs.stripe.com/payments/checkout/how-checkout-works.md?payment-ui=checkout-form). You can visually customise the embedded form to match the design of your site with the `appearance` option. The layout of the form stays consistent, but you can modify colours, fonts, borders, padding, and so on. 1. Pick a prebuilt [theme](https://docs.stripe.com/payments/checkout/customization/appearance.md#theme) that most closely resembles your website. 1. Customise the theme using [inputs and labels](https://docs.stripe.com/payments/checkout/customization/appearance.md#inputs-and-labels). 1. Set [variables](https://docs.stripe.com/payments/checkout/customization/appearance.md#variables), such as the `fontFamily` and `colorPrimary` to broadly customise components appearing throughout the embedded form. ## Themes Start customising the embedded form by selecting one of the following themes: - `stripe` - `night` - `flat` #### HTML + JS ```js const appearance = { theme: 'night' }; // Pass the appearance object when initializing checkout const checkout = stripe.initCheckoutFormSdk({clientSecret, appearance}); ``` #### React ```jsx import {CheckoutFormProvider} from '@stripe/react-stripe-js/checkout'; const appearance = { theme: 'night' }; // Pass the appearance object to CheckoutFormProvider ``` ## Inputs and labels Customise the appearance of input fields and their associated labels. `const appearance = { inputs: 'spaced', labels: 'auto' }` ### Inputs Choose the style of input fields to suit your design. | Variant | Description | | ----------- | ------------------------------------------------------------------------------------------------- | | `spaced` | Each input field has space surrounding it. | | `condensed` | Related input fields are grouped together without space between them. This is the default option. | ### Labels Control the position and visibility of labels associated with input fields. | Variant | Description | | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `auto` | Labels adjust based on the input variant. When inputs are `spaced`, labels are `above`. When inputs are `condensed`, labels are `floating`. This is the default option. | | `above` | Labels are positioned above the corresponding input fields. | | `floating` | Labels float within the input fields. | ## Variables Set variables to affect the appearance of many components appearing throughout the Checkout form. ![Payment form with card input fields, major credit card icons, and Klarna payment option, with labelled Appearance API variables for colours and styling.](https://b.stripecdn.com/docs-statics-srv/assets/exampleVariables@2x.8c50d1561d5d4fbb1ac0187983ab33c0.png) The `variables` option works like [CSS variables](https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties). You can specify CSS values for each variable and reference other appearance variables with the `var(--myVariable)` syntax. You can even inspect the resulting DOM using the DOM explorer in your browser. > The `colorPrimary`, `colorBackground`, `colorText`, `colorSuccess`, `colorDanger`, and `colorWarning` variables don’t support `rgba()` or the `var(--myVariable)` syntax. #### HTML + JS ```js const appearance = { theme: 'stripe', variables: { colorPrimary: '#0570de', colorBackground: '#ffffff', colorText: '#30313d', colorDanger: '#df1b41', fontFamily: 'Ideal Sans, system-ui, sans-serif', spacingUnit: '2px', borderRadius: '4px', // See all possible variables below } }; // Pass the appearance object when initializing checkout const checkout = stripe.initCheckoutFormSdk({clientSecret, appearance}); ``` #### React ```jsx import {CheckoutFormProvider} from '@stripe/react-stripe-js/checkout'; const appearance = { theme: 'stripe', variables: { colorPrimary: '#0570de', colorBackground: '#ffffff', colorText: '#30313d', colorDanger: '#df1b41', fontFamily: 'Ideal Sans, system-ui, sans-serif', spacingUnit: '2px', borderRadius: '4px', // See all possible variables below } }; // Pass the appearance object to CheckoutFormProvider ``` ### Commonly used variables | Variable | Description | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `fontFamily` | The font family used throughout the UI. The Checkout form supports custom fonts by passing the `fonts` option to [initCheckoutFormSdk](https://docs.stripe.com/js/custom_checkout/init#custom_checkout_init-options-elementsOptions-fonts) or [CheckoutFormProvider](https://docs.stripe.com/js/react_stripe_js/checkout/checkout_provider#react_checkout_provider-options-elementsOptions-fonts). | | `fontSizeBase` | The font size that’s set on the root of the UI. By default, other font size variables such as `fontSizeXs` or `fontSizeSm` are scaled from this value using `rem` units. Make sure that you choose a font size of at least 16px for input fields on mobile. | | `spacingUnit` | The base spacing unit that all other spacing is derived from. Increase or decrease this value to make your layout more or less spacious. | | `borderRadius` | The border radius used for tabs, inputs and other components. | | `colorPrimary` | A primary colour used throughout the UI. Set this to your primary brand colour. | | `colorBackground` | The colour used for the background of inputs, tabs and other components. | | `colorText` | The default text colour used. | | `colorDanger` | A colour used to indicate errors or destructive actions. | ### Less commonly used variables | Variable | Description | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `buttonBorderRadius` | The border radius used for buttons. By default, buttons use `borderRadius`. | | `buttonColorBackground` | The color used for the background of buttons. By default, buttons use `colorPrimary`. | | `buttonColorText` | The text colour used for buttons. By default, buttons use `accessibleColorOnColorPrimary`. | | `focusBoxShadow` | The `box-shadow` used for focused components. | | `focusOutline` | The `outline` used for focused components. | | `fontSmooth` | What text anti-aliasing settings to use. It can be `always`, `auto`, or `never`. | | `fontVariantLigatures` | The [font-variant-ligatures](http://developer.mozilla.org/en-US/docs/Web/CSS/font-variant-ligatures) setting of text. | | `fontVariationSettings` | The [font-variation-settings](http://developer.mozilla.org/en-US/docs/Web/CSS/font-variation-settings) setting of text. | | `fontWeightLight` | The font weight used for light text. | | `fontWeightNormal` | The font weight used for normal text. | | `fontWeightMedium` | The font weight used for medium text. | | `fontWeightBold` | The font weight used for bold text. | | `fontLineHeight` | The [line-height](http://developer.mozilla.org/en-US/docs/Web/CSS/line-height) setting of text. | | `fontSize2Xl` | The font size of double-extra large text. By default this is scaled from `var(--fontSizeBase)` using `rem` units. | | `fontSizeXl` | The font size of extra-large text. By default this is scaled from `var(--fontSizeBase)` using `rem` units. | | `fontSizeLg` | The font size of large text. By default this is scaled from `var(--fontSizeBase)` using `rem` units. | | `fontSizeSm` | The font size of small text. By default this is scaled from `var(--fontSizeBase)` using `rem` units. | | `fontSizeXs` | The font size of extra-small text. By default this is scaled from `var(--fontSizeBase)` using `rem` units. | | `fontSize2Xs` | The font size of double-extra small text. By default this is scaled from `var(--fontSizeBase)` using `rem` units. | | `fontSize3Xs` | The font size of triple-extra small text. By default this is scaled from `var(--fontSizeBase)` using `rem` units. | | `logoColor` | A preference for which logo variations to display; either `light` or `dark`. | | `tabLogoColor` | The logo variation to display inside `.Tab` components; either `light` or `dark`. | | `tabLogoSelectedColor` | The logo variation to display inside the `.Tab--selected` component; either `light` or `dark`. | | `blockLogoColor` | The logo variation to display inside `.Block` components; either `light` or `dark`. | | `colorSuccess` | A colour used to indicate positive actions or successful results. | | `colorWarning` | A colour used to indicate potentially destructive actions. | | `accessibleColorOnColorPrimary` | The colour of text appearing on top of any `var(--colorPrimary)` background. | | `accessibleColorOnColorBackground` | The colour of text appearing on top of any `var(--colorBackground)` background. | | `accessibleColorOnColorSuccess` | The colour of text appearing on top of any `var(--colorSuccess)` background. | | `accessibleColorOnColorDanger` | The colour of text appearing on top of any `var(--colorDanger)` background. | | `accessibleColorOnColorWarning` | The colour of text appearing on top of any `var(--colorWarning)` background. | | `colorTextSecondary` | The colour used for text of secondary importance. For example, this colour is used for the label of a tab that isn’t currently selected. | | `colorTextPlaceholder` | The colour used for input placeholder text. | | `iconColor` | The default colour used for icons, such as the icon appearing in the card tab. | | `iconHoverColor` | The colour of icons when hovered. | | `iconCardErrorColor` | The colour of the card icon when it’s in an error state. | | `iconCardCvcColor` | The colour of the CVC variant of the card icon. | | `iconCardCvcErrorColor` | The colour of the CVC variant of the card icon when the CVC field has invalid input. | | `iconCheckmarkColor` | The colour of tickmarks displayed within components like `.Checkbox`. | | `iconChevronDownColor` | The colour of arrow icons displayed within select inputs. | | `iconChevronDownHoverColor` | The colour of arrow icons when hovered. | | `iconCloseColor` | The colour of close icons, used for indicating a dismissal or close action. | | `iconCloseHoverColor` | The colour of close icons when hovered. | | `iconLoadingIndicatorColor` | The colour of the spinner in loading indicators. | | `iconMenuColor` | The colour of menu icons used to indicate a set of additional actions. | | `iconMenuHoverColor` | The colour of menu icons when hovered. | | `iconMenuOpenColor` | The colour of menu icons when opened. | | `iconPasscodeDeviceColor` | The colour of the passcode device icon, used to indicate a message has been sent to the user’s mobile device. | | `iconPasscodeDeviceHoverColor` | The colour of the passcode device icon when hovered. | | `iconPasscodeDeviceNotificationColor` | The colour of the notification indicator displayed over the passcode device icon. | | `iconRedirectColor` | The colour of the redirect icon that appears for redirect-based payment methods. | | `tabIconColor` | The colour of icons appearing in a tab. | | `tabIconHoverColor` | The colour of icons appearing in a tab when the tab is hovered. | | `tabIconSelectedColor` | The colour of icons appearing in a tab when the tab is selected. | | `tabIconMoreColor` | The colour of the icon that appears in the trigger for the additional payment methods menu. | | `tabIconMoreHoverColor` | The colour of the icon that appears in the trigger for the additional payment methods menu when the trigger is hovered. | | `accordionItemSpacing` | The vertical spacing between `.AccordionItem` components. This is only applicable when [spacedAccordionItems](https://docs.stripe.com/js/elements_object/create_payment_element#payment_element_create-options-layout-spacedAccordionItems) is `true`. | | `gridColumnSpacing` | The spacing between columns in the grid used for the UI layout. | | `gridRowSpacing` | The spacing between rows in the grid used for the UI layout. | | `pickerItemSpacing` | The spacing between `.PickerItem` components rendered within the `.Picker` component. | | `tabSpacing` | The horizontal spacing between `.Tab` components. | ## Other configuration options In addition to `themes`, `labels`, `inputs` and `variables`, you can style the Checkout form using other appearance configuration options. You can customise these by adding them to the appearance object: ```js const appearance = { disableAnimations: true, // other configurations such as `theme`, `labels`, `inputs`, and `variables`... } ``` We currently support the following options: | Configuration | Description | | ------------------- | -------------------------------------------------------------------- | | `disableAnimations` | Disables animations throughout the UI. Boolean, defaults to `false`. |