Getnet DocsGetnet Docs

Intent Parameters

This reference page lists all the input parameters (Intent “extras”) you can use when communicating with the Tap on Phone application.

You must pass these parameters using the putExtra() method when building your Intent objects. The required parameters vary depending on the action you are performing (such as initializing the POS, processing a payment, or broadcasting a request).

Authentication and Session Parameters

These parameters manage user identity, terminal linking, and Single Sign-On (SSO) authorization. They are mandatory for almost all operations, including initializations, transactions, and background attestations.

Parameter NameData TypeRequiredDescription
userIdIntYesYour system’s technical identifier for the current user/merchant.
userTokenStringYesThe secure authentication token for the user. The Tap on Phone backend sends this token to your SSO endpoint to authorize the operation.
merchantIdIntYesThe unique Tap to Pay ID representing the merchant business. You receive this identifier during the merchant onboarding process.
operationMetadataStringConditionalA serialized JSON string required for SSO authorization. It must contain your ClientID (e.g., {"ClientID":"your-client-id"}). Required for initialization, refunds, and cancellations.

Transaction Parameters

You pass these parameters to the POSActivity when initiating financial operations.

Parameter NameData TypeRequiredDescription
transactionTypeStringYesDefines the operation. Accepted values: PURCHASE, REFUND, CANCEL, PREAUTH, WITHDRAW.
amountLongYesThe total amount of the transaction in cents (e.g., pass 1200 for $12.00). Note: For purchases, this must include any tips.
tipLongNoThe tip amount in cents. This is strictly metadata. The application does not add this value to the amount automatically.
originalTransactionIntConditionalThe Tap on Phone transaction ID of the original payment. Required only when the transactionType is REFUND or CANCEL.
paymentModeStringNoSpecifies the payment method. Defaults to Card. Accepted values: Card, Link (if supported by your merchant configuration).
externalTransactionReferenceStringNoYour internal system’s reference ID for this order. If provided, the application attaches this string to the transaction receipt.
acquirerMetadataStringNoA serialized string attached to the transaction data and forwarded to the payment acquirer. You can use this for advanced reporting or fraud prevention logic agreed upon with your gateway.

User Interface and Behavior Parameters

You can use these parameters to modify how the Tap on Phone payment screen behaves and appears to the user.

Parameter NameData TypeRequiredDescription
localeStringNoForces a specific language for the payment screen. Format as LANGUAGE, LANGUAGE_COUNTRY, or LANGUAGE-COUNTRY (e.g., en_US, fr_FR). Defaults to English if the requested language is unsupported.
transitionAutoBooleanNoIf true, the Tap on Phone application automatically transitions and returns control to your application immediately after the transaction finishes. If omitted or false, it retains its default manual closure behavior.

Broadcast Parameters

You use these parameters when sending asynchronous Android Broadcasts (e.g., to check status, force attestation, or query past transactions).

Parameter NameData TypeRequiredDescription
TransactionIdStringConditionalThe UUID of the transaction you want to check. Required only when sending a TRANSACTION_STATUS_BROADCAST.
ResponseActionStringNoA custom action name you define. The Tap on Phone application will emit its response broadcast using this exact string instead of its default action name.