Description: Understand why Shift4 is moving away from Enterprise Extracts, how Customer Hub-based Extracts differ, and how to get started with the new solution.
Overview
Shift4 is moving away from Enterprise Extracts and replacing them with Customer Hub-based Extracts, a more comprehensive, scalable, and globally-inclusive data solution. This change reflects our commitment to providing enterprise clients with complete payment data visibility across all processing channels, not just a subset.
Why We Are Moving Away from Enterprise Extracts
Enterprise Extracts were built around a specific architecture: they sourced data directly from individual TSYS acquirer files. While this worked well for US-based merchants processing through TSYS, it created a fundamental limitation where the data reflected only one part of the Shift4 processing ecosystem.
As Shift4 has grown into a global payment platform, this approach has become increasingly insufficient:
- US-only scope: Enterprise Extracts only covered merchants processing in the United States.
- Partial data: Because data was pulled from TSYS files alone, transactions processed through other acquirers — Global Payments, Finaro, and others — were simply not included.
- Reconciliation gaps: Merchants with multi-acquirer or multi-region operations had no single source of truth, forcing manual reconciliation across disconnected data sources.
- Limited scalability: The file-based, TSYS-specific architecture could not evolve to meet the demands of an expanding global platform.
Enterprise Extracts vs. Customer Hub-based Extracts
The table below highlights the key differences between the two solutions:
Enterprise Extracts | Customer Hub Based Extracts | |
| Data Source | TSYS acquirer files | Customer Hub |
| Geographic Coverage | United States only | Global (all regions) |
| Acquirer Coverage | TSYS (Gateway 1.0) only | TSYS (Gateway 1.0), Gateway 2.0, and Gateway 3.0 |
| Data Completeness | Partial: acquirer-specific | Complete: all Gateway data |
| Delivery Method | SFTP (file-based) | SFTP (file-based, with self-service in customer hub coming soon) |
| Files | Multiple files, based on merchants selection | One consolidated file |
| Self-Service Access | Not available | Planned for the second half of 2026 |
What Customer Hub-based Extracts Offer
- Global coverage: Includes transactions processed through TSYS, Global Payments, Finaro, and all other acquirers connected through the Shift4 Gateway.
- Single source of truth: All extract data originates from the same system your transactions flow through, eliminating cross-system reconciliation gaps.
- Consistent format: A unified extract schema regardless of the underlying acquirer or geography.
- Customizable: Additional data fields can be requested to tailor extracts to your reporting needs.
Coming Soon: Self-Service From the Customer Hub
On the Roadmap
We are actively building self-service extract management directly within the Customer Hub. This upcoming capability will allow enterprise users to configure, schedule, and manage their own custom extracts without requiring a support request to Shift4, putting data access directly in your hands.
Watch for release announcements in the Customer Hub product notes and this knowledge base.
What This Means for You
If you are currently using Enterprise Extracts, we will continue to support it for the foreseeable future. If you'd like to explore the option to move to Customer Hub-based extracts, please contact your Enterprise account manager.
For merchants new to Shift4's extract capabilities, Customer Hub-based Extracts are the standard going forward. To get started:
- Contact your Shift4 account manager to request the Customer Hub-based Extract setup.
- Provide the required configuration details (SFTP IP, authentication method).
- Refer to the Customer Hub-based Extracts knowledge base articles for file format specifications and field definitions.
Comments
0 comments
Please sign in to leave a comment.