430 Integration

This page contains the required fields for integration with the 430 device.

Manifest.xml Configurations

<manifest ... >
    ...
    <application ... >
        ...
        <meta-data android:name="app_name" android:value="BNK_ID_COMPANYNAME" /> 
        <meta-data android:name="app_model_type" android:value="430TR" /> // For 430TR devices
        <meta-data android:name="app_version" android:value="43000110" /> // Change Android  Version major/minor/build into integer. We kindly request this change. Version no must start with 430. Example: 43000110.
     </application>
...

To convert version name to manifest data, you can use following example in your build.gradle

apply plugin: 'com.android.application'

// This section is parsing Android manifest file, reads version in the meta-data tag, writes it into version name in gradle
// so that the version shown in the android settinsg is same as version in the meta-tag
def versionFromManifest

task parseManifest() {
    def manifest = new XmlSlurper().parse(file(android.sourceSets.main.manifest.srcFile)).declareNamespace(android: 'http://schemas.android.com/apk/res/android');
    println manifest.@package
    manifest.application["meta-data"].each {
        def m = it.attributes()['android:name'] =~ /app_version/
        if (m.find()) {
            versionFromManifest = it.attributes()['android:value'].toString()
        }
    }
}

android {
    compileSdkVersion 28
    defaultConfig {
        applicationId "com.example.atms_alpha"
        minSdkVersion 26
        targetSdkVersion 28
        versionCode versionFromManifest.toInteger()
        versionName "${versionFromManifest}"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        setProperty("archivesBaseName", "ATMS_Alpha_" + versionFromManifest)

    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
}

Device Info

void getFiscalId(DeviceInfoResponseHandler deviceInfoResponseHandler)

The getFiscalId function retrieves the fiscal ID from the service.

deviceInfo.getFiscalId(object: DeviceInfoResponseHandler {
    override fun onSuccess(result: String) {
        Log.i("Fiscal ID", result)

    }
    override fun onFail(errMessage: String) {
        Log.i("Error Message", errMessage)
    }
});

Note: The Fiscal ID will be in the format AW......

void getDeviceMode(DeviceInfoResponseHandler deviceInfoResponseHandler)

The getDeviceMode function retrieves the device mode from the service.

deviceInfo.getDeviceMode(object : DeviceInfoResponseHandler {
    override fun onSuccess(result: String) {
        Log.i("Device Mode", result)
        // "POS"
    }

    override fun onFail(errMessage: String) {
        Log.i("Error Message", errMessage)
    }
})

public enum PosModeEnum {
    VUK507,
    POS,
    GIB,
    ECR,
    EFT_POS,
    RESERVED_0,
    RESERVED_1,
    RESERVED_2,
    RESERVED_3,
    RESERVED_4,
    CY // CYPRUS    
}

NOTE: The deviceMode value of the device will be POS.

Important Considerations

UI

UI behavior is identical to the X30TR device. Therefore, if UI separation is implemented via BuildConfig checks in your codebase, the relevant conditional statements should be reviewed.

For QR display flows, if the QrScreen330 fragment is used on the X30TR, the same fragment can be reused on the 430TR.