Skip to main content
The doTransaction method initiates and processes payment transactions within the TweezerComm protocol. It enables client applications, such as point-of-sale (POS) systems or electronic cash registers (ECRs), to interact with the Agamento payment terminal for secure transaction execution. This method supports multiple transaction types, including:
  • Regular Transactions (PreSelection): Standard payments using credit cards or closed-loop payment methods.
  • Pre-Authorization (initiation): Reserve a specified amount on a customer’s card for later confirmation.
  • Pre-Authorization Completion and Cancellation: Completing or voiding previously authorized transactions.
  • MOTO (Mail Order/Telephone Order) Transactions: Processing card-not-present transactions securely.
  • Refunds: Partial or full refunds of previous transactions.
  • Deferred Payments: Approving transactions even in cases where there is no immediate network connectivity.
The sections below will describe the request parameters in more detail:

Requests

JSON-RPC 2.0All methods in TweezerComm follow a JSON-RPC 2.0 structure. See Get Started for more details on how the requests are structured and sent.
In the request, the method field needs to be set to doTransaction. The transaction is defined by the tranCode parameter. Check the example request for each transaction type on the tabs below:
Mandatory Fieldsvuid, amount and tranType are mandatory for all requests. All others depend on the type of transaction made.
For a regular transaction, set the tranType parameter to 1. The code block shows a request example for a regular transaction:

Parameter Definitions

The table below describes all parameters available in this request:

Responses

The service will return a response structured similarly to the examples provided in the code blocks below:

Response Parameters

Below is a table with all the possible response parameters and their description: