Documentation
Everything Pay,explained end to end.
What ePAY is, how a payment moves, what you can pay with and when each source opens, where it works, and where the fees go.
What ePAY is
A payment layer that lets you spend what is already in your wallet — anywhere — without selling, bridging or cashing out first.
Stripe lets merchants accept cards. ePAY lets people pay with what they already hold.
The mechanism
You hold USDC, SOL, a balance in fomo or pump, dollars in X Money, or a memecoin. You see something you want. ePAY takes it, converts it to dollars in the background, and pays the merchant on the rail that merchant already uses. You never touch a bank account or an exchange.
Crypto and X Money behind one button
People earn real dollars on X through protocols like UsePaid, which route memecoin creator fees to X handles as USD. Those dollars spend through the same checkout as your wallet, so there is one balance to think about instead of two.
What the merchant sees
A normal payment. No crypto on their books, no price exposure, and on the card rail nothing to integrate at all. That is the whole point: this cannot depend on convincing every shop in the world to install something.
Why this exists
Three things are true at once, and until now nothing sat in the middle of them.
01 — Crypto wealth is stuck in wallets
To buy a pair of shoes with SOL you used to swap, send to an exchange, sell, withdraw to a bank, wait days, then pay by card. Most people gave up and the value stayed where it was.
02 — Merchants do not accept memecoins
Integrating a crypto gateway store by store is slow, and most merchants do not want price volatility on their books. Asking them to change is the wrong end of the problem to push on, so ePAY does not.
03 — A new kind of income appeared
UsePaid alone has claimed roughly $1.35M in fees and paid out about $640K to X handles through X Money. Those dollars sit in X Money accounts, and ePAY is the checkout that treats them and a Solana wallet as one balance.
The insight
Nobody cares what rail the merchant uses. They care about one question — can I pay for this with what I already have? ePAY answers yes by sitting between your assets and the merchant’s normal payment method, and converting at the moment of purchase.
Who it is for
Memecoin holders, who are the most underserved spenders in crypto — no major card or gateway lets you pay from a pump.fun balance. And UsePaid recipients, already fluent in the idea that tokens turn into dollars. Both are reachable today.
How a payment moves
One flow, whatever you hold. Your funds go out, dollars arrive at the merchant, and the conversion happens in the middle where you can see it before you confirm.
At any online store
You pay with the ePAY virtual card — a Visa or Mastercard number issued to you. At the moment it is charged, ePAY prices the purchase, draws on your balance, and settles. The store sees an ordinary card payment. This is the rail that makes “anywhere” true.
At a store that integrates ePAY
A “Pay with ePAY” button, like Pay with PayPal. You connect a wallet, see the price in dollars, pick a funding source, and sign one transaction. The merchant receives USDC or USD by their own setting. No card-network fee, so it costs them less than cards.
By QR code
Solana Pay QR codes are read and paid directly on-chain. Scan, confirm, done — no account, no redirect, no card number to hand over.
With X Money
Sign in, then send the amount from your X Money account with your payment code in the note. ePAY matches the code to your order and settles it.
What you see before you confirm
One number, always. “You pay 0.482 SOL ≈ $54.20, includes the $0.54 fee.” The swap, the slippage ceiling and the fee are all inside that figure. Nothing is added afterwards.
What you can pay with
Seven funding sources, opening in three waves.
USDC — open now
Dollars already, so there is no swap and no slippage. Connect Phantom, Solflare or Backpack and pay straight from your wallet — ePAY never holds your private key. USDC is the source running today; everything below joins it on the schedule named here.
SOL — at launch
Routed to USDC through Jupiter at the moment you pay, at the best route across every pool. Same wallet, same single signature, and the quote with its slippage is shown before you confirm.
X Money — at launch
Sign in, then send the amount with your payment code in the note. ePAY matches the code to your order. Your X Money dollars and your Solana wallet sit behind one checkout and one card.
fomo and pump balances — at launch
Spend either balance straight through the checkout. No withdrawal step and no bridging: the balance you already have is the balance you pay with.
$ANSEM and $CATE — shortly after launch
The first two memecoins ePAY takes directly, routed to USDC as you pay. They are first because they have the liquidity to absorb a real purchase without moving their own price, which is the bar every token added after them has to clear.
The mints, in full
Both are pump.fun tokens on Solana mainnet, printed here in full so you can check a token before you spend it rather than trusting a ticker. A ticker can be copied; a mint address cannot.
How memecoin payments stay safe
Every payment carries a minimum liquidity floor, so a $100 purchase cannot move a price 20%. A 1–3% max slippage, shown before you confirm. A small price buffer, refunded in USDC. And a blocklist for honeypots, freeze authorities and transfer-tax tokens. A token that cannot clear those bars is marked not spendable up front rather than failing at the till.
Where it works
Almost anywhere online. The card rail alone reaches every store that already takes a Visa or Mastercard, and three more routes sit behind it.
| Rail | Coverage | How ePAY pays | Status |
|---|---|---|---|
| Virtual card | Almost every online store in the world | Card issuer partner, funded from ePAY’s USDC float | At launch |
| Pay with ePAY | Merchants who add the button | On-chain USDC, or USD to the merchant’s bank | Open now |
| Solana Pay | Merchants and QRs on the open standard | Direct on-chain USDC transfer | Open now |
| X Money | Anyone with an X Money account | P2P from ePAY’s X Money account | At launch |
What “anywhere” actually covers
The four rows above are routes, not destinations. Counting them undersells the answer badly: the card rail alone is an ordinary Visa or Mastercard number, so it reaches every merchant that already accepts one. Shopping, travel, food delivery, subscriptions, games, phone bills, anything with a checkout field. No integration, no partnership, no conversation with the merchant at all. The other three rails exist because each one is cheaper, faster or more direct than a card where it applies, not because the card leaves gaps.
Cash App and Venmo
Both open shortly after launch, and both arrive as direct payouts rather than resold gift codes. That is a slower way to build them and the right one — a resold code is a rail that works until the first time one is rejected, and then it is your money in the middle of the argument.
Fees, and where they go
ePAY earns on the conversion, not on you being surprised. And every payment fee it collects goes to holders.
Every fee ePAY earns from a payment is distributed to holders. The product is the buyback.
The fee, in one number
A small fee on every conversion to USDC, 1.5% or less on majors, with a clearly shown extra spread for memecoins with thinner liquidity. It is inside the figure you approve. There is no second number after you confirm. Paying in USDC converts nothing, so there is nothing to spread.
Where the fee lands
Fees accrue in USDC in the ePAY treasury on Solana, alongside the float that settles card payments and merchant payouts. Every payment produces a receipt with a public transaction link, so the flow is checkable rather than asserted.
And then it goes to holders
Every payment fee ePAY earns is distributed to holders. Fees are not retained as a house margin — they are collected in USDC and passed through, pro-rata, to the people holding. More spend means more fees, and more fees means more distributed. That is the whole loop.
The other revenue lines
Card interchange, where issuers share part of the fee merchants pay. A merchant gateway fee set below Stripe. A thin margin when USDC is converted to USD for a bank payout. And Jupiter referral fees on swaps. The distribution above is the payment fee — the line the person paying actually sees.
What holders are entitled to
A share of the payment fees, proportional to what they hold, and nothing else. There is no gate, no tier and no promise of anything the fees do not produce. The number that matters is volume, and it is the only number that matters.
Why it clears instantly
A card authorisation has to clear in about a second. An on-chain swap takes longer than that. ePAY is built around closing the gap rather than pretending it is not there.
The ePAY balance
You hold a USDC spending balance inside ePAY, and card charges draw on it the instant they arrive. Nothing waits on a block. Topping it up is one transfer, and auto top-up keeps it at whatever floor you set — keep $50 on the card, pull from SOL.
The float behind it
ePAY keeps USDC and USD ready to settle card payments and merchant payouts before your funds finish converting. That float is what lets an authorisation be approved in under a second while the conversion completes behind it.
On-chain payments
Solana Pay and Pay with ePAY settle directly on-chain, so there is no authorisation window to beat and no float involved. You sign once and the merchant is paid.
Why the mechanics are on this page
A payment product that hides its settlement model will surprise someone at a checkout. The top-up step is visible in the flow rather than buried, and the quote you approve is the amount that leaves your wallet.
Money flow
ePAY is UsePaid’s capital flow running in reverse.
The two directions
UsePaid moves memecoin fees in SOL → exchange → USD → X Money → person. ePAY moves your funds → Jupiter → USDC → card issuer or merchant → store. Same plumbing, opposite direction.
Float
Enough USDC and USD stays ready to settle card payments and merchant payouts before user funds finish arriving. What gets tracked: float balance, pending settlements, swap failures, refunds and chargebacks.
Custody
The float is held in USDC on Solana under multisig, with hardware or MPC keys. Your own funds are yours until the moment you confirm a payment — ePAY never holds your private key, and a wallet payment is signed by you and nobody else.
Receipts
Every payment gets a receipt and a public transaction link. The flow in and the flow out are both on chain, which means you can check them rather than take them on trust.
The settlement wallet
Every payment made through ePAY settles to one address on Solana, and it is printed below. Open it in an explorer and you can see every payment that has ever landed there — the ledger is public whether or not anyone is looking at it.
- Settlement walletEvery payment settles here.BkqioAWHagLqgAcfVK9B23ptQadEL9aNA97tVk8tYLMA
Limits and safety
What ePAY checks, what it refuses, and what it will not do with your money.
Account tiers
Wallet only, for on-chain payments and the merchant gateway at smaller amounts. Basic identity checks for a virtual card with moderate limits. Full checks for high limits and X Money. The card network requires it — a card that nobody can be identified behind is not a card any issuer will run.
Token screening
A token has to clear a minimum liquidity floor before it can be spent at all, and honeypots, freeze authorities and transfer-tax tokens are blocked outright. This happens before you reach a checkout, so a token is marked not spendable rather than failing mid-payment.
Price movement
A memecoin can move between quote and settlement, so quotes expire quickly, slippage is capped at 1–3% and shown before you confirm, and a small buffer is charged and then refunded in USDC. If a swap fails on a congested block it is retried with priority fees, and there is always a refund path.
Wallet screening
Sanctioned and flagged addresses are screened on both sides of a payment. On-chain payments cannot be reversed, which is exactly why the checks happen before the transfer and not after it.
What is final
An on-chain payment is final once confirmed. A top-up lands on the account you name and cannot be pulled back, which is why the checkout asks you to confirm that address twice. Card payments follow the normal card dispute process.
What opens when
USDC runs today. Everything else lands on a schedule, in this order.
| Wave | What opens | Detail |
|---|---|---|
| Open now | USDC | Wallet payments, Solana Pay and Pay with ePAY, settling in USDC |
| At launch | SOL · X Money · fomo · pump | Conversion through Jupiter, plus the virtual card and auto top-up |
| Shortly after | $ANSEM · $CATE | The first two memecoins taken directly, with Cash App and Venmo payouts |
| Then | More tokens and merchants | Any token that clears the liquidity floor; more chains once Solana is settled |
How a token gets added
It has to hold enough liquidity that a real purchase does not move its own price, route cleanly on Jupiter, and carry no freeze authority or transfer tax. $ANSEM and $CATE clear that bar, which is why they are first rather than because they were chosen.
How a merchant gets added
Gift cards and balance top-ups open as soon as the supplier is live, because they deliver the moment a payment confirms. Physical goods open per merchant. The tabs on the catalogue that are not open yet are priced and dated already.
API access
The ePAY API is private. It is not open to sign up for, and there are no public keys: access is granted per project, after a request.
Why it is private
Every endpoint moves money or reads a balance. A key handed out automatically is a key nobody has read the use of, and on a payments API that is the whole risk. Access is granted by a person who has seen what it is for.
What you get
Keys for your environment, the rate limits that match your volume, and the reference for the endpoints your integration actually needs: checkout sessions, payment status, balances, receipts and webhooks.
How to ask
Send a request with what you are building and what you need the API to do. Be concrete. A request that names the product, the flow it plugs into and the rough volume is answered quickly; one that says “integration” is answered with questions.
What happens next
Requests are read by a person, not a queue. If your use fits, you get keys and the reference for your endpoints. If it does not, you get told why rather than left waiting.