No results

Payment confirmation (Accounting request)

Confirmation allows you to request posting of an authorised transaction. Confirmation can be only requested once and the posting amount can be total or partial.

Confirmation operation is supported by the following payment methods:

  • Credit cards, debit cards and prepaid

Transmission of payment capture message

Example of HTTP payment-confirmation message
id=99999999&password=99999999&tenantId=10&operationType=confirm&amount=1.00& currencyCode=978& merchantOrderId=TrackingNo12345&paymentId=123456789012345

Call parameters of HTTP payment-confirmation message

NAME DESCRIPTION FORMAT
id Id associated with terminal N
Max. length: 8
password Terminal id password AN
Max. length: 50
tenantId Identification code of the acquiring service to which the merchant belongs. In the case of a merchant having an agreement with Intesa enter "10", otherwise enter "20". N
operationType 'confirm' AN
Max. length: 50
amount Transaction amount using the point as decimal separator (e.g. 1428,76€ = "1428.76"). The decimal portion may vary depending on the currency N Int. 18 - Dec. 4
currencyCode Currency numeric code (optional – default '978' [euro]) N
Max. length: 3
merchantOrderId Transaction reference sent by the merchant during Initialization (can contain only letters and numbers and must be absolutely unique) AN
Max. length: 18
paymentid Unique identifier of the Gateway authorization request AN
Max. length: 18
customField Custom field AN
Max. length: 255
description Payment description AN
Max. length: 255
Example of XML message with payment outcome

Parameters of response to confirmation message

NAME DESCRIPTION FORMAT
paymentid Unique identifier of the Gateway authorization request AN
Max. length: 18
result Confirmation outcome:
  • CAPTURED = confirmed transaction
AN
Max. length: 20
responsecode Response code (e.g. '000' if the transaction is authorised, in all other cases the transaction is rejected) N
Max. length: 3
authorizationcode Authorisation code, which is entered only if the transaction has been authorised AN
Max. length: 6
merchantorderid Transaction Reference sent to the merchant in Initialisation phase (can contain only letters and numbers and must be absolutely unique) AN
Max. length: 18
description Payment description AN
Max. length: 255
customfield Custom field sent to the merchant in Initialisation phase AN
Max. length: 255

Behaviour of the system in case of error upon confirmation

If incorrect parameters are sent (e.g. unknown terminal, incorrect password, attempt to confirm an already confirmed payment, attempt to confirm a payment for an amount higher than as authorised,...) the Gateway responds with an error message in XML format.

This message includes:

  • an error code
  • a mnemonic description of the error

Example of error message in confirmation phase: