POST /transactions/enrich and publishes the enriched payload to Sync Hub in near real time. Channels still receive only an HTTP acknowledgement from Grand Central. Enriched data arrives exclusively through Sync Hub events.
How it works
The following diagram shows how Grand Central accepts an enrichment batch, how the Plaid Connector calls Plaid Enrich, and how Sync Hub delivers the result:Key capabilities
Single-call enrichment
Map Grand Central unified transaction batches to the Plaid Enrich request shape and receive enriched transactions and enrichment metadata in one vendor response.
Personal finance categories
Surface Plaid personal finance category (PFC) data on each enriched transaction, including primary and detailed category values and confidence.
Merchant mapping
Map Plaid merchant and counterparty fields into Grand Central
merchantInformation for consistent downstream consumption.Location and payment channel
Attach city, region, country, and coordinates when Plaid provides location enrichment, and preserve payment channel signals (for example, online or in store).
Unified asynchronous delivery to channels
Although Plaid responds synchronously to the connector, channels follow the same accept-then-deliver pattern. Grand Central acknowledges the REST request, then publishes
transactionsEnriched to Sync Hub with canonical category, merchant, and location fields.Supported operations
The Plaid Connector supports the following operations from the Grand Central transaction enrichment unified API.
Grand Central returns
202 with an empty body.
A request can contain a maximum of 50 accounts and 100 transactions in total. For schema limits and other restrictions, see Reference.
Enrichment events (Sync Hub)
When Plaid Enrich 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 Plaid directly. The following table lists the event that the connector publishes:
Published events use the standard Grand Central envelope. The
data payload includes per-transaction category, merchant, and location fields. Grand Central preserves Plaid native personal finance category taxonomy and does not remap categories to other vendor taxonomies.
For how Sync Hub distributes events to multiple consumers, see Sync Hub overview.
When to choose Plaid
The following table compares when Plaid is a fit and when another vendor is a better match:Core use cases supported
US personal and retail banking
Enrich core and linked-account transaction feeds for US retail and personal banking experiences.
Spending insights and personal financial management (PFM)
Group transactions by category and merchant, improve search using enriched narratives, and feed category-level aggregates into budget and goal features.
Linked external account transactions
Enrich transactions retrieved from external accounts so customers see consistent category and merchant context alongside internal accounts.