A payment gateway built the way we'd want to use one

Rectavion started from a plain observation, not a personal crisis. Across the high-risk payment processors we looked at, the basic facts a merchant needs (will you take my business, what will it cost) are treated as things you have to earn through a sales call. Four of five card processors we researched gate real pricing behind an application or a call. Not one of ten publishes a plain list of what it accepts and declines. That's an industry pattern, not a bad-apple problem, and it's the gap Rectavion exists to close: publish those two answers first, before anyone applies.

The name comes from the Latin rectus: straight, direct, fair. It's meant literally. The rate on the page is the rate you get, and the accepted/declined list is the real list, not a starting point for negotiation.

Status: Phase 0, in development

Here's what that actually means. There's no live processing yet, no signed merchants, and the rail (card, crypto, or both) hasn't been decided. What's on this site is the shape of what we're building, not a current offer, and every page says so where it matters. Publishing a claim we can't back up would be exactly the kind of overpromise this company exists to avoid making, so we'd rather the site look unfinished than pretend otherwise.

What is decided: the values that don't move regardless of which rail we end up on. Publish the number first. Stay a business the sponsor bank can see: no cloaking, no misrepresenting a merchant's business to an acquirer. Promise only what we can actually keep, and mark what we don't know yet instead of guessing.