Skip to main content
The Transaction API identifies the merchant behind a raw payment descriptor. STARBUCKS 1523 OMAHA NE means nothing to most customers. The Transaction API resolves it to Starbucks and returns the same brand object as the Brand API, with the name, domain, logos, colors, and company data. Merchants that are not in the dataset yet are indexed live, so small and local merchants are covered too. See real-time indexing.

Make your first request

Send the descriptor as transactionLabel and the country where the transaction took place as countryCode. The Transaction API uses the same API key as the Brand API, and must be called from your server:
The response is a brand object for starbucks.com. The Brand API overview describes every field.
Building an agent with no account? It can pay per request with x402 or MPP instead of using an API key.

Errors

Not every descriptor names a merchant, for example a transfer between accounts, so a label that matches no brand is an expected answer rather than a fault. Both codes below come back in the x-bf-error header and in the body’s error field, and neither uses an API credit. Every other error uses a Brand API code, explained in Brand API errors.

Quotas and usage

The Transaction API shares one quota with the Brand API and Brand Context API, counted in brand fetches. See limits and billing for quotas, throughput, and overage.

Go further

Transaction enrichment

A complete build that turns a transaction feed into merchant names and logos.

API reference

Every request and response field.