Skip to end of banner
Go to start of banner

Authorizations

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 32 Next »

The system supports the ability to include pending authorizations in a claim.  When pending transactions are included in a claim, the system will call the posted transaction service every 6 hours to retrieve new postings.

  A decision table is used to evaluate each posted transaction against a set of criteria to determine if it is one of the following.
  • Exact Match - The system will automatically associate the posted transaction and add it to the claim.
  • Possible Match - An assignment will be generated for a user to review all possible matches and select the match if present.
  • No Match - The system will continue to check each day for new postings and no additional action is taken.

An SLA deadline is set to 5 business days by default and, when expired, the system no longer checks for posted transactions.  

When a posting is found, the original dispute is set to a "Resolved-PostedDisputeCreated" status, and a new dispute ID is created for the posted transaction.

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 Letter (When Rule: ShouldSendNotPostedDeniedLetter)

When a posted transaction is matched to an authorization, Should the system send the Authorization Posting Confirmation Letter?  (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 Letter

Confirmation Letter

Never Posted Deny Letter

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
  • No labels