Response Parameters

This reference documents all parameters returned by the Get Smart application after a transaction attempt. When the payment activity finishes, it returns an Intent to your application's onActivityResult method 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.

Common Response Parameters

The following parameters are returned for all transaction types. These fields provide essential information about the transaction outcome, authorization details, and payment method used.

Parameter KeyTypeAlways PresentDescription
RESULTStringYesTransaction outcome. Values: "AUTORIZADA" (approved) or "DENEGADA" (denied).
RESPCODEintYesResponse code indicating the specific reason for the transaction outcome. Use -1 as default value when extracting to distinguish from code 0.
ERROR_MSGStringConditionalHuman-readable error or denial reason. Present when transaction is denied or encounters an error.
AUTORIZATION_NUMBERStringConditionalAuthorization code assigned by the bank. Only present for approved transactions. Note the spelling (missing 'H').
IDENTIFIER_RTSStringYesUnique transaction identifier assigned by the Get Smart system.
ORDERStringYesOrder number associated with the operation. Required for refund operations as original_order parameter.
CARDBRANDStringConditionalBrand of the card used for payment. See Card Brands. Present for approved transactions.
information icon
Important: The authorization number key is spelled "AUTORIZATION_NUMBER" (missing the 'H'). You must use this exact string as the key to retrieve the value.

Transaction-Specific Response Parameters

Depending on the transaction type, additional parameters may be included in the response. The following table lists operation-specific fields that may be present.

Parameter KeyTypeTransaction TypesDescription
AUTHORIZATIONStringAll successful transactionsAlternative key for authorization code. Some transaction types may return this in addition to or instead of AUTORIZATION_NUMBER.
TICKET_IMAGEStringSuccessful transactions (Android < Q)File path to the receipt image for devices running Android versions below Q.
TICKET_DATAUriSuccessful transactions (Android ≥ Q)Content URI for accessing the receipt PDF on Android Q and above. Requires FLAG_GRANT_READ_URI_PERMISSION.
information icon
Note: Receipt access methods vary by Android version. For Android Q and above, use intent.getData() to retrieve the receipt URI. For earlier versions, use the TICKET_IMAGE extra to get the file path.

Response Values

Result Values

The RESULT parameter indicates the final transaction outcome. Always check this value first to determine if the transaction was successful.
ValueMeaningDescription
"AUTORIZADA"AuthorizedThe payment was successfully approved by the payment gateway
"DENEGADA"DeniedThe payment was rejected or failed

Card Brands

The CARDBRAND parameter returns the network of the card used for payment. This information is useful for receipts, analytics, and tracking payment method preferences.
ValueCard Network
"VISA"Visa
"MASTERCARD"Mastercard
"DINERS"Diners Club
"AMEX"American Express
"JCB"JCB
"CUP"China UnionPay

Response Code Values

The RESPCODE parameter provides specific reason codes for transaction outcomes, particularly useful for denied transactions. Response code values vary by payment gateway and card issuer. Common categories include:
  • Insufficient funds - Customer does not have enough balance
  • Expired card - Card expiration date has passed
  • Invalid card - Card number or details are incorrect
  • Restricted card - Card has been blocked or reported
  • Technical errors - Gateway or communication issues
For approved transactions, the response code is typically 0. For denied transactions, consult with Get Smart support for specific code meanings relevant to your merchant configuration.

On this page

Response Parameters