Authorizations
- Devan Robertson
- Kristafanie Somers
- Jacob Harris
Overview
A decision table is used to evaluate each posted transaction against a set of criteria to determine if it is one of the following. To see which claim reasons support pending transactions, see Dispute Transactions.
Duplicate Detection
If a posted transaction already exists as a dispute on another claim, it will not be considered for auto-match, nor will it be available to the user to select during a review.
Extension Points
When the WaitForPosting SLA expires, should a user review all transactions that have posted since the pending transaction was added to the claim? (Config: ShouldReviewPostedAfterWindowExpires)
How should the system determine what is a potential match and what is an automatic match? (Decision Table: TempMatchingCriteria)
How long should the system wait for the posting before denying the dispute? (SLA Deadline: WaitForPosting)
How often should the system check the system of record for new postings? (SLA Goal: WaitForPosting)
When it is determined that the authorization did not post, should the system send the Never Posted Deny? (When Rule: ShouldSendNotPostedDeniedLetter)
When a posted transaction is matched to an authorization, Should the system send the Authorization Posting Confirmation? (When Rule: ShouldSendAuthorizationPostedLetter)
To customize how the start and end date parameters are set for searching for posted transactions, update DefaultCheckForPostingSearchDateRangeExt.
Related Correspondence
Authorization Posting Confirmation
Integration Requirements
A service capable of providing a list of pending authorizations that includes the data fields identified below. This may be the same service that provides posted transactions or it could be a stand-alone service.
Data Requirements
Required
Description
Transaction Date
Amount
Preferred
Authorization Code
Release Date
Acquirer Reference Number