Getnet DocsGetnet Docs

Transaction Types

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

The Get Mini App2App integration supports three transaction types: Payments, Refunds, and Queries. Each transaction type serves a specific purpose in the payment lifecycle and requires different parameters.

Payment Transactions

A payment transaction processes a charge against a cardholder’s account. This is the most common operation, used when a customer purchases goods or services at your point of sale.

To process a payment, you need to provide the transaction amount and optionally an order identifier. Your app creates a payment Intent, the Get Mini app launches and manages the card interaction with the PIN pad, then returns the authorization result to your application.

For implementation details, see Process a Payment.

Refund Transactions

A refund transaction reverses a previous payment, returning funds to the cardholder’s account. Use this when a customer returns goods or when you need to correct an erroneous charge.

To process a refund, you must provide the original transaction details including the authorization number, order number, date, and the refund amount. The refund amount can be less than or equal to the original payment amount, allowing for partial refunds. Note that refund availability may depend on the card issuer and the time elapsed since the original transaction.

For implementation details, see Refund a Payment.

Query Operations

A query operation retrieves transaction history or status information for operations performed within a specific date range. This is useful for reviewing transaction history, reconciling end-of-day reports, or investigating specific transactions.

To perform a query, you specify a date range using start and end dates in YYYYMMDD format. The Get Mini app retrieves the transaction data and returns it to your application, typically as a formatted report or certified ticket.

For implementation details, see Query Operations.

Response Data

Every transaction type returns a result code in the Intent callback — RESULT_OK or RESULT_CANCELED — plus the state code, an error message when one applies, and the URL of the generated certified ticket PDF. A payment also returns the authorization number, the transaction identifier and the order number; a query and a refund do not.

For complete details on response handling, see Handle Transaction Results.