Response Parameters
This reference documents all parameters returned by the Get Mini application after a transaction attempt. When the operation finishes, it returns an Intent to your application’s ActivityResult callback with transaction details stored as extras.
Accessing Response Data
Response parameters are retrieved from the Intent using getStringExtra() or getIntExtra() methods with the parameter keys listed below. All keys are case-sensitive and must match exactly.
Response Parameters by Operation
The Get Mini app returns a different set of extras for each operation. Read the keys listed for the operation you launched. All keys are case-sensitive.
After a payment
| Parameter Key | Type | Description |
|---|---|---|
TICKET_IMAGE | String | URL of the generated PDF with the certified receipt. |
AUTORIZATION_NUMBER | String | Authorization number. |
IDENTIFIER_RTS | String | Transaction identifier. |
ORDER | String | Order number. |
STATE | String | Result code. |
ERROR_MSG | String | Error description. |
The authorization key is spelled AUTORIZATION_NUMBER, without the ‘H’. Use that exact string.
After a query
| Parameter Key | Type | Description |
|---|---|---|
TICKET_IMAGE | String | URL of the generated PDF with the certified receipt. |
STATE | String | Result code. |
ERROR_MSG | String | Error description. |
After a refund
| Parameter Key | Type | Description |
|---|---|---|
TICKET_IMAGE | String | URL of the generated PDF with the certified receipt. |
STATE | String | Result code. |
ERROR_MSG | String | Error description. |
Receipt Access
Receipt access methods vary by Android version. The Get Mini application provides different mechanisms for accessing transaction receipts:
| Method | Android Version | Description |
|---|---|---|
TICKET_IMAGE extra | < Android Q | File path to the receipt PDF stored on the device. |
intent.getData() | ≥ Android Q | Content URI for accessing the receipt PDF. Requires FLAG_GRANT_READ_URI_PERMISSION. |
For Android Q and above, use intent.getData() to retrieve the receipt URI instead of the TICKET_IMAGE extra.
State Values
STATE carries the result code of the operation, and the denial code when the operation is declined.
See Result and Errors Codes for how to read it.
Data Handling Best Practices
When processing response parameters, follow these guidelines to ensure robust transaction handling:
- Verify Intent data - Always check that the Intent is not null before extracting parameters
- Check STATE first - Always verify the
STATEparameter before processing other fields - Store critical fields - Save
AUTORIZATION_NUMBER,ORDER, andIDENTIFIER_RTSfor all successful transactions - Handle missing fields - Not all parameters are present in every response. Check for null values before using strings
- Add timestamps - Store your own timestamp when recording transaction data for accurate reconciliation
- Manage receipts - Handle both file path and URI methods depending on Android version
The ORDER parameter must be stored for successful payment transactions as it is required for processing refunds.
Related Resources
- Handle Transaction Results - Complete guide on processing transaction responses
- Request Parameters - Request parameter reference
- Result Codes and Errors - Complete error code reference