Key capabilities
Multi-step categorization
Orchestrate SaltEdge categorization buckets, accounts, transactions, and start flows.
Merchant resolution
When SaltEdge returns a
merchant_id, the connector calls the SaltEdge merchants API to retrieve names, contact information, and address data. The connector adds the merchant details to the enrichment event.Webhook-driven completion
Receive SaltEdge categorization completion callbacks on a Grand Central webhook endpoint. The connector verifies the SaltEdge signature on every callback.
Unified async delivery
Transform SaltEdge-native responses into the Grand Central enrichment event model and publish to Sync Hub for the Engagement Banking Platform and other subscribers.
Supported operations
The SaltEdge Connector supports the following operations from the Grand Central transaction enrichment unified API.Outbound
Inbound (webhook)
Replace
{baseURL} with the transaction enrichment API base URL and {baseInboundURL} with the transaction enrichment inbound API base URL from your setup. Register the webhook URL in your SaltEdge configuration to receive categorization completion callbacks.
Grand Central returns 202 with an empty body. The response does not contain enriched transaction data.
An enrichment request can contain a maximum of 50 accounts. Each account can contain a maximum of 100 transactions. For the full validation rules, see Reference.
Enrichment events (Sync Hub)
When SaltEdge categorization completes, the connector publishes unified enrichment events to Sync Hub. Downstream consumers subscribe to Sync Hub to receive updates. You do not need to poll SaltEdge directly.
Published events use the standard Grand Central envelope. The
data payload includes per-transaction category, merchant, location, and counterparties.
The connector publishes an event only when the SaltEdge callback reports a completed categorization. For any other callback status, the connector acknowledges the callback and publishes no event.
For how Sync Hub distributes events to multiple consumers, see Sync Hub overview.
Core use cases supported
Spending insights and PFM
Group transactions by category and merchant, improve search using enriched narratives, and feed category-level aggregates into budget and goal features in digital banking apps.
Agent-assisted servicing
Give agents enriched merchant and location context when customers dispute or query transactions.
Related topics
- Reference for the Grand Central Unified API endpoints that support these features.
- Get started for deployment steps.