Do you store PANs or account numbers?

Never send sensitive card data — pass merchant descriptors only, following your PCI policies.

Does coverage include international descriptors?

Yes — include `country_gl` when you have it for better resolution on regional processors.

Do you return multiple logo variants?

Yes — SVG when available, raster fallbacks, and type hints so you can pick the right asset for light and dark UI.

How does usage scale for this endpoint?

Crawl jobs grow with pages discovered; single-call endpoints are one request. See the API reference for request semantics.

★ IDENTIFICATION / 15 OF 15

The merchant, from the descriptor.

Turn 'SQ *BLUE BOTTLE 4471' into Blue Bottle Coffee, with a logo, a category, and a website — built for neobanks and expense tools.

api.orsa.dev

Resolve a bank descriptor to a merchant and category.

Live API response — no signup required.

0ms

p50 latency

1.6s

p99 latency

94.1% merchant resolution on sampled processors

quality

credits per call

One call in. A resolved merchant out.

Integration

Three lines to structured data.

Drop this into your codebase. TypeScript, Python, cURL — pick your language.

example

Response

{
  "transaction_info": "SQ *BLUE BOTTLE 4471",
  "name": "Blue Bottle Coffee",
  "domain": "bluebottlecoffee.com",
  "naics": "722515",
  "logo": "https://cdn.orsa.dev/bluebottlecoffee.com/logo.svg"
}

Who builds with this

Real jobs this endpoint solves.

Card feeds

Replace cryptic strings with recognizable brands.

Expense automation

Route spend to the right GL without user edits.

Risk signals

Ground alerts in merchant identities, not raw strings.

Combine with

NAICS Classification Company Logos Company Description

FAQ

Common questions.

Can't find your answer? Check the docs or reach out.

Try this endpoint. Free.

No credit card. Most teams integrate in under 10 minutes.