Open the Portico Developer Guide site
PosGateway Schema
CreditIncrementalAuth Element
PosGateway Schema > PosRequest Element > Ver1.0 Element > Transaction Element : CreditIncrementalAuth Element
Description

CreditIncrementalAuth adds to the authorized amount for a prior transaction.

The following rules apply:

  • The original transaction must have been an approved CreditAuth. NOTE: CreditSale is allowed for US merchants processing to the Exchange host only.
  • The original transaction id should continue to be used for subsequent transactions (i.e., voids, reversals, edits, etc.); the transaction id of the incremental authorization should never be referred to by subsequent transactions.
  • Each incremental authorization is not added to the batch. The total amount is maintained with the original transaction.
  • If the final settlement amount of the original transaction is less than the total of all authorizations, reversals will automatically be generated as needed.

Note:UnionPay cards routed directly to UnionPay International do not support Incremental Authorizations. CreditIncrementalAuth may continue to be used for UnionPay cards routing through either the Discover or JCB networks. (UnionPay direct routing available for Canada merchants on the GSAP authorization platform only).

Namespace http://Hps.Exchange.PosGateway
Type
PosCreditIncrementalAuthReqType Complex Type
Diagram
Block1 Element All CreditIncrementalAuth Element
Overview
CreditIncrementalAuth PosCreditIncrementalAuthReqType Complex Type

CreditIncrementalAuth adds to the authorized amount for a prior transaction.

The following rules apply:

  • The original transaction must have been an approved CreditAuth. NOTE: CreditSale is allowed for US merchants processing to the Exchange host only.
  • The original transaction id should continue to be used for subsequent transactions (i.e., voids, reversals, edits, etc.); the transaction id of the incremental authorization should never be referred to by subsequent transactions.
  • Each incremental authorization is not added to the batch. The total amount is maintained with the original transaction.
  • If the final settlement amount of the original transaction is less than the total of all authorizations, reversals will automatically be generated as needed.

Note:UnionPay cards routed directly to UnionPay International do not support Incremental Authorizations. CreditIncrementalAuth may continue to be used for UnionPay cards routing through either the Discover or JCB networks. (UnionPay direct routing available for Canada merchants on the GSAP authorization platform only).

All
Block1 CreditIncrementalAuthReqBlock1Type Complex Type

Contains a series of required and optional elements

All
GatewayTxnId optional txnIdType Simple Type

Gateway-generated transaction identifier returned in the response of the original transaction.

Amt amtTypeGlobal Simple Type

The amount requested for authorization

LodgingData optional ExtraChargesDataType Complex Type

Lodging extra charge indicators; common group of elements that provide additional details specific to lodging transactions that may be required in certain situations as determined by the brands

Note: The field name LodgingData can be confusing in this case as it is actually referring to the lodging extra charges data type.

All
Restaurant optional booleanType Simple Type

Restaurant charge

GiftShop optional booleanType Simple Type

Gift shop charge

MiniBar optional booleanType Simple Type

Mini-bar charge

Telephone optional booleanType Simple Type

Telephone charge

Other optional booleanType Simple Type

Other charge

Laundry optional booleanType Simple Type

Laundry charge

ExtraChargeDetailAmtInfo optional ExtraChargeDetailAmtInfoDataType Complex Type

Defines the individual amounts of extra charges included in the extra charge amount information and the total transaction amount.

ExtraChargesDetailAmountInfo can be used by Asia Pacific merchants only.

All
RestaurantCharges optional amtTypeGlobal Simple Type

Restaurant amount. For Feature Use

GiftShopCharges optional amtTypeGlobal Simple Type

Gift shop amount. For Feature Use

MinibarCharges optional amtTypeGlobal Simple Type

Mini-bar amount. For Feature Use

TelephoneCharges optional amtTypeGlobal Simple Type

Telephone amount. For Feature Use

OtherCharges optional amtTypeGlobal Simple Type

Other amounts. For Feature Use

LaundryCharges optional amtTypeGlobal Simple Type

Laundry amount. For Feature Use

AdditionalTxnFields optional AdditionalTxnFieldsType Complex Type

A common group of optional fields that are supported in several different transaction types for Merchant use.

All
Description optional descriptionType Simple Type

Free-form description field. This must not contain sensitive information.

