GeekPay now settles every payment through NEAR Intents.

Checks, invoices, Paytags, Checkout and payouts all move across one rail. You send the token you already hold. Your recipient gets the token they asked for, on the chain they asked for. Neither of you touches a bridge, and neither of you needs a gas token to make it work.

What this means if you are sending money

Any chain to any chain. Hold USDT on Tron, pay someone who wants USDC on Base. No bridge, no swap, no wrapped asset, no second set of fees.

The recipient needs nothing. GeekPay covers gas on the hub and on the destination. Getting paid never requires already owning the right token on the right chain — which is the quiet reason most first crypto payments fail.

Confidential settlement, everywhere. Payments settle from the shared rail rather than from your wallet, so what lands on chain does not trace back to you or your history. On every surface now, not just some.

Pull-backs where they are possible. Checks and invoices hold value in the rail until the recipient claims it, so you can retrieve a payment that has not been taken yet.

What changed

The rail has been carrying production payments for a while — if you have sent anything through GeekPay, you have already used it. What is new is that it is now the default path for every payment surface, rather than some flows routing and others going direct.

That sounds like plumbing, and it is. It is also the difference between a guarantee and a footnote. Gasless receiving, confidential settlement and recoverable holds are either true of every payment or they are marketing copy. Making the rail the default is what puts them in the first category.

How it works, briefly

A transaction tells a chain how: call this contract, with these arguments, in this order. An intent states what: I have this, and I want that to arrive there.

GeekPay expresses your payment as an intent and settles it on NEAR. Solvers compete to find a route that satisfies it and are paid only on delivery. The complexity of getting from one chain to another moves off you and onto the network.

Bridges have been the most expensive category of failure in this industry — not because the teams building them are careless, but because a bridge is a large pot of money that has to be right every time. The useful question was never which bridge to pick. It was whether a person sending a payment needs to touch one at all.

They do not.

Why NEAR

Chain abstraction is not a side project at NEAR; it is the thing they build toward on purpose. We needed a settlement layer whose reason for existing was making chains stop mattering to the person sending money, and that narrowed the field quickly.

NEAR also backed the work with a grant, which we say plainly rather than letting it read as a neutral technical pick.

What this does not change

GeekPay remains non-custodial. We never take ownership of your funds and cannot move them on our own — routing a payment is not holding it.

Public pages stay final. If someone pays your Paytag or a public invoice from their own wallet, that payment completes the moment they approve it; the pull-back applies to payments that start inside GeekPay.

And the chain is still public. Settlement transactions exist and anyone can read them. What changed is that they no longer point back at your wallet.

Try it

Send a payment to yourself in a token and chain you do not normally hold, and watch what arrives. The interesting part is everything you did not have to do on the way — start at app.geekpay.co.