Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.

Final Authorization Indicators

The purpose of this feature is to ensure that unused funds are reversed, so that a customer's funds are available again when an order is not fulfilled.

For an authorization with an amount greater than zero, indicate whether the authorization is a final authorization, a pre-authorization, or an undefined authorization.

You can set a default authorization type in your account. To set the default authorization type in your account, contact customer support.

Supported Processors

  • Chase Paymentech Solutions: Mastercard and Maestro (International) only. Does not support this feature for Maestro (UK Domestic).
  • Elavon Americas: Mastercard only.
  • FDC Nashville Global
  • Streamline
  • Worldpay VAP: Worldpay VAP sets the indicator. You do not need to send a final authorization indicator when using the API.

Supported Services

These services are supported:

  • Authorization: supported for all processors
  • Incremental authorization: supported for Chase Paymentech Solutions, Elavon Americas, FDC Nashville Global, Visa Platform Connect, Worldpay VAP processors

Supported Card Types

These card types are supported:

  • Maestro (International)
  • Maestro (UK Domestic)
  • Mastercard

Requirements for Final Authorizations

For a final authorization:

  • The authorization amount is greater than zero.
  • The authorization amount is the final amount that the customer agrees to pay.
  • The authorization should not be cancelled after it is approved except when a system failure occurs.
  • The authorization must be submitted for capture within seven calendar days of its request.
  • The capture amount and currency must be the same as the authorization amount and currency.
  • Chargeback protection is in effect for seven days after the authorization.

Pre-Authorizations

Supported Processors:

  • Chase Paymentech Solutions
  • Elavon Americas
  • FDC Nashville Global
  • Streamline
  • Worldpay VAP

A pre-authorization enables you to authorize a payment when the final amount is unknown. The system places the funds on hold until you request a follow-up transaction. Pre-authorizations are typically used for lodging, auto rental, e-commerce, and restaurant transactions.

When you have a specific merchant category code (MCC) assigned to your account, you are allowed to capture up to 20% more than the cumulatively authorized amount on Visa, Diners Club, Discover, and JCB cards. Contact your account manager to have your account enabled for this option.

Requirements for Pre-Authorizations

For a pre-authorization:

  • The authorization amount is greater than zero.
  • Submit the authorization for capture within 30 calendar days of its request.
  • When you do not capture the authorization, reverse it. In the US, Canada, Latin America, and Asia Pacific, Mastercard charges an additional fee for a pre-authorization that is not captured and not reversed. In Europe, Russia, Middle East, and Africa, Mastercard charges fees for all pre-authorizations.
  • Chargeback protection is in effect for 30 days after the authorization.

Undefined Authorizations

Supported Processors:

  • Chase Paymentech Solutions
  • Elavon Americas
  • FDC Nashville Global

An authorization is undefined when you set the default authorization type in your account to undefined and do not include the authIndicator field in the authorization request. To set the default authorization type in your account, contact customer support.

Undefined authorizations are supported only in the US, Canada, Latin America, and Asia Pacific. They are not supported in Europe, Russia, Middle East, and Africa.

Requirements for Undefined Authorizations

For an undefined authorization:

  • The authorization amount must be greater than zero.
  • The authorization amount can be different from the final transaction amount.
  • The authorization should not be cancelled after it is approved except when a system failure occurs.
  • The authorization must be submitted for capture within seven calendar days of its request.
  • When you do not capture the authorization, you must reverse it; otherwise, Mastercard charges an additional fee for the transaction.

Unmarked Authorizations

Supported Processors:

  • Chase Paymentech Solutions
  • Elavon Americas
  • FDC Nashville Global
  • Streamline

An authorization is unmarked when the default authorization type is not set in your account and you do not include the processingInformation.authorizationOptions.authIndicator field in the authorization request. To set the default authorization type in your account, contact customer support.

Unmarked authorizations are supported only in the US, Canada, Latin America, and Asia Pacific. They are not supported in Europe, Russia, Middle East, and Africa.

does not set a mark or indicator for the type of authorization in the request that is sent to the processor.

Chase Paymentech Solutions: Supported for Mastercard and Maestro (International) only. Chase Paymentech Solutions does not support this feature for Maestro (UK Domestic).

Elavon Americas: Supported for Mastercard only.

Requirements for Unmarked Authorizations

For an unmarked authorization:

  • The authorization amount must be greater than zero.
  • The authorization amount can be different from the final transaction amount.

Endpoints

POST /pts/v2/payments

POST /pts/v2/payments

POST /pts/v2/payments

Example

{  "orderInformation": {    "billTo": {      "firstName": "RTS",      "lastName": "VDP",      "address1": "201 S. Division St.",      "postalCode": "48104-2201",      "locality": "Ann Arbor",      "administrativeArea": "MI",      "country": "US",      "email": "[email protected]"    },    "amountDetails": {      "totalAmount": "100.00",      "currency": "usd"    }  },  "paymentInformation": {    "card": {      "expirationYear": "2030",      "number": "CARD_NUMBER",      "expirationMonth": "12",      "type": "001"    }  },  "processingInformation": {    "authorizationOptions": {      "authIndicator": "1"    }  }}
{    "_links": {        "authReversal": {            "method": "POST",            "href": "/pts/v2/payments/6910040807416719003955/reversals"        },        "self": {            "method": "GET",            "href": "/pts/v2/payments/6910040807416719003955"        },        "capture": {            "method": "POST",            "href": "/pts/v2/payments/6910040807416719003955/captures"        }    },    "clientReferenceInformation": {        "code": "1691004080800"    },    "id": "6910040807416719003955",    "orderInformation": {        "amountDetails": {            "authorizedAmount": "100.00",            "currency": "usd"        }    },    "paymentAccountInformation": {        "card": {            "type": "001"        }    },    "paymentInformation": {        "card": {            "type": "001"        }    },    "pointOfSaleInformation": {        "terminalId": "111111"    },    "processorInformation": {        "approvalCode": "888888",        "networkTransactionId": "123456789619999",        "transactionId": "123456789619999",        "responseCode": "100",        "avs": {            "code": "X",            "codeRaw": "I1"        }    },    "reconciliationId": "67628631TKRG2OVE",    "status": "AUTHORIZED",    "submitTimeUtc": "2026-08-02T19:21:20Z"}

Required Fields

These fields are required for a final authorization request:

FieldDescription
orderInformation.amountDetails.currency—
orderInformation.amountDetails.totalAmount—
orderInformation.billTo.address1—
orderInformation.billTo.administrativeArea—
orderInformation.billTo.country—
orderInformation.billTo.email—
orderInformation.billTo.firstName—
orderInformation.billTo.lastName—
orderInformation.billTo.locality—
orderInformation.billTo.postalCode—
paymentInformation.card.type—
paymentInformation.card.expirationMonth—
paymentInformation.card.expirationYear—
paymentInformation.card.number—
processingInformation.authorizationOptions.authIndicator
Set the value to 0 for pre-authorizations, or to 1 for final authorizations. Do not include this field for unmarked or undefined authorizations.

Last published: October 28, 2026

Not available for your audience

This page isn't available for your current audience selection.