Logical 02336 - Retail Transaction - Tender - Authorization View

Top  Previous  Next

Subject Area Concepts

Each type of tender requires a different level of authorization before the retailer accepts it to settle a customer purchase.  In part, the authorization level is a function of the fraud or default risk associated with each tender type. Also, floor and ceiling limits may be placed on different types tender.  For example stores often impose minimum purchase amounts on credit card charges.

The adjudication of a request for tender authorization may be performed remotely by the corporate office (for proprietary charge cards), by a third party financial institution (for bank cards) or locally within the store (for personal checks or store-based customer accounts). To support local authorization, this view includes TenderApprovalReference. This entity provides the background information required to approve the acceptance of personal checks by the store.

Logical 02336 - Retail Transaction Tender Authorization View shows the extra authorization data that can be recorded in the ARTS Operational Data Model, when a RetailTransaction is paid for using a debit or credit card (or any other form of tender that requires authorization).

TenderAuthorization records the authorization data that financial institutions require the enterprise to keep, after an authorization request was made of a TenderAuthorizationProvider. TenderAuthorizationReversal records authorization reversals that may have to be performed if the tender authorization process is being conducted using the ISO-8583 tender authorization protocols.

TenderAccountApprovalReference is both the 'blacklist' of blocked tender instruments (Credit and Debit card numbers, Check Account numbers, Gift Certificate Serial Numbers, etc.) that cannot be used to tender a transaction as well as the 'white list' of specifically approved tender instruments that can be used to tender a transaction.

The ARTS data model has a placeholder for customer account numbers.  These actual values should never be stored as readable text.  The information must be obfuscated or encrypted before it is posted to a table so it cannot be read or used by unauthorized parties.

New in ODM V7.3

A new  join entity, TenderLineItemAuthorization removes the dependency of TenderAuthorization on TenderLineItem which limited the way TenderAuthorization could be referenced to RetailTransactions.  This became a problem when stored value instruments required authorization as part of being  activted in in a TenderControlTransaction.  This change fixes the problem and adds some flexibility in how TenderAuthorization might be used in the future.