Description: The daily authorization extract file provides you with all authorizations attempted regardless of their disposition (e.g., approved, declined, etc.). The data elements provided reflect information specific to how a transaction was authorized in order to confirm that the individual initiating the purchase was the authorized cardholder.
For more information on Enterprise Extracts, refer to the Enterprise Extracts Guide.
How to Use the Extract
Merchants who receive this data can use the information for monitoring their authorization performance in order to optimize their processes for increased card acceptance/sales, reduce auth related fees, or to identify authorization submittal issues that need to be addressed based on unfavorable Issuer authorization responses.
Types of analysis include but are not limited to:
-
Declined Auth Ratios
- Analyze authorization data to help reduce the number/percentage of declined transactions based on response codes returned in conjunction with auth request data being submitted (or not submitted).
-
Authorization Retries
- Assess timing for when authorizations are performed (including recurring transactions) to determine optimal windows for submission for increased approval rates (optimal weekdays/times of day).
-
Issuer Acceptance
- Identify Issuing bank patterns for acceptance/declines based on auth request submittal timeframes, transaction size, currency, and data provided (or not provided).
-
Dispute Processing
- Access authorization data to help defend against cardholder disputes (not authorized scenarios) or to help prevent future disputes based on identification/resolution of authorization related issues.
File Name
-
EnterpriseCustomer_YYYYMMDD_Enterprise_Authorization_Extract.csv
- EnterpriseCustomer is the given customer’s name
- YYYYMMDD is the given date for the file generated; it is based on the previous day’s date and will represent the data that was provided by the various card acquirer systems within Shift4
Location
- Shift4 SFTP / Customer-Specific Folder / Prod
File Format
- Comma Separated Values (CSV)
Frequency
- Daily, based on the reception of data from the various card acquirer systems within Shift4. We are currently expecting all data to be available by 4:00 a.m. ET and the extracts should be available within the SFTP sites by 11:00 a.m. EST.
Content
# | Data Element | Data Type | Description |
1 | FileName | nvarchar(26) | The given file name - ‘Authorization Extract File’ |
2 | MerchantNumber | nvarchar(15) | This identifies your merchant number |
3 | AuthorizedAmount | numeric | The dollar amount for the type of activity |
4 | SettlementDate | date | The date that transaction settled |
5 | AccessMethod | nvarchar(2) | The code that identifies what kind of access was used for the authorization |
6 | AccountNumber | nvarchar(22) | The account number for the card used |
7 | AccountFundingSource | nvarchar(1) | Identifies whether transaction is debit or card |
8 | AcquirerBIN | nvarchar(6) | The financial institution acting as the Acquirer of this customer transaction. |
9 | AuthorizationResponse | nvarchar(2) | The authorization response code from the authorizer |
10 | CVV2Response | nvarchar(1) | The response to CVV authorization |
11 | AVSResponse | nvarchar(1) | The response to AVS authorization |
12 | AuthenticationMethod | nvarchar(25) | Response message data |
13 | ApprovalCode | nvarchar(6) | Approval code from the authorizer |
14 | AttemptCount | number | How many times authorization for a given transaction was attempted |
15 | BillingDescriptor | nvarchar(1) | Identifies the billing descriptor |
16 | CardAcceptorCity | nvarchar(18) | Identifies the city where the cardholder’s transaction occurs |
17 | CardType | nvarchar(1) | Identifies the card plan type |
18 | CountryCode | nvarchar(3) | International standard 3-digit country code. |
19 | IssuingBank | nvarchar(100) | Identifies the issuing bank of card used |
20 | DigitalWallet | nvarchar(1) | Indicates whether a digital wallet was used |
21 | POSEntryMode | nvarchar(4) | The method used to capture the account number and expiration from the card |
22 | Receipt | ||
23 | TerminalNumber | nvarchar(4) | Identifies the terminal number |
24 | TransactionCurrencyCode | nvarchar(3) | 3-digit currency code |
25 | TransactionDateAndTime | date |
the date and time stamp of a transaction Format: YYYY-MM-DD HH:MM:SS |
26 | TransactionID | nvarchar(15) | Unique identifier to each transaction |
27 | TransactionSourceFlag | nvarchar(3) | The Telecom provider for authorization |
28 | Provider | nvarchar(4) | Identifies the payment provider |
29 | FileDate | date | Date when the file was created |
30 | Category |
nvarchar(10) |
Category of transaction |
31 | DeclinedDepositCount | number | Count of declined transactions for a given card number within a given day |
32 |
SuccessfulDepositCount | number | The total net deposit amount for successful transactions for a given card number within a given day |
33 | SuccessfulNetDepositAmount | number | The total net deposit amount for successful transactions for a given card number within a given day |
34 | ReturnACI |
nvarchar(1) |
Identifies the response to the ACI Request. Refer to Authorization Characteristics Indicators for possible values. |
35 | ISOSourceStationID |
nvarchar(6) |
The originator of the ISO request message |
36 |
ProductTypeIdentification |
nvarchar(2) |
Refer to Card Product Codes for a list of values. |
37 |
CAVVResultCode |
nvarchar(1) |
Displays the CAVV Result Code See Shift4 CAVV Result Code reference table for values |
38 |
MerchantAdviceCode |
nvarchar(4) |
Displays the Merchant Advice Code which is specific to MasterCard See Shift4 Merchant Advice Code reference table for values |
39 | VendorReference |
nvarchar(256) |
Reference received from the Gateway |
40 | CorrelationID |
nvarchar(12) |
Universal transaction identifier allowing linking among Transaction, Authorization, and Dispute data |
Please proceed to the next article on this topic: Batch Extract File Details.
Comments
0 comments
Please sign in to leave a comment.