DescriptorAPI: Turn messy card descriptors into clean merchant data

Hey Product Hunt 👋 I'm Samy, and I built DescriptorAPI. The problem. Open any banking or budgeting app, and you'll see lines like POS 4521 CAREEM*RIDE DXB AE or PAYPAL *NETFLIX 4029357733. Users don't recognise them. That leads to support tickets, "I didn't make this charge" disputes, and budgets that put Netflix under "Other". What DescriptorAPI does. Send the raw line and get back the merchant name, logo, category, website, city, and payment processor. Every answer has a confidence score from 0 to 1, so you can show strong matches right away and send the rest to review. What's different: • Built for statements outside the US. It reads airport codes, local spellings, and Arabic script, and it strips processors and wallets like PayPal, Stripe, and Fawry to find the real merchant underneath. • You pay for answers, not attempts. A call counts only when it returns a merchant. Unknown lines are free. • Cheapest step first. Cache, then rules, then fuzzy match. AI only sees lines nothing else could answer, and its answer is cached. • Private by design. We need the descriptor, never the cardholder. Amounts aren't stored, and we don't train on your data. Try it in 10 seconds, no signup: paste any line from your own statement into the playground: descriptorapi.com/playground. Not a developer? Upload your credit card statement PDF at descriptorapi.com/statements and see where your money went: every merchant named, subscriptions and hidden fees picked out, all checked against your bank's totals. Free for 3 statements a month, and the PDF is never stored. Launch offer: the free plan gives 500 enrichments a month with no card. For Product Hunt, code PRODUCTHUNT takes 50% off Starter or Growth for your first 3 months. It's valid for 7 days. I'd love to know: what's the strangest descriptor on your statement? Paste it below, and I'll decode it live in the replies.