Android library for integrating payments into a mobile app.

• sdk_core - the source code of the base part of the library.
• sdk_forms - the source code of the UI part of the library.
• sdk_payment - the source code of the full payment cycle.
• documentation - documentation on integrating the sdk into applications.
• app_kotlin_core - an example of using the library in a kotlin application without UI.
• app_kotlin_ui - an example of using the library in a kotlin application with UI.
• app_java_ui - an example of using the library in a java application with UI.
• config - code validation configurations.

It uses the library copying, instead of setting up a dependency on the sdk subproject, to reproduce all the integration steps of the sdk application as in the end user.

Before building the examples, you need to change the sdk_threeds module dependency in the file sdk_payment / build.gradle.kts This is required for Gradle to use the aar artifact, which will be loaded by the copy_sdk_lib_to_samples.sh script. The source code of the sdk-threeds module is not included in the project as it contains implementation details of the security system and is supplied as an aar artifact.

dependencies {
    implementation(project(":sdk_forms"))
//    implementation(project(":sdk_threeds"))
    implementation(group = "", name = "sdk_threeds-release", ext = "aar")
    implementation(project(":sdk_core"))

And run the command

./copy_sdk_lib_to_samples.sh

The script will build and add the library files to the examples (in the libs folder).

If you use .aar compiled files (sdk_forms-release.aar, sdk_payment-release.aar or sdk_threeds-release.aar) in your Android project you don’t have to do anything. The specific rules are already bundled into the AAR files which can be interpreted by R8 automatically.

If you, however, don’t use R8 compiler as a default, you have to apply the rules from file proguard-rules.pro which is located in each module (sdk_forms, sdk_payment and sdk_threeds).