In-App Push Provisioning Android SDK
The In-App Push Provision (IAPP) allows to build provisioning bundles for different wallets and different tokenization platforms.
Every OEM Pay wallet has its own In-App provisioning specification. Generally, the wallet will either:
Pass all data received from the Mobile Application as opaque down to the tokenization platform (Google Pay, goodylabs Wallet Management Server) or
Decrypt data received from the Mobile Application and pass down the card data along authentication code (Apple Pay)
Scope
This service allows Issuer Mobile Applications to easily push a card into an OEM device wallet that might remove the need for running any ID&V process.
Introduction
Welcome to the In-App Push Provisioning SDK User guide.
The In-App Push Provision (IAPP) allows to build provisioning bundles for different wallets and different tokenization platforms.
Prerequisites
Android version supported
min sdk: 24
Setup
dependencyResolutionManagement {
repositories {
mavenLocal()
}
}
dependencies {
implementation("com.google.android.gms:play-services-tapandpay:18.3.3")
implementation("com.goodylabs:iapp:0.2.0")
}Usage
The com.goodylabs.iapp.goodylabsSdk is the main entry point of the In-app push provisioning SDK.
To call asynchronous API methods code should be placed inside coroutine scope.
For example:
viewModelScope.launch {
val results = goodylabsSdk.getInstance().findCardsByCardHolder(/** params **/)
// do something with results
}Methods
Changelog
v0.2.0
replaced
AppCompatActivitywithActivityinstartPushProvisioning()and removed activity argument fromnotifyProvisioningCompleted()removed wallets arguments from
checkCards()andcanAddCards()changed return type in
canAddCardsmethod toMap<String, Map<Wallet, Eligibility>>all exceptions are now caught by the SDK and default values are returned (empty lists/maps and false values)
migration from kotlinx.serialization to com.fasterxml.jackson
v0.1.0
Initial version