T1 PRO-TMC
This page contains the required fields for integration with the T1 PRO device.
This device will support two operating modes: ECR and TMC. All flows will be identical in both modes.
Bank App Protocol
The transaction flows for this device follow the exact same standards as our existing devices. You can access the relevant integration flows and detailed guide via the link below
Bank App ProtocolManifest.xml Configurations
<manifest ... >
...
<application ... >
...
<meta-data android:name="app_name" android:value="BNK_ID_COMPANYNAME" />
<meta-data android:name="app_model_type" android:value="T1PRO" /> // For T1 Pro devices
<meta-data android:name="app_version" android:value="51000110" /> // Change Android Version major/minor/build into integer. We kindly request this change. Version no must start with 510. Example: 51000110.
</application>
...Device Info
The TMC value has been added to the posMode enum. To use the updated posMode enum, you need to update the AAR in your project.
Pos Mode
The deviceInfo.getOperationMode function retrieves the Pos Mode from the service.
NOTE: On TMC devices, this value will be reported as TMC. There will be no differences in the flows between POS Mode TMC and POS Mode ECR.
FiscalID
The deviceInfo.getFiscalId function retrieves the fiscal ID from the service.
Note: For Pos Mode ECR devices, the Fiscal ID will be in the format AY.....
Note: For TMC devices, the fiscal ID will be T1A.........
Card Service
Please include the updated CardServiceBinding AAR in your project. This version resolves the compatibility issue in applications with a targetSdkVersion of 34 or higher and can also be used without issues in applications with a targetSdkVersion below 34.
Important Considerations
Device Name
Device name will be "T1PRO".
When the device model information is obtained using the Build.MODEL field, it returns the value T1PRO for the corresponding device.
UI Components V2
NOTE: uicomponents_v2.aar will be used only on T1Pro and TMC devices for now.
If your projects share the same codebase, uicomponents_v2.aar should be used only for T1Pro devices. This can be implemented using product flavors.
Required Changes for UI Components V2 Migration
1-) Set Theme
NOTE: You need to set the theme in the onCreate() method of all your Activities. Please note that ThemeManager is not available in uicomponents_v1
2-) EditTextInputType.Date
To use the date input feature, you need to update the RecyclerView version in your build.gradle file. A version of 1.2.1 or later is sufficient.

UI Components V2 Screens
ListMenuFragment


InputListFragment

Confirmation Dialog
Dialog types: Confirmed, Warning, Error, Info, Declined, Connecting, Downloading, Uploading, Processing, Progress, None






InformationDialog
Dialog types: Confirmed, Warning, Error, Info, Declined, Connecting, Downloading, Uploading, Processing, Progress, None





QR Screen

Printer Service
Our new printer library provides three APIs. Their descriptions and usage examples are provided below.
void printBitmap(String name, int verticalMargin)
void printAdditionalLogo(byte[] bitmapData, int margin)
You can print your monochrome logo as a bitmapArray using this API. This is the recommended approach.
void printAdditionalLogo(int resID, int margin)
The static logos you place in the raw folder will be printed using this method. The logos must be monochrome. This is the recommended approach.
Last updated

