Crypto payments are easy exactly once.

Sending money to one person, one time, from one wallet is a solved problem and has been for years. The trouble starts the second time — when it is twelve contractors on the last working day of the month, when the only person who holds the keys is on a plane, and when someone eventually has to explain to an accountant what a 42-character string was for.

That gap, between a transfer works and a company can run on this, is what GeekPay exists to close.

What it actually is

GeekPay is a payment rail for companies that pay and get paid in crypto. It gives you four ways to move money, keeps your wallet and history out of public view by default, and puts an assistant in front of the admin so the work is approving things rather than doing them.

It is non-custodial. Your wallet is yours.

Four ways to send, and how to choose

Most of the confusion about crypto payments disappears once you ask one question: what does the person on the other side already have?

If they have nothing

Use a Check. You commit the funds and send a link. They claim it with an email and can create a wallet at that moment if they need one. Unclaimed checks expire and return to you.

If you are billing them

Use an Invoice. They pay from whatever wallet they already use, in whatever token they already hold. Reversible until it is paid.

If it happens repeatedly

Use a Paytag — a permanent public page at your name. Anyone can pay you, any amount, any time, without ever seeing a wallet address.

If you are selling something

Use Checkout — a pay button on your own site, settling to the token you want.

The first two are reversible until the other side acts. The last two are not. That difference matters more than any feature.

The address is the part that should not exist

A wallet address is a bearer instrument pasted into a spreadsheet. It cannot be verified by eye, it is chain-specific, and once a transfer confirms there is nobody to appeal to.

Every surface above removes it. The recipient picks their own chain and token; you never type an address. Gas is handled on both ends, so they do not need a gas token to receive money.

The address is the part everyone focuses on, and the part that should not be there at all.

Confidential by default

Anyone with one of your addresses can walk your entire payment history — who you pay, how much, how often, and what you have left. For a company, that is your payroll and your runway, public.

GeekPay settles so that what lands on chain does not point back to you. The person you are paying sees the payment. They do not see your wallet.

An assistant that does the paperwork

You ask, it does the work, you approve. Chase an unpaid invoice, pay a list of contractors, categorise last month’s outgoings, tell you what you spent on design.

It works inside GeekPay, and over MCP from assistants you already use — so the same actions are available from your own tooling. Limits live on the wallet, not in the prompt: the assistant proposes, you approve, and it cannot exceed what you have allowed.

The Concierge is included from the free tier.

Where the record lives

Every payment carries a category, a note, and who approved it — so the question “what was this?” has an answer next quarter. Roles and permissions separate whoever approves an amount from whoever sends it, which on a spreadsheet is a step that usually does not exist at all.

For platforms

If you are building a product rather than running payroll, the same rails are an API. Create a wallet for every user, then move money with one call — non-custodial, no gas, any chain.

POST /v1/wallets             a wallet for your user
POST /v1/payments            send, request, settle
GET  /v1/wallets/:id/balance

What it costs

Basic — 0.5% per transaction, never more than $25. No setup fee, no monthly fee. All four payment types, confidential by default, AI Concierge included.

Pro — $299 a month plus 0.2% per transaction, and your bill never passes $2,500 a month. Team roles and permissions, dedicated support. Built for companies running regular payroll, usually from around $100k a month.

Platform — custom. For products embedding wallets and payments for their own users.

The cap is the point: on Basic a single large payment costs the same $25 whether it is $5,000 or $500,000.

Who this is not for

If you send one payment a quarter, a wallet and a careful copy-paste will do, and you do not need us.

GeekPay starts earning its place when payments become a routine — a payroll run, a stream of client invoices, a product that has to pay its own users — and when more than one person needs to be involved without sharing a seed phrase.

Getting started

Send a Check to yourself and claim it. It takes about two minutes and shows you the whole model end to end — start at app.geekpay.co.

GeekPay is backed by Sigma Software Labs, with a grant from NEAR.