Can matching and payment data leave the Console?
The Payment Partner and Matcher Engine views export to CSV for sharing, archiving or analysis outside the Console, and an audit file covering matching actions can be generated on demand. Exports built from a merchant view carry the column names, field order, file format and filename pattern defined in that view.
In detail
Yes. Data can leave the Console in several ways, each keeping the structure your merchants defined.
Exports from matching views
The Payment Partner and Matcher Engine views export to CSV, for sharing, archiving or analysis outside the Console. An audit file covering matching actions can also be generated on demand, for auditors or internal control.
Exports from merchant views
Exports built from a merchant view carry the column names, field order, file format and filename pattern defined in that view. A finance team that renamed its columns to its own nomenclature receives files in that same language, ready to load into its accounting tools.
Other ways data reaches your systems
- Webhooks deliver transaction, checkout and batch events to the endpoints your merchants configure.
- API payloads carry order and transaction data, including network token fields when they apply.
Exports follow permissions. A user exports only what their scope allows, so a merchant's file contains its own data, while your team can work across the structure it oversees.
Keeping exports tied to views avoids a common problem: spreadsheets that drift away from what the Console shows. What a team reads on screen is what it receives in the file.