---
title: Payment Optimization Post-Auth Fields
slug: public-apis/payment-optimization-post-auth-fields
createdAt: 2026-06-22T17:06:19.470Z
---

::::ExpandableHeading
###

**Topic type: Reference**

:::hint{type="warning"}
**Purpose**: Define fields required in post-authorization updates for Payment Optimization.&#x20;

**Audience**: API integrators sending post-authorization data.

**Applies to**: Universal Fraud API authorization update requests.

**Does not apply to**: Pre-authentication requests or response values.&#x20;
:::
::::

Post-authorization feedback allows Payment Optimization to evaluate authentication outcomes and improve future recommendations.

The Universal Fraud APIs submit this information through the **Authorization Update** workflow.

## Authorization Update Context

Authorization Update requests are sent after an authorization attempt occurs and provide feedback about:

- Authorization outcomes
- Authentication outcomes
- 3-D Secure execution
- Strong Customer Authentication (SCA) results
- Issuer behavior

This information supports ongoing optimization and performance measurement.

## paymentMethods\[]

The following fields may be supplied within the paymentMethods\[] array of an Authorization Update request.

:::ExpandableHeading{isOpen="true"}
### paymentMethodID

Identifies the payment method being updated.
:::

***

:::ExpandableHeading
### avsResult

Address Verification Service result returned by the issuer.

Values:

- matched
- partialMatch
- notMatched
- notChecked
- systemError
- other
:::

***

:::ExpandableHeading
### cvvResult

Card Verification Value result returned by the issuer.

Values:

- matched
- notMatched
:::

***

:::ExpandableHeading
### cardAuthorizationCode

Authorization approval code returned by the card network or issuer.
:::

***

:::ExpandableHeading
### cardAuthorizationDateTime

Date and time the authorization result was received in ISO 8601 date-time.
:::

***

:::ExpandableHeading
### postAuthorizationRejectReason

Reason the authorization was rejected.

Values:

- creditReject
- fraudReject
- otherReject
:::

***

:::ExpandableHeading
### totalFailedAttempts

Total failed authorization attempts for the payment method.
:::

***

## 3-D Secure Fields

The following fields are used when 3-D Secure information is available.

:::ExpandableHeading
### sca3DSFlow

Authentication flow used during 3-D Secure processing.

Values:

- challenge
- frictionless
- dataOnly
:::

***

:::ExpandableHeading
### sca3DSVersion

3-D Secure protocol version.
:::

***

:::ExpandableHeading
### eciIndicator

Electronic Commerce Indicator returned by the authentication process.
:::

***

:::ExpandableHeading
### isSCASoftDecline

Indicates whether the authorization resulted in an SCA soft decline.
:::

***

:::ExpandableHeading
### sca3DSChallengeRequestType

Values:

- 02
- 03
- 04
- 05
- 06
- 10
- 11
:::

***

:::ExpandableHeading
### sca3DSTransactionStatus

Values:

- Y
- N
- U
- A
- I
:::

***

:::ExpandableHeading
### scaAuthorizationStatus

Values:

- approve
- decline
:::

***

:::ExpandableHeading
### scaAuthorizationError

Reason the SCA authorization was declined.

Values:

- decline
- fraudReject
- insufficientFunds
- invalidCard
- incorrectInformation
- lostOrStolen
- withdrawalAmountExceeded
- technicalError
- other
:::

