XRayAI

Card processing is one of those things almost nobody understands until something goes wrong. Around 90% of US businesses are overpaying. 80% of owners can't fully read their own statements. 70% are out of PCI compliance, usually without realising it. Most never find out until they get audited or quietly start losing margin to a rate increase nobody mentioned. The other side of the market isn't much better, payment providers spend half their week prospecting cold, asking for statements, and explaining basic pricing before they can even start a real conversation. XRayAI came to us wanting to fix both sides with the same product. Merchants would get a free, honest look at what they're actually paying. Providers would get a clean pipeline of merchants who already understand their numbers and are ready to talk. The work split naturally into three surfaces the marketing site, a merchant portal where owners upload statements and see results, and a partner portal where vetted providers meet those merchants on the other side.

Merchants get answers in minutes. They see the full breakdown of their fees, learn where they sit against businesses like theirs, find out whether they're PCI compliant, and start getting alerts when something on their bill quietly changes. Average users identify 10–30% in savings against what they're paying today. When they're ready to act, they take that verified baseline straight into the marketplace and pull real offers from vetted providers, without sitting through a single sales call. The provider side ended up being the more counter-intuitive win. Sales cycles in payment processing are usually long and expensive because providers spend most of their time qualifying. With XRayAI, the qualification is already done before the provider shows up. Every merchant they see has uploaded a statement, understands their numbers, and is in evaluation mode. Close rates go up, cycle times come down, and the first conversation starts with verified data instead of a cold pitch. The whole platform works because one engine serves both sides. The clarity that earns the merchant's trust is the same clarity that turns that merchant into a qualified opportunity for the provider. That's the product.

The product is three Next.js apps sitting on top of one Python service. The marketing site loads fast, ranks well, and gets the right person to the right call-to-action quickly. The merchant portal at merchant.xrayai.io handles uploads, the analysis dashboard, the alerts feed, PCI tracking, and the provider marketplace. The partner portal at partner.xrayai.io is a separate app for vetted providers, with onboarding, a live pipeline of opted-in merchants, the supporting baseline data behind every opportunity, and the tools to actually work the deal. Underneath all of it is a Python pipeline that does the real work. It takes a processing statement PDF, cleans it up, and hands the heavy interpretation to Claude. Claude reads a statement the way a payments analyst reads one tagging interchange, calling out assessments, separating real network costs from processor markup, flagging anything that looks like a non-compliance fee, and comparing effective rates against industry baselines. Every output traces back to a specific line on the merchant's own statement. Statements never cross from the merchant side to the provider side until the merchant explicitly opts in to share, that boundary is enforced in code, not just policy.