Get Smart App2App Overview

This topic provides a conceptual overview of the Redsys App2App integration for Android. It explains the architecture that allows your external application to communicate with the Redsys TPV application to process payments.

Introduction

The App2App solution defines a connection method between the generic Redsys Android TPV application and an external third-party application. This integration enables your application to send payment requests directly to the Redsys 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

1. The external app (your app) initiates the process.
2. The Redsys TPV app processes the secure transaction.

The Transaction Flow

The interaction follows a synchronous request-response model:

1. 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).
2. Your application launches this intent using startActivityForResult, effectively handing control over to the Redsys application.
3. The Redsys TPV application handles the financial transaction logic, card reading, and communication with the payment gateway.
4. Once the transaction concludes, the Redsys 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 Redsys financial 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 Redsys 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

Next Steps

Continue exploring the App2App integration:

• Learn about the specific installation requirements in Prerequisites and Configuration.
• Follow step-by-step instructions to implement the payment Intent in Processing a Transaction.
• View the detailed list of parameters available for the payment request in Request API Reference.