Mobile app vs SDK responsibilities
About
The Wallets SDK provides methods to simplify the Wallets management and payment.
The list belows outlines who is responsible for the UI that the consumer sees.
The Mobile App owns some of the UI to get some additional control over the flow and look. UI owned by Aera can be customized to some degree using the Branding option defined under "Merchant Specific Preferences". Related push messages and notifications to the Mobile App are always handled by the Mobile App.
| UI | Related SDK Methods | Aera UI | Mobile App UI | Notes |
|---|---|---|---|---|
| Authenticating user (Identity providers, Biometrics, app pin) | getOpenWalletURL | X | Mobile App can add their own intermediate UI between onboarding and opening of wallet | |
| Wallets dashboard | getOpenWalletURL openURL | X | Mobile App is responsible for opening Aera Wallets Dashboard via openUrl using the URL provided by Aera Wallets SDK method getOpenWalletURL. The WSP Config can add branding to the dashboard, see "Merchant Specific Preferences" section. | |
| Payment UI | getPaymentInfo signPayment | X | Payment details provided by Aera Wallets SDK method getPaymentInfo. Mobile App handles the user interaction for payments and triggers signPayment or cancelPayment. |
Implementation details are found under each SDK method outlined under Definitions
Updated 3 months ago
Did this page help you?
