Maintenance Work Notice!

We will carry out maintenance work on this documentation on Tuesday, 15.06.2021 between 3 pm and 4 pm CEST. Thank you for your understanding.

Page tree

Search

Skip to end of metadata
Go to start of metadata


Product overview

Rationale

Where the final amount will exceed or is likely to exceed the amount of the pre-authorization (including any scheme allowed percentage variation), a further incremental authorization may be obtained. The incremental authorization will be for the difference between the original pre-authorization and the actual or estimated final amount. The sum of all linked estimated and incremental authorizations represent the total amount on hold in the cardholder’s account for a given transaction.

By using incremental authorizations merchants can ensure the cardholder’s open-to-buy accurately reflects their transaction activity.


Industries

Incremental (multiple) authorizations were available to merchants in the travel and entertainment industry such as hotels and car rentals:

MCC

Industry

3351-3441

Car Rental Agencies

4411

Cruise Lines

3501-3999

Hotels/Motels/Resorts

7011

Hotels/Motels/Resorts - not elsewhere classified

7512

Automobile Rental Agency -not elsewhere classified

Effective October 14, 2016 MasterCard made incremental authorizations available to all merchant types.


Schemes

Brand

Incremental Authorization

VISA

Yes

MasterCardYes

Acquirer via GICC

Brand

Incremental Authorization

Elavon Europe

Yes

ConCardisYes


Authorization Validity

The 30 day chargeback protection timeframe is calculated from the date of the last approved authorization. Thus, an incremental authorization may be submitted to extend the chargeback protection period for the same transaction. 


Message Flow

A regular incremental authorization sequence consists of three parts:

  • The original pre-authorization itself
  • An incremental transaction with an amount update to add to the original pre-authorization amount
  • At a later time a capture transaction referring to the incremental transaction


Reversals

If an incremental authorization is being reversed, the amount being reversed is just that of the increment. A pre-authorization for the original amount will exist at the host (if it has not expired). Please note that to date it is not possible to reverse a pre-authorization and all its increments in one message. Each increment must be reversed individually starting with the latest incremental transaction before the original pre-authorization can be cancelled.


Card Authentication and Cardholder Verification

All pre-authorizations and incremental authorizations must occur online and if it is an EMV transaction it has to supply full EMV data for the transaction. The incremental transaction might be a ‘card-present’ or a ‘card-not-present’ transaction. Therefore it is possible or even likely that the initial preauthorization is an EMV transaction but not the increment. This is permitted as it can be assumed that card authentication and cardholder verification were perused in the initial pre-authorization.


Message Linking

For a given transaction, the original authorization request, the incremental authorization requests, and the reversal request are linked together by unique values referred to as tracing data. For Paygate merchants this link will be established towards the acquirer automatically through the PayID.


Process flow chart

Incremental authorization process flow


Paygate interface

Definitions

Data formats

Format

Description

a

alphabetical

as

alphabetical with special characters

n

numeric

an

alphanumeric

ans

alphanumeric with special characters

ns

numeric with special characters

bool

boolean expression (true or false)

3

fixed length with 3 digits/characters

..3

variable length with maximum 3 digits/characters

enum

enumeration of allowed values

dttm

ISODateTime (YYYY-MM-DDThh:mm:ss)


Abbreviations

Abbreviation

Description

Comment

CND

condition


M

mandatory

If a parameter is mandatory, then it must be present

O

optional

If a parameter is optional, then it can be present, but it is not required

C

conditional

If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional


Notice: Please note that the names of parameters can be returned in upper or lower case.


Call of interface for incremental authorisation

 To carry out an incremental authorisation via a Server-to-Server connection, please use the following URL:


Notice: For security reasons, Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the encrypted payment request parameters:

Parameter

Format

CND

Description

MerchantID

ans..20

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

PayID

ans32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch file

TransID

ans..64

M

Merchant’s transaction number, which should be unique for each payment

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent)

Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217

MAC

an64

O

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

Durationn2C

Indicates the additional number of days to be added to the stay or rental. Valid only for merchants operating in specific industries like Hotel/Car rental.

Parameters for incremental authorisation


The following table describes the Paygate response parameters:

Parameter

Format

CND

Description

MID

ans..20

M

MerchantID, assigned by Computop

PayID

ans32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch file

XID

ans32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

Merchant’s transaction number, which should be unique for each payment

Status

a..30

M

OK or FAILED

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

n8

M

Error code according to Paygate Response Codes (A4 Error codes)

MAC

an64

O

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

Response parameters for incremental authorisation