Introducing DescriptorAPI

Today we're introducing DescriptorAPI, a new service from ApisOS FZE, the team behind IBANAPI.

The problem

Card statements are full of cryptic merchant descriptors like SQ *BLUEBTL 8442, AMZN MKTP US*2K4 or PAYPAL *STEAMGAMES. Cardholders don't recognise them. That leads to support tickets, "unknown transaction" disputes and chargebacks that never needed to happen.

What DescriptorAPI does

DescriptorAPI takes a raw card statement descriptor and returns clear, structured merchant information:

• Merchant name: the real, recognisable business behind the descriptor.
• Logo: a merchant logo you can show next to the transaction.
• Merchant details: extra context that helps a cardholder confirm a purchase at a glance.

Who it's for

• Banks and neobanks that want transaction feeds their customers actually understand.
• Fintech and expense apps that categorise and enrich card spending.
• Support and dispute teams that want fewer "I don't recognise this charge" contacts.

Built by the IBANAPI team

DescriptorAPI is built by the same team, on the same infrastructure, with the same focus on data accuracy that IBANAPI customers rely on for IBAN and bank validation. Both products are operated by ApisOS FZE. You can find our company details on the About page.

Get started

Visit descriptorapi.com to see the API and get your key. If you have questions, email us at [email protected].