Skip to end of banner
Go to start of banner

Auth Matching Event

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Authorization Matching events provide all the data necessary to evaluate the effectiveness of potential posting matching logic.  When a posted transaction is automatically matched to a disputed authorization by the system, an event is created.  When a posting is identified by a user, an event is created.  When a posting is referred to a user by the system, and the user does not identify it as a match for the disputed authorization, an event is created.

Data Category

Event Field/Column Name

Data Type

Description

Applicability

Sample Value

Notes

Key

TenantId

VARCHAR(32)

Unique ID associated with each Quavo client.

ALWAYS

qvo-stg

Key

ClientId

VARCHAR(64)

A unique ID representing a single client.

ALWAYS

Default

Key

ClaimId

VARCHAR(32)

Unique ID associated with a claim.  Format: YYMMDD<Ordinal Number>"C"

Example: 2405230003C

ALWAYS

2306060014C

Key

DisputeId

VARCHAR(32)

Unique ID associated with a disputed transaction.  Format: YYMMDD#####"D"

ALWAYS

2306050001D

Posting Details

PostingMatchList[].TransactionDate/TRANSACTIONDATE

DATE

The date of the transaction, as provided by the system of record.  This generally represents the Posting Date.

CONDITIONAL

2023-10-07

Posting Details

PostingMatchList[].AuthorizationCode/AUTHCODE

VARCHAR(10)

A credit card authorization or approval code is an alphanumeric string generated at the POS. Normally consisting of five to six characters, this one-time approval code is unique to each transaction.

CONDITIONAL

031832

Posting Details

PostingMatchList[].TransactionId/TRANSACTIONID

VARCHAR(256)

A unique ID associated with a transaction.  This value is provided by the transaction system of record.

ALWAYS

5315158617D1116187908

Posting Details

PostingMatchList[].PostingDate/POSTINGDATE

DATE

The date the transaction posted to the customer/member account.

CONDITIONAL

2023-0909

Posting Details

PostingMatchList[].Description/DESCRIPTION

VARCHAR(256)

A description of the transaction as provided by the system of record.  Typically, this will match what the customer/member sees on their account statement.

CONDITIONAL

STARLINK INTERNET

Posting Details

PostingMatchList[].MerchantName/MERCHANTNAME

VARCHAR(256)

Name of the business providing goods or services, as provided by the system of record.

CONDITIONAL

STARLINK INTERNET

Posting Details

PostingMatchList[].Amount/AMOUNT

NUMBER(9,2)

The amount of the posted transaction.

ALWAYS

133.13

Posting Details

AuthMatchingOutcome/OUTCOME

VARCHAR(16)

For merchant credit checking, this represents the result of the check or user review.

ALWAYS

"Auto", "Manual", "No Match"

Posting Details

PostingMatchList[].Iteration/ITERATION

NUMBER(2,0)

For matching algorithms, such as merchant credit or authorization posting, this number represents the the highest probability rule that resulted in a match.

ALWAYS

1

Posting Details

PostingMatchList[].MatchResult/MATCHRESULT

VARCHAR(16)

For matching algorithms, such as merchant credit or authorization posting, this represents whether a match was applied automatically or referred to a user.

ALWAYS

"Auto Match", "Review"

Posting Details

PostingMatchList[].PostedDisputeId/POSTEDDISPUTEID

VARCHAR(32)

Unique ID associated with the posting record of a disputed authorization.  Format: YYMMDD#####"D"

CONDITIONAL

2310110380D

Metadata

EventDateTime

TIMESTAMP_NTZ(9)

The datetime that the event was recorded.

ALWAYS

2023-09-09 21:00:00

Metadata

EventIdentifier

VARCHAR(64)

A unique ID associated with each business event.

ALWAYS

70b1c86d-d06f-4c93-bab2-0e938a4ef768

Metadata

EventItemId

VARCHAR(64)

An ID included with each business event that identifies the tenant and Claim ID or Dispute ID associated with the event.

ALWAYS

qvo-stg|2302030002D

  • No labels