Customization
Customize your Web unified checkout
You can customize the Unified Checkout to support your checkout context and brand guidelines by using Layouts and Styling APIs
1. Layouts
Choose a layout that fits well with your UI pattern. There are two types of layout options as listed below. The layout defaults to accordion if not explicitly specified.
1.1 Accordion layout
The accordion layout displays payment methods vertically using an accordion. To use this layout, set the value for layout to accordion. You also have the option to specify other properties, such as those shown in the following example.
1.2 Tabs layout
The tabs layout displays payment methods horizontally using tabs. To use this layout, set the value for layout to tabs. You also have the option to specify other properties, such as tabs or collapsed.
2. Wallets
The wallet customization feature lets users configure payment options like Apple Pay, Google Pay, PayPal, and Klarna. It includes a walletReturnUrl
for post-payment redirects and a style
property to customize the wallet's appearance, offering flexibility for seamless integration.
3. Styling variables
The Styling APIs could be used to blend the Unified Checkout with the rest of your app or website.
4. Rules
The rules option is a map of CSS-like selectors to CSS properties, allowing granular customization of individual components. After defining your theme and variables, use rules to seamlessly integrate Elements to match the design of your site. The selector for a rule can target any of the public class names in the Element, as well as the supported states, pseudo-classes, and pseudo-elements for each class. For example, the following are valid selectors:
.Tab, .Label, .Input
.Tab:focus
.Input--invalid, .Label--invalid
.Input::placeholder
.billing-section, .billing-details-text
Each class name used in a selector supports an allowlist of CSS properties that you specify using camel case (for example, boxShadow for the box-shadow property). The following is the complete list of supported class names and corresponding states, pseudo-classes, and pseudo-elements.
Tabs
.Tab, .Label, .Input
.Tab:focus
.Input--invalid, .Label--invalid
.Input::placeholder
Each class name used in a selector supports an allowlist of CSS properties that you specify using camel case (for example, boxShadow for the box-shadow property). The following is the complete list of supported class names and corresponding states, pseudo-classes, and pseudo-elements.
Tabs
Form Inputs
Checkbox
5. Languages
Hyperswitch Unified Checkout supports localization in 6 languages. By default, the Unified Checkout SDK will detect the locale of the customer’s browser and display the localized version of the payment sheet if that locale is supported. In case it is not supported, we default to English. To override, you can send locale in hyper.elements (options)
We support the following locales -
Arabic (ar)
Catalan (ca)
Chinese (zh)
Deutsch (de)
Dutch (nl)
English (en)
EnglishGB (en-GB)
FrenchBelgium (fr-BE)
French (fr)
Hebrew (he)
Italian (it)
Japanese (ja)
Polish (pl)
Portuguese (pt)
Russian (ru)
Spanish (es)
Swedish (sv)
If you need support for locales other than the ones mentioned above, please contact the Hyperswitch team. Now you can test the payments on your app and go-live!
6. Confirm Button
The Styling APIs could be used to blend the Confirm Payment Button (handled by SDK) with your app.
7. More Configurations
Branding
You can decide whether to display the Hyperswitch branding using the branding
prop
Payment Methods Header Text
Customize the header text for the section displaying available payment methods.
Saved Payment Methods Header Text
Customize the header text for the section displaying saved payment methods.
Custom Message for Card Terms
We provide a default message for card terms i.e.
If you would like to customize this message, you can do so by using the customMessageForCardTerms
property in the paymentElementOptions
object.
Hide Card Nickname Field
The hideCardNicknameField
property allows you to hide the card nickname field when saving a card.
Hide Expired Saved Payment Methods
The hideExpiredPaymentMethods
property allows you to control whether expired saved payment methods are hidden or not.
Show Card Form by Default
The showCardFormByDefault
property determines whether the card form is displayed by default or not.
Terms
The terms
property allows you to configure the display of terms for various payment methods.
Display Saved Payment Methods
The displaySavedPaymentMethods
property determines whether saved payment methods are displayed.
Display Saved Payment Methods Checkbox
The displaySavedPaymentMethodsCheckbox
property determines whether the "Save payment methods" checkbox is displayed.
Payment Method Order
The paymentMethodOrder
property allows you to specify the order in which payment methods are displayed.
Business
The business
property allows you to specify a business name to be attached to the terms. By default merchant name will be taken as business name.
Read Only
The readOnly
property puts the SDK into read-only mode, disabling all interactions.
Next step:
Last updated