Posts
Practical writing for payment operations, risk, and issuing teams — what we learn building the layer between raw transaction data and the people who have to act on it.
Most unrecognised charges are not fraud. They are the trading name losing a fight with a 25 character field. Here is how to read a statement line and identify a charge in a few minutes.
No annual fee means one charge is removed, not all of them. Here is what still appears on the statement of a card without annual fees, and how to read each fee line.
A JCPenney charge often does not say JCPenney. Here is why the descriptor can read SYNCB, what the store card and the Mastercard do differently, and how to check a charge you do not recognise.
Kohl's card charges often show a store number or the issuing bank rather than a clean brand name. Here is how to read the line, and how rewards and Kohl's Cash affect what you see.
Bud publishes a 12k logo library and operates in the US and UK, with additional engagement to open new markets. Here is how that compares to a global engine, over 150k logos refreshed daily, and webhook delivery.
On the core product the two are close — both return 512×512 logos and clean merchant names. The differences are in coverage outside DACH and the UK, what you pay and for how long, whether you need a DPA at all, and who picks up the phone during implementation.
Both resolve cryptic card descriptors into clean merchant names and logos. The differences that matter are logo resolution and consistency, how much of the world the data actually covers, and what you have to commit to before you see a result.
Most disputes an issuer sees are not fraud — they are recognition failures. Clean names, logos and categories remove the ambiguity before a cardholder ever opens a dispute.
We use essential cookies to make this site work. We don't use tracking or advertising cookies. Privacy Policy
