Description: Learn how Lighthouse Business Manager (LBM) Extracts streamlines enterprise data retrieval by consolidating gateway and settlement information into a single, automated file.
Overview
Lighthouse Business Manager (LBM) Extracts provide Enterprise customers with an automated method to retrieve consolidated gateway and settlement data. This system enhances reconciliation workflows by delivering a unified view of the entire transaction lifecycle within a single file.
Extract Specifications and Procedures
File Naming Convention
LBM Extract files follow a standard naming format for clarity and consistency.
Format: LBMCustomer_YYYYMMDD_Enterprise_Custom_Transaction_Extract.csv
How to Initiate an Extract Request
To set up a new LBM Extract, contact your designated Account Manager, who will guide you through the standardized onboarding process.
Customizing Data Fields
If your organization requires additional data fields beyond the standard extract, notify your Account Manager to request a custom field assessment.
Strategic Update
A self-service module for LBM Extract management is currently in development. This enhancement will enable users to configure and control data retrieval settings independently.
Data Availability
Refer to the delivery schedule for details on when LBM Extract data becomes available.
Extract Information Table
LBM Extract Field Name | Description | Example | Datatype | Additional Notes |
| Merchant ID | The unique identifier assigned by the payment processor (e.g., TSYS) to the merchant's processing account. | 002xx0000 | STRING | |
| Shift4 Mid | The internal Shift4 unique identifier for the merchant account | 8xxxx00 | BIG INT | |
| Merchant Name | The "Doing Business As" (DBA) name of the merchant location | Toronto Book Store | STRING | |
| Transaction Datetime | The timestamp indicating when the transaction was initiated at the POS. | 2025-08-04 17:59:16 | Date and Timestamp | |
| Settled Date | The date the transaction was finalized and moved into the Processor's general Ledger for reconciliation. | 2025-08-05 | Date (YYYY-MM-DD) | |
| Transaction ID | The primary system-generated key used to uniquely identify this specific transaction record. | 0V0000xxBKZx | STRING | Not shown in LBM, used primarily internally to link transaction events together. |
| Merchant Reference | A custom reference value provided by the merchant to link the transaction to their internal records. Generated and managed by the merchant. | 1239750076 | STRING | |
| Transaction Amount | The total gross value of the transaction (Sale or Refund) in the specified currency. | 9.63 | numeric(10,2) | |
| Card Brand | The specific card network associated with the payment (e.g., Visa, Mastercard) | Visa | STRING | Visa/Amex/ Mastercard etc. |
| Card Type | The classification of the payment instrument (e.g., Credit Card, Debit Card, Gift Card). | Credit Card | STRING | |
| Last 4 of Card | The last 4 digits of credit card. | xxxx | STRING(4) | |
| Company Name | The name of the parent organization or vendor responsible for the interface software. | PAX | STRING | |
| Interface Name | The specific name of the software application, POS system, or middleware platform that captured the transaction and transmitted it to the gateway | BROADPOS | STRING | |
| Interface Version | The version of the software or system used to initiate the transaction. | 1.1 | ||
| Currency Code | The currency of the payment amount. | USD | STRING (3 char alpha) | |
| Processor ID | The processor code - TSYS. | TSYS | STRING | |
| Amex Direct Flag | A boolean indicator that specifies if an American Express transaction was processed directly with Amex (OptBlue) or through a third-party acquirer. This flag helps determine the settlement path and fee structure used for the transaction. | N | boolean | Y or N |
| Deposit ID | A unique reconciliation identifier assigned to a batch when they are settled and funded. This ID is used to match the total transaction volume in LBM to the actual deposit appearing on the merchant's bank statement. | 36480077745 | STRING | |
| Batch Number | A unique identifier generated by Shift4 to group all transactions processed within a specific terminal's work period. It serves as the primary reference for auditing a set of transactions before they are sent for settlement. The format follows a strict convention: [Merchant ID]_[YYYYMMDD]_[4_Digit_Running Number]. | 0022554772-20250904-1130 | STRING | |
| Processor Batch ID | A unique identifier generated by the processor to group all transactions processed. | 276967666 | STRING | |
| Decision | The final processing status indicating whether the transaction was 'Accepted' or 'Rejected' by the host. | Accepted/ Rejected | STRING | |
| Transaction Type | The classification of the financial movement, limited to 'SALE' or 'REFUND' in this extract. | SALE | STRING | SALE or REFUND |
| Customer Reference | A custom reference value provided by the merchant to link the customer to their internal records. Generated and managed by the merchant. | 2998248121 | STRING | |
| Invoice | An identifier assigned to a transaction, used for tracking and reference purposes. | 70052731 | STRING | In LBM the field is called "transaction ID" |
| Auth Code | A unique code provided by the bank or card issuer confirming that the transaction has been authorized. | 09363G | STRING | |
| Entry Mode | The method used to input the payment information, such as swiping or chip. | EMV Chip | STRING | |
| AVSResponseCode | Indicates whether the billing address matches the address on file with the bank. | X - Street address and 9-digit ZIP/postal code matched | STRING | |
| CVV2ResponseCode | Shows if the security code on the card was verified successfully. | M - CSC matched | STRING | |
| Auth Amount | The initial dollar amount requested and approved by the issuing bank. | 8.95 | numeric(10,2) | |
| Payout Date | Indicated the date of the payout. Depending on bank holidays or weekends, this date might be different than the actual date the payout in reflected in the merchant's bank account. | 2025-08-08 | Date (YYYY-MM-DD) | |
| Auth Approved Date | The date Authorization was approved. | 2025-08-07 | Date (YYYY-MM-DD) | |
| DebitCreditIndicator | Signifies the financial impact of the transaction: Debit (increasing the merchant's balance/Sale) or a Credit (decreasing the merchant's balance/Refund or Adjustment). | Debit | STRING | Debit or Credit |
| Customer Name | Name of the customer as received by the gateway. | MALxxxx/MITxxx | STRING | |
| Customer Email | Email of the customer as received by the gateway. | MALxxxx@yahoo.com | STRING | |
| Card Token | A non-sensitive surrogate value used to represent the card data for secure future processing. | 8677792559978476 | STRING | |
| Issuer BIN | The Bank Identification Number identifying the specific institution that issued the card. | 424631 | STRING | |
| Global Merchant ID | The unique merchant identifier assigned specifically by Global Payments. | 7792559978476 | STRING | In LBM the field is called "Processor MID" |
| Terminal ID | The unique identifier for the specific physical or virtual POS terminal used for the transaction. | SYTZ00NS1 | STRING | |
| Processed ARN | A unique identifier assigned to a settled transaction by the processor. It is used to track a specific transaction, especially in the event of a refund, dispute, or chargeback. | 85369436091515801330035 | STRING | |
| Surcharge Amount | The additional amount charged by the merchant to a customer for the privilege of using a credit card for payment. | 0.23 | numeric(10,2) | |
| Serial Number | Shift4 identifier | 8536943 | STRING |
Comments
0 comments
Please sign in to leave a comment.