Cards & Wallets · Mobile SDK

UI Components

The UI components are pre-defined Compose components used to collect the cardholder information securely, without raising the PCI scope for the merchant or integrator of the Mobile SDK.
The Compose components and the CardInputView / CardInputSlimView Android Views are annotated @ExperimentalMobileUI. Add @OptIn(ExperimentalMobileUI::class) wherever you reference them from Kotlin; the other Android Views and the iOS controllers need no opt-in.

Components

ComponentDescription
Card InputCollect the cardholder details securely. Three lines of space, a more spaced-out component.
Card Input SlimCollect the cardholder details securely in one to two lines of space.
Billing AddressCollect the billing address in a form view. Optional.
SaveCardBoxA checkbox UI to determine whether the cardholder information can be saved for later use. Optional.
SavedCardsA simple list of the current customer’s saved cards, letting the user choose between them for the current payment session or use a new card.
Google Pay ButtonA simple Google Pay button managed by us.

Variants

Most components are available in three variants:

ComposablesViewsUIViewControllers
CardInputCardInputViewCardInputController
CardInputSlimCardInputSlimViewCardInputSlimController
BillingAddressComponentBillingAddressViewBillingAddressController
GooglePayButton (Android only)GooglePayButtonView (Android only)-
SaveCardBoxSaveCardViewSaveCardBoxController
SavedCardsSavedCardsViewSavedCardsController

There is no pre-defined Apple Pay component: build the button with PassKit and call PaymentProcessor.processApplePayPayment from it. See Apple Pay Button.