Skip to main content
Banking OS financial data aggregation connectors integrate with transaction enrichment vendors so you can give customers clearer insight into their spending. Channels such as the Backbase Engagement Banking Platform interact with these providers through standardized unified APIs and Sync Hub events. This domain covers transaction data enrichment. Enrichment turns raw transaction narratives into categories, merchants, locations, and counterparties. Enrichment uses vendor connectors behind a unified API contract. Banking OS delivers the results asynchronously through Sync Hub, not in the HTTP response body.

Core functionalities

Transaction categorization

Classify transactions using each vendor’s native category taxonomy. Banking OS preserves vendor-native categories and does not map them to a single cross-vendor taxonomy.

Merchant and counterparty resolution

Resolve merchant names, contact details, logos, and counterparties where the vendor supports them.

Location enrichment

Attach geographic context (city, region, country, and coordinates) when the vendor provides location signals from transaction data.

Event-driven result delivery

Publish unified outcomes to Sync Hub so multiple downstream consumers can update transaction insights, spending analytics, and customer-facing UI without polling Banking OS.

Use case coverage

Personal financial management (PFM)

Customer support

Enriched merchant and location context helps agents when customers dispute or query a transaction.

Analytics and engagement

The Banking OS Unified API lets you interact with enrichment providers through standardized interfaces. You integrate once, and you can change the vendor without changing the channel.

Available financial data aggregation connectors

SaltEdge

Multi-step transaction categorization with webhook callback and optional merchant resolution.

Plaid

Single-call synchronous enrichment through Plaid Enrich with personal finance categories, merchant details, and location in one response.
SaltEdge versus Open Banking: SaltEdge also appears in Banking OS Open Banking connectors for UK and EU PSD2 compliance. Connectors in this domain use SaltEdge for data enrichment. They are separate from PSD2 consent, account information services (AIS), and payment initiation services (PIS) flows under Open Banking.
For unified API operations, events, and error mappings, see API playground and each connector’s Reference page.