Request Parameters

This reference documents the Intent action and parameter specifications required to communicate with the Get Smart application. All parameters must be passed as Intent extras using the putExtra() method. Parameter keys are case-sensitive and must match the specifications exactly.

Intent Action

To initiate a transaction request, your application must create an Intent with the following action string.

Intent Action
es.android.redsys.mPOS.movil.tpvAndroid_PAYMENT_REQUEST
This single Intent action handles all transaction types (sales, refunds, and summaries). The specific operation is determined by the type parameter.

Request Parameters

The following table lists all available request parameters. Use intent.putExtra() to include these fields in your request.
ParameterTypeRequiredDescription
amountdoubleConditionalTransaction amount (e.g., 12.50). Required for sales and refunds. Not required for summaries.
typeintYesOperation type identifier. See Transaction Types for valid values.
invoiceStringNoMerchant reference identifier or order number for internal tracking.
original_orderStringConditionalRequired for refund operations. Must match the ORDER ID returned by the Get Smart from the original sale transaction.
original_dateStringNoDate of the original transaction in DD/MM/YYYY format. Used only for refund operations to help identify the original transaction.

Transaction Types

The type parameter determines which operation the Get Smart application will process. The following values are supported:
Type ValueOperationDescriptionRequired Parameters
1SaleProcesses a standard payment transaction.amount, type
2RefundReverses a previous sale transaction and returns funds to the customer.amount, type, original_order
3SummaryTriggers batch closure (totalización) to reconcile all transactions for the day.type

Sale Transactions

Sale transactions process customer payments and require the transaction amount. The Get Smart application manages the card interaction, PIN entry, and communication with the payment gateway. Upon completion, the application returns transaction details including the authorization code and order ID.

Refund Transactions

Refund operations reverse a previous sale and require reference to the original transaction. You must provide the original_order value that was returned in the original sale response. The refund amount can be equal to or less than the original transaction amount, allowing for partial refunds. The original_date parameter is optional but recommended to help identify the transaction.

Summary Operations

Summary operations close the daily batch of transactions for reconciliation purposes. This operation does not process individual transactions but triggers the Get Smart's totalization process. No amount or order information is required for summaries.

Parameter Validation

The Get Smart application validates all incoming parameters before processing. Common validation errors include:

  • Missing required parameters (type must always be provided)
  • Invalid type values (must be 1, 2, or 3)
  • Missing amount for sales or refunds
  • Missing original_order for refund operations
  • Incorrect data types for parameters
information icon
Note: Always validate your parameters before launching the Intent to avoid transaction errors and provide a better user experience.

For implementation guidance and code examples, see:

On this page

Request Parameters