Installments

Regional Scope: The specifications and requirements detailed on this page apply exclusively to Host-to-Host integrations for Pinpad operations in Argentina.

Getnet provides a specialized endpoint for querying installment plans (cuotas), which automatically applies relevant interests and promotions. This section outlines the mandatory procedures for handling installment transactions within the Argentinian market.

Installment inquiry and QUOTE ID

For many installment schemas, the Host System is required to invoke the Getnet installments endpoint prior to initiating the transaction. This process is essential to retrieve a QUOTE ID, a unique identifier that tracks the installment transaction throughout the Getnet ecosystem. The QUOTE ID is returned in the response associated with the specific plan and number of installments selected.

Requirement matrix

The following table determines if a specific installment schema requires a mandatory endpoint query to obtain a QUOTE ID:

Installment Schema	Inquiry Required?
`plan_emisor`	Yes
`plan_emisor_accelerated`	Yes
`plan_ahora`	Yes
`cuota_simple`	Yes
`plan_n`	Yes
`pago_en_cuota`	Yes
`plan_amex`	Yes
`plan_z`	No
`alphanumeric`	No
`sin_interes`	No
`con_interes`	No
`plan_normal`	No
`plan_diferido`	No
`plan_especial`	No
`plan_convenio`	No
`plan_1`	No
`plan_2`	No
`plan_3`	No
`plan_4`	No
`cuotas`	No

If a plan does not require an inquiry, the partner should send the transaction directly without a quote_id.

Interests and promotions

The Host System has two options for managing financial calculations:

Self-Managed Calculations: If the partner system calculates interests and promotions internally, it must still perform a “SIN INTERESES” (Without Interest) query to the endpoint to obtain the necessary QUOTE ID.
Getnet-Managed Calculations: If the partner prefers Getnet to handle calculations automatically, it must perform an inquiry (either “SIN INTERESES” or “CON INTERESES”) based on the payment method selected during the sale.

Installment selection and conversion

Getnet expects to receive the exact payment plan and installment count selected by the user in the API request.

Installment converter

In cases where the Host System uses a specific “installment quantity” to identify a plan, a converter must be developed and applied before sending the request to Getnet.

Example: A system might use “11 installments” as a code to identify a Plan Emisor in 6 installments.
Action: When the operator enters “11” in the system, the Host System must convert this value to “Plan Emisor 6 installments” and create the request with those values.

QR code installments

For transactions utilizing QR Codes, the flow differs from standard card payments:

Transactions must be generated without any prior calculation of taxes or interest.
The customer selects the desired installments directly within their digital wallet.
The transaction response returns all necessary information to the Point of Sale (PDV) based on the customer’s selection.

Next steps

Process Card Payments: send the installment values inside the standard Y19 initialization.
Process QR Code Payments: run the wallet flow where the customer chooses the installments.
Code Tables: look up the transaction type and account type codes used in the requests.