API Reference
Start typing to search…

Enrichment overview

Overview

Before you enrich transactions, it's important to determine which endpoints you will be hitting, what your integration pattern will be, and what type of data you will receive. This set of guides will help you design your integration and start enriching your transaction data through our API.

Endpoints:

We enriches card and transfer data via two separate endpoints to capture inputs unique to each type of spend, and return a single, unified response. You can determine which endpoint to integrate with based on the following criteria:

  • Card enrichment: our card enrichment endpoint is designed to ingest first party and streamed card data from the ISO8583 message.
    • If you receive raw DE43 data from your issuer (e.g., WALMART.COM BENTONVILLE ARUS") you should hit our /transactions/cards/enrich/parse endpoint.
    • If you receive parsed data or already do parsing on your end (looks like MerchantName: Walmart.com, City: BENTONVILLE, Region: AR, Country: US), you should hit our /transactions/cards/enrich endpoint.
  • Transfer enrichment: our transfers endpoint is designed to ingest first party transfer data (e.g., wires, ACH payments, ATM transactions). Head to our transfer enrichment API reference to learn more.

Integration methods:

  • Real time enrichment: send single transactions and received enhanced data with a p99 of under 50ms. These endpoints are best for use cases with low latency requirements or data models that receive transactions in single events.
  • Batch enrichment: send batches of up to 50,000 transactions at once for mass enrichment. Results can be retrieved through webhooks or endpoint polling. These endpoints are best for use cases with no latency requirements. Learn more about batch enrichment here or head to our batch card or batch transfers API references.

Enriched data types:

We offer two levels of enriched data:

  • Core data enrichment: our foundational layer of factual transaction including factual details like merchant name, logo, category, counterparty ID, and location – delivered in real time and designed for consistency across rails. These are included in our base product package.
  • Enhanced data features: premium fields and predictive signals – like Google Play app data, fraud risk indicators, and recurrence detection – that can be activated based on your use case. These add-ons and can be purchased by contacting [[email protected]]