Android UI components
The Afterpay Android SDK includes prebuilt views that follow the brand guidelines for each region. This guide shows the Afterpay branding that merchants in Australia, New Zealand, and Canada display.
All components are in the com.afterpay.android.view package. You can add any of them in an XML layout or create them in Kotlin. You must initialize the checkout widget in code.
Configure the SDK first
The components read your merchant configuration to choose the brand, language, currency format, and order limits. Call Afterpay.setConfiguration before you inflate or create any component. For details, see Configure the SDK.
Each component resolves its color scheme for the configured locale when you create it or set its style. When the configuration changes, the payment button rechecks its visibility and the price breakdown refreshes its text, but neither changes its color scheme. The logo views and the checkout widget don’t update. To avoid views that show the wrong brand or stay hidden, set the configuration first.
How the SDK chooses the brand
The SDK picks the brand from the locale you pass to Afterpay.setConfiguration. This is your merchant region, not the device locale.
You don’t select the brand directly. The same layout renders Afterpay branding for merchants in Australia, New Zealand, and Canada, Clearpay branding for UK merchants, and Cash App Afterpay branding for US merchants.
Styles and color schemes
The payment button, logo views, and price breakdown each have a style property of type AfterpayWidgetStyle, and an equivalent app:afterpayStyle XML attribute. The checkout widget doesn’t have a style. The style is semantic: the SDK maps it to the color scheme for the configured locale.
Outside the US, the styles map to the Afterpay and Clearpay color schemes:
The default style is Default. The color schemes are internal to the SDK, so you select them only through style or app:afterpayStyle.
The logo lockup has no background. With the Default style, the Afterpay wordmark is black, so use Default or MonochromeLight, which looks the same, on light backgrounds. On dark backgrounds, use Alt or MonochromeDark.
Set the style in XML:
Or in Kotlin:
Declare the app namespace, xmlns:app="http://schemas.android.com/apk/res-auto", on the root element of your layout.
US merchants
For US merchants, the same styles map to the Cash App Afterpay color schemes:
The lockup guidance is reversed in the US: Default suits dark backgrounds and Alt suits light backgrounds. If your app serves US and other regions, choose the lockup style for the configured region.
When components are hidden
A component hides itself, by setting its visibility to View.GONE, when the SDK isn’t enabled for the current configuration. The SDK tracks this internally as Afterpay.enabled, which isn’t part of the public API. The SDK is enabled only when both of these are true:
- You set a configuration with
Afterpay.setConfigurationorAfterpay.setConfigurationV3. - The customer’s language is supported in your merchant region.
The SDK takes the customer’s language from the consumerLocale you pass to setConfiguration. If you don’t pass one, it uses the device’s default locale.
For example, a US merchant’s components hide themselves on a device set to Spanish, unless you pass consumerLocale = Locale.ENGLISH.
Some components also have rules of their own:
AfterpayBadgeis always hidden for US merchants, because Cash App Afterpay branding uses the lockup instead. See Logo.AfterpayPriceBreakdownsupports only the lockup logo for US merchants. See Price breakdown.