InvoiceNbr optional Restriction of xs:string

Used to log the invoice number on transactions that are not eCommerce.

CustomerID optional customerIDType Simple Type

Used to log Merchant specific customer identification.

Note: For GETI check transactions, this is sent in the CUSTOM3 field.

CardOnFileData optional CardOnFileDataType Complex Type

Card On File Data

For Credit Incremental Auth transactions, this data is used for Exchange-hosted merchants only. For GSAP, GNAP, and AP hosted merchants, the card on file data is obtained from the original Credit Auth being incremented.

All
CardBrandTxnId optional restrictedStringType Simple Type

Network Transaction Identifier

CardOnFile optional CardOnFileType Simple Type

Card On File Indicator

Valid values include:

  • 'C' - Cardholder initiated transaction
  • 'M' - Merchant initiated transaction

CategoryInd optional CategoryIndType Simple Type

Mastercard CIT/MIT indicator subcategory

Valid values include:

  • 01 - Unscheduled Credential-on-file
  • 02 - Standing Order (variable amount and fixed frequency)
  • 03 - Subscription (fixed amount and frequency)
  • 06 - Related/Delayed Charge
  • 07 - No Show Charge
  • 08 - Resubmission

Note: Future use for GSAP-AP merchants

x_global_transaction_id optional x_global_transaction_idType Simple Type

Client generated transaction identifier sent in the request of the original transaction. This indicates the transaction to be updated.

Note: This is for internal use only.

CurrencyConversion optional CurrConversionDataType Complex Type

Data block for Currency Conversion.

Integration must be through GP-API

All
CurrConvOptOutFlag booleanType Simple Type

This setting indicates if the Customer has decided Opt Out of currency conversion and have the amount remain in the Merchants currency. If the customer does not opt out, the amount will be converted to currency associated with the card.

RateLookupTxnId optional guidType Simple Type

The Retrieval Reference Number (RRN) of the RateLookup or Incremental Authorization that provided the rate used for the calculations in this transaction, if it is different from the original Authorization.

CardHolderCurrCode optional currCodeType Simple Type

Indicates the currency associated with the cardholder card.

CardHolderAmt optional amtTypeGlobal Simple Type

The charge amount in the cardholder currency.

ExchangeRateApplied optional exchangeRateType Simple Type

The exchange rate used for currency conversion.

MarkupFee optional Restriction of xs:decimal

The mark up percentage applied to the transaction, resulting in the commission fee.

AccountReferenceReq optional accountReferenceReqType Simple Type

'Payment Account Reference' (PAR) is 29-character alphanumeric value requested by merchant. PAR is reference number associated with unique PAN and used by merchants to track transactions associated with customers PAN. Currently, PAR is only supported by Card Brand American Express.

Note: Account Reference is supported only for HOST Exchange.

Source
<xs:element name="CreditIncrementalAuth" type="PosCreditIncrementalAuthReqType" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:annotation>
    <xs:documentation>
      <p xmlns="http://Hps.Exchange.PosGateway">CreditIncrementalAuth adds to the authorized amount for a prior transaction.</p>
      <p xmlns="http://Hps.Exchange.PosGateway">
                            The following rules apply:
                            <ul><li>The original transaction must have been an approved CreditAuth. NOTE: CreditSale is allowed for US merchants processing to the Exchange host only.</li><li>The original transaction id should continue to be used for subsequent transactions (i.e., voids, reversals, edits, etc.); the transaction id of the incremental authorization should never be referred to by subsequent transactions.</li><li>Each incremental authorization is not added to the batch. The total amount is maintained with the original transaction.</li><li>If the final settlement amount of the original transaction is less than the total of all authorizations, reversals will automatically be generated as needed.</li></ul></p>
      <p xmlns="http://Hps.Exchange.PosGateway">
        <strong>Note:</strong>UnionPay cards routed directly to UnionPay International do not support Incremental Authorizations. CreditIncrementalAuth may continue to be used for UnionPay cards routing through either the Discover or JCB networks. (UnionPay direct routing available for Canada merchants on the GSAP authorization platform only).
                          </p>
    </xs:documentation>
  </xs:annotation>
</xs:element>
See Also
Transaction ElementVer1.0 ElementPosRequest ElementPosGateway Schema