Get Smart App2App Overview

The Get Smart App2App solution defines a connection method between the generic Get Smart application and an external third-party application. This integration enables your application to send payment requests directly to the Get Smart payment module and receive transaction results programmatically.

This architecture allows you to add card payment functionality to your Android application while avoiding the significant costs and complexities associated with certifying a complete payment solution.

Architecture and Workflow

The integration relies on standard Android Intent mechanisms to facilitate communication between two distinct applications installed on the same device:

The external app (your app) initiates the process.
The Get Smart app processes the secure transaction.

The Transaction Flow

The interaction follows a synchronous request-response model:

Your application generates an Android Intent specifically named es.android.redsys.mPOS.movil.tpvAndroid_PAYMENT_REQUEST. This intent carries necessary operation data, such as the amount and transaction type (sale or refund).
Your application launches this intent using startActivityForResult, effectively handing control over to the Get Smart application.
The Get Smart application handles the financial transaction logic, card reading, and communication with the payment gateway.
Once the transaction concludes, the Get Smart application returns control to your application. It provides a result code (indicating success or cancellation) and additional data describing the transaction outcome (such as authorization numbers or error messages).

Receipt Printing: The Getnet application remains responsible for printing the merchant receipt (if applicable) and offering the option to print the customer receipt. Your application does not need to handle print logic.

Key Benefits

The App2App integration offers several advantages:

You do not need to implement low-level EMV or contactless payment logic, which simplifies integration.
By offloading the payment processing to the certified Get Smart application, you avoid the costs associated with certifying your own payment solution.
The integration does not require specific permissions in your application's AndroidManifest.xml file, ensuring minimal configuration.

Requirements

To utilize this architecture, the generic Get Smart application ("Aplicación de Cobro") must be installed and updated on the target Android device. If the application is not present, the intent call will fail, and you must handle this exception gracefully (e.g., by alerting the user).

Next Steps

Continue exploring the App2App integration: