USDTonPay

A FOUNDER NOTE

An Idea That Started in 2019

Some projects begin because you see an opportunity. Others stay with you quietly for years, like a seed you never quite forget.

For me, USDTonPay is the second kind.

01

In 2019, I first tried to build this

Sending USDT was already becoming familiar to more and more people. Open a wallet. Enter an address. Enter an amount. Confirm. A few minutes later, the money arrives.

But the moment you try to use that same transfer as a real payment for a business, everything becomes more complicated.

Who sent this payment? Which order does it belong to? Was the correct amount paid? And once it arrives, how does the merchant's website know?

Transfer is easy. Payment is hard.

A developer working at a desk late at night

I did not want to build a wallet. The customer should pay, and the USDT should go directly to the merchant's own wallet. The system should only handle everything around that payment: creating the order, presenting the payment information, detecting the transaction, confirming it, and finally telling the merchant's system that it was paid.

Today, that idea may sound obvious. In 2019, building it properly was anything but obvious.

02

I talked to a lot of developers

Some understood part of the idea. Some suggested building a wallet. Others suggested generating deposit addresses for users. Each time, I came back to the same answer: that was not what I was trying to build.

I wanted payment infrastructure, not custody. The customer's money should move from the customer's wallet directly to the merchant's wallet. We should simply stand beside that transaction and verify that it happened.

The deeper we went, the more edge cases appeared: simultaneous payments, matching orders, incorrect amounts, slow networks, confirmations, and the moment after a customer closes the page.

The difficult part was never generating a QR code. The difficult part was everything behind it.

03

So I put it aside

Not because I believed the idea was wrong. I began to think that maybe the timing was wrong. The infrastructure was not as mature as it is today, and I had not yet fully understood what merchants actually needed.

City lights seen through a rain-covered window at night

Years passed. I worked on other businesses, websites, orders, customers and online stores. But every now and then, something would bring the old idea back. Most business ideas disappear after a few weeks or months. This one remained there like a question I had never finished answering.

04

Over those years, I changed too

In 2019, I had been thinking about payments from the perspective of blockchain. Later, after spending more time actually running online businesses, I realized that was backwards.

A merchant does not care how sophisticated the technology behind a payment system is. They care about simpler questions: Did the customer pay? Which order was it? When was it paid? Can my website know automatically? And most importantly: where is my money?

My answer became increasingly clear. It should not be with us.

05

Seven years later

In 2026, I opened the idea again. This time, I did not think about it for a few minutes and move on. I asked myself seriously: could I finally build today what I could not build seven years ago?

So I decided to try again. The tools were more mature, ideas could be tested faster, and this time I was not working alone. We organized assumptions, inspected the logic, found edge cases, and rebuilt one problem at a time.

A laptop on a desk in early morning light

We redesigned the payment flow. We redesigned the order logic. We rebuilt the payment states. We tested, failed, changed things, and tested again.

AND THEN, ONE DAY

PAID
Payment confirmedOrder matched · Merchant wallet received USDTLIVE

To the system, it meant a payment had been confirmed. To me, it was an answer I had waited seven years to see.

06

But we still decided not to touch your money

There were easier ways to design the system. We could have received customer funds ourselves and settled them to merchants later. But eventually I came back to the same question I had asked in 2019: why should the money need to pass through us at all?

If blockchain already allows a customer to send USDT directly to a merchant, there is no reason for USDTonPay to place itself in the middle of the funds.

Your money never passes through us.

The customer pays. The merchant receives. USDTonPay helps the systems understand which order the payment belongs to, whether it happened, when it was confirmed, and what should happen next.