Bank Transfers Still Ask Permission. PayTo Doesn't.

Sending money should be as simple as sending an email. Instead, a bank transfer still asks for permission — business hours, clearing windows, a fee hidden in the exchange rate, and a card network taking its cut at every step.

PayTo was built to remove the middle.

What Is PayTo?

PayTo is an open payment standard — one simple way to describe any payment, whether it lands in a bank account or a crypto wallet. It builds on an existing internet standard, so a single payment link can point at a European bank transfer, a US one, Brazil's instant PIX, or a wallet on Core. One format, every rail.

And because it's just a link, a payment can travel anywhere a link can: a QR code, a button on a website, a chat message, even a printed sticker.

A Quick Example

A freelancer in Berlin invoices a client in São Paulo. No SWIFT form, no three-day wait, no 4% currency markup — she sends one PayTo link, the client pays straight from their own bank, and the money is on its way in seconds, not days.

What It Does

• Bank-to-wallet, wallet-to-bank — money and crypto described the same way
• Pay a website by its name — a shop publishes its domain as a payment tag, and you pay it without copying a long address
• No card network in the middle — no 2.9% + 30¢, no spread quietly skimmed off the top
• Built for QR — every payment can become a scannable code

Where It Fits

PayTo is the layer underneath everything else in the stack. Wall Money, CorePay, CorePort and MoneyX don't replace it — they speak it. Think of it as the shared language that lets a payment cross from a bank to a blockchain without a translator in between. And it isn't a whitepaper: PayTo is already live, and the tools to build these payment links are open source.

PayTo. Money that moves like the internet.