ZeroFee Pay

Pay links & payments

Ask for an exact amount in the coin you want, for example exactly 25 USDC on Solana. Whoever opens your link pays with a coin they hold on 70+ chains, and it lands at your own address: a standard link delivers exactly that amount, a private one at least it. The payer pays every fee. ZeroFee adds 0% and never holds the money.

Paid straight to your address

ZeroFee never holds the money, keeps no merchant accounts, stores no links and adds 0%. It connects the payer straight to exact-output swaps on Relay or NEAR Intents, whichever asks the payer for less: the payer sends from any wallet or exchange to a one-time deposit address that protocol issues, and the protocol pays you. No settlement delay, no chargebacks, no middleman taking a cut. Rules for accepting crypto differ by country and business; this page is not legal or tax advice.

What you get

The link is the request: Everything is in the URL: your address, the chain, the coin, the amount, and an optional name and note. Nothing is saved on a server, so there is nothing to sign up for and nothing to delete.
70+ chains in: The payer picks a coin they hold on any of 70+ chains and sends it to a one-time deposit address from any wallet or exchange. There is no wallet to connect.
Never delivered short: A standard link delivers exactly the amount; a private link delivers at least the amount, often slightly more. The payer pays every fee and sees how much of their coin that takes before paying. A short payment is refunded, never delivered short.
Straight to you: The payment lands at your address. ZeroFee is never in the path of the money.
How fast: Seconds from Base, Arbitrum or Ethereum on a Relay route, instant for the same coin on a fast chain, about 17 to 45 seconds on NEAR routes (how Solana payers pay), minutes from Bitcoin. See How fast is it.
0% from ZeroFee: No platform fee. The route provider (Relay or NEAR Intents) and the networks charge their own, shown to the payer before paying.
Private if they want: The payer can send it through the Solana ZK pool, Zcash shielded or Monero, stacked their way. See Paying privately.
Yours, end to end: No custody, no accounts, no middleman between you and your payer. You confirm receipt in your own wallet.

For merchants: make a link

1
Open Pay links (in the header). Under You receive, pick the coin and chain you want to be paid in. The default is USDC on Solana.
2
Enter the Exact amount, for example 25.
3
Enter your address on that chain. It is checked against the chain's address rules before a link is made.
4
Optionally add your name, shown to the payer (up to 60 characters), and a note such as Invoice #1042 (up to 120).
5
You get the link, a QR code and a ready-made “Pay with crypto” button (an HTML snippet for your site). Share any of them.

Each payment gets its own deposit. There is nothing to set up and nothing to reconcile on our side: watch the money arrive at your address, and follow any single payment from its own swap page or tracking link.
A link can be paid more than once. It is a reusable request, not a one-time invoice. Put an invoice number in the note and match payments in your own wallet history.
A link is public to whoever has it. Anyone who sees it sees your address, the amount, the name and the note.
Pick a coin NEAR Intents lists (USDC, USDT and the major native coins work best). Whether other coins can pay a link is checked against NEAR Intents' list; a coin it doesn't list can be paid only in that same coin. See How it works.

Link format

Format

https://zerofee.si/pay?to=<your address>&chain=<chain key>&token=<mint | contract | native>&amount=<decimal>[&label=<name>][&note=<text>]

to: Your receiving address on that chain.
chain: A chain key from GET /api/v1/chains (sol, eth, base, arb, btc…). Only chains that can be paid to (canReceiveOn) are accepted.
token: The token's mint (Solana) or contract (EVM), or native for the chain's own coin.
amount: The exact amount you receive, in whole units (25 means 25 USDC).
label: Optional. Your name, shown to the payer.
note: Optional. A note shown to the payer, such as an invoice number.

Example: exactly 25 USDC on Solana

/pay?to=<your Solana address>&chain=sol&token=EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v&amount=25&label=Coffee%20shop

For payers: pay a link

The link opens a page that reads, for example, Pay Coffee shop — 25 USDC on Solana, and says that the merchant receives exactly that amount.

1
Under Pay with, tap a coin or search for one you hold on 70+ chains.
2
Enter a refund address on the chain you pay from; if anything goes wrong, the money comes back there. There is no wallet to connect: you pay from any wallet or exchange.
3
Read You send …: the exact input needed for the merchant to get exactly the amount, and which route carries it (Relay or NEAR Intents, whichever asks you for less). On a NEAR route it includes a small price margin that is refunded if unused; a Relay route is exact, or refunded.
4
Confirm. The route provider (not ZeroFee) issues a one-time deposit address; send exactly the amount shown to it, on the right network, from any wallet or exchange. The swap's own page (/swap/<id>) follows the payment to the end: the deposit card with its network warning and deadline, and tracking links. If something goes wrong, the page tells our team and offers a support ticket. Once the payment finishes, that browser forgets it, and nothing is kept on a server.

Already holding the merchant's coin

No swap is needed. The page shows the chain's standard transfer request instead, as a link and a QR code you can scan with a compatible wallet. It goes straight from your wallet to the merchant, with no routing and no fee beyond the network's:

Solana Pay on Solana: solana:<to>?amount=…&spl-token=<mint>&label=…&message=…
EIP-681 on EVM chains: ethereum:<token>@<chainId>/transfer?address=<to>&uint256=<raw amount>, or ethereum:<to>@<chainId>?value=<wei> for the native coin.

On other chains the page shows the address and the exact amount to send.

Paying privately

A normal payment can be followed on-chain from the payer's wallet to yours. Under Privacy, the payer can switch on the Solana ZK pool, Zcash shielded or Monero, one or several, in the order they choose, and the payment reaches you without that public trail. The page draws the path and shows the cost and the time before they pay. It works from a coin they hold or from your own (USDC to USDC through Monero). What each protocol hides.

At least the amount. Prices move while a privacy step runs, so a private link promises at least the amount, never less. With Monero alone the payer sends a 3% cushion and you receive everything that arrives: at least the amount asked unless prices move more than 3% while Monero confirms. With the ZK pool or Zcash, the payment is worked out backwards from your amount; what it doesn't use goes back to the payer, or travels with the payment when it can't go back privately, and the payer sees which before paying.
Time and minimums. About 3–5 minutes for the ZK pool, several minutes for Zcash and about 15–30 minutes for Monero, whose minimum is about 50 USD. The page shows the live time estimate before the payer pays, and below a minimum it says the minimum in your coin. For Monero, the payer's coins are held for a few minutes on the way.
Temporary wallets in the payer's browser. The ZK pool and Zcash run through wallets made in the payer's browser, as on the swap page. The payer keeps the page open until it finishes.
Refunds. A step that fails is tried once more; if it still can't finish, the money goes back to the payer's refund address. If the Monero step needs a hand after the XMR has been sent on, the payment's page flags it to our team and its support button opens a ticket with the payment attached.

Paying someone else's request: paste or scan it

Someone shows you a payment QR code or sends you a payment link from their wallet or shop? Paste it, or scan it with the QR button, in the pay page's Paying someone? box. ZeroFee reads ZeroFee pay links, BIP21 (bitcoin:, litecoin:, dogecoin:, bitcoincash:, zcash:, dash:), EIP-681 (ethereum:, native coins and tokens on any EVM chain ZeroFee routes), Solana Pay transfer requests, TON transfer links and plain addresses. It sets the chain, the exact coin (matched by its contract or mint, never by name) and the address. When the request names an amount, it offers to pay exactly this from any coin you hold.

The camera image never leaves your device: the QR code is read in the page. No camera? Upload a photo of the code instead.
An Ethereum-style address works on every EVM chain, so ZeroFee keeps the chain you picked and says so; an address that belongs to another chain is offered (“receive on Bitcoin instead”), never switched silently.
A Solana Pay transaction request (the shop builds the transaction) has to be paid from a Solana wallet; ZeroFee says so rather than guessing.

How fast is it — and is it fast enough for shopping?

Short answer, as of 14 Oct 2026: seconds on the fast routes, with the money at your own address and no payout day. Shopping is a speed test: at a till, with a queue behind the payer, a payment has to confirm in about 2 to 3 seconds; online, a customer will wait a little longer for the green tick; an invoice can wait minutes. Here are the measured numbers, route by route, where each one fits, and how it compares with the other ways of being paid.

From the payer's tap to the money at your address

1
The payer sends. They send the exact amount to the deposit address, from any wallet or exchange. Their transaction goes onto their own chain.
2
Their chain confirms it. Typical confirmation: Solana about 1 second; Base, Arbitrum and Optimism about 2 seconds; Ethereum about 12 to 15 seconds; Bitcoin, minutes.
3
The route fills the order. On a Relay route the fill estimate is 0 to 2 seconds after the payer's transaction confirms. Relay issues deposit addresses only on EVM chains, so a payer on Solana goes through NEAR Intents. A NEAR Intents estimate already includes the origin chain's confirmations: about 17 to 47 seconds from the fast chains.
4
You have the money. The exact amount lands at your own address. There is no payout day, no batch and no hold: what you see at your address is the money.

End to end, a Relay payment from a fast chain is roughly steps 2 and 3 added together: about 3 seconds from Base, about 4 seconds from Arbitrum to Base. That sum is our own addition from the two estimates, not a separate measurement, and a real payment can take longer than an estimate.

What we measured (14 Oct 2026)

Live prices for $25 payments on 14 Oct 2026. No funds were moved, so these are the providers' own estimates for each route, not completed payments.

Relay (a “strict” deposit address tied to the order):

From Solana: Solana payers go through NEAR Intents, about 17 seconds: Relay issues deposit addresses only on EVM chains (checked 14 Oct 2026).
Base ETH → exactly 25 USDC on Solana: About 1 second. Cost 1.18%, against 1.88% on NEAR Intents for the same payment.
Arbitrum USDC → exactly 25 USDC on Base: About 2 seconds. Cost 0.10%, against 0.53% on NEAR Intents.
Cost at $25: 0.10% to 1.18% in the pairs checked. Where Relay could price a pair, it was cheaper than NEAR Intents in every pair.
From a deposit address: Relay uses a strict address tied to the order. An underpayment is refunded; an overpayment fills the amount asked and the rest is refunded.

NEAR Intents (its estimates include the origin chain's confirmations). Merchant paid on Solana:

From Solana (SOL): About 17 seconds
From Arbitrum: About 22 seconds
From Base, Optimism or Polygon: About 32 seconds
From Ethereum: About 42 seconds
From Zcash: About 7.5 minutes
From Bitcoin: About 13 minutes
Merchant paid on Base: About 22 to 47 seconds from the same fast chains.

Same coin, and what is not payable today:

Payer already holds your coin: A direct Solana Pay or EIP-681 transfer: as fast as the chain (about 1 second on Solana, about 2 seconds on Base, Arbitrum and Optimism), with no route and no route fee. This is the only case we would call instant.
Not payable right now: USDT on BSC and on Tron. NEAR Intents has temporary minimums there of $1,000 and $100 (in that order), so an ordinary payment cannot use them today.

Where it fits

Fits a checkout queue (needs about 2 to 3 seconds): The same coin paid directly on a fast chain. Relay from an Ethereum L2 such as Base or Arbitrum (about 3 to 4 seconds end to end; an L2-to-L2 payment sits at the slow edge).
Fine online and for invoices, not for a queue: Relay from Ethereum (about 12 to 17 seconds). NEAR Intents from Solana, Arbitrum, Base, Optimism or Polygon (about 17 to 47 seconds). A customer on a checkout page can wait for the tick; the person behind them at a till cannot.
Minutes: invoices and orders: Zcash (about 7.5 minutes) and Bitcoin (about 13 minutes) through NEAR Intents. Good for an invoice or an order you ship later, wrong for a counter.
Not payable now: USDT on BSC and Tron, until NEAR Intents lowers its temporary minimums there.
For a physical till: Show the same-coin QR (Solana Pay or EIP-681) and ask the payer to pay it, or to pay from Solana or an L2. The pay link offers the same-coin request to anyone who holds your coin.

What “seconds” means here

These are route estimates, not guarantees, and the payer's own network can be slow when it is busy. Hand over goods that cannot be taken back when the payment shows at your own address, not when a page says so. The same irreversibility that spares you chargebacks also means your payers have no card-style dispute button: a refund on a pay link is a transfer you send yourself.

How it compares with other ways of being paid

As of 14 Oct 2026. Typical figures from public pricing and rulebook pages of card processors, card networks, payment schemes, banks and crypto processors, for a small merchant in the US, the euro area or the UK. They differ by provider, country and ticket size, so read them as the shape of each option, not a quote; check your own provider before relying on one. This page names categories, not companies.

Card payments, online and in person

Speed to your money: Approval takes about 1 to 3 seconds at checkout, but approval is not payment. Funds usually reach the merchant’s bank 1 to 3 business days later (2 business days is a common US default). A new account’s first payout can take 7 to 14 days.
Fees: US list prices for small merchants are about 2.9% + 30¢ online and about 2.6% to 2.7% plus 5¢ to 15¢ in person. On a $25 sale that is roughly 4.1% online and 2.9% to 3.2% in person, before extras for foreign cards (about +1.5%) and currency conversion (about +1%). Across all US card volume the blended cost was lower, about 1.6% in 2025, because it includes cheap debit and large merchants.
Reversal and chargebacks: A cardholder can dispute a payment typically up to about 120 days later, and longer when goods or services are delivered later (one network’s rules cap that at about 540 days from purchase). You usually get 7 to 21 days to answer; a case takes 2 to 3 months; the money is taken back at once while it runs, and many processors add a fee per dispute.
Account and checks: A merchant account with business verification. New or higher-risk merchants can have part of their takings held back as a reserve.
Who holds the money: The processor and the acquiring bank, between approval and payout.

Instant bank transfers

Speed to your money: Seconds, around the clock, in the US (on the two instant-payment networks), the euro area (up to 10 seconds) and the UK (typically seconds). The money is in your bank account.
Fees: Set by the banks. In the euro area an instant transfer may not cost more than a standard one. We could not verify a current US fee schedule.
Reversal and chargebacks: Final once settled. Getting money back depends on the recipient agreeing, or on the bank’s fraud process.
Account and checks: A bank account on both sides, in a country with an instant scheme, so it does not cross borders easily. Per-payment caps apply: $10 million on the US networks (banks can set lower), £1 million in the UK, commonly €100,000 in the euro area.
Who holds the money: Only the banks: from the payer’s bank to yours.

Standard bank transfers

Speed to your money: Mostly the next banking day. In the US about 80% of batch bank-transfer volume settles in one banking day or less, a credit can be dated up to two banking days ahead, and nothing settles on weekends or federal holidays. The UK’s batch scheme takes three working days.
Fees: Set by the bank or processor that collects it.
Reversal and chargebacks: A payment you pull from the payer’s account (a debit) can be returned by their bank within the scheme’s return period, so the money can come back after the goods have gone.
Account and checks: A bank account on both sides; pulling money needs the payer’s authorisation on file.
Who holds the money: The banks, and the processor too if one collects it for you.

International bank wires

Speed to your money: Usually 1 to 5 business days. The international interbank network’s own data (October 2024) says 90% of payments reach the destination bank within an hour, but only about 43% reach the end customer’s account within an hour.
Fees: Large US banks typically charge $25 to $50 to send an international wire and about $15 to receive one. Intermediary banks can take another $20 to $50 that nobody sees in advance, and the exchange rate carries a margin.
Reversal and chargebacks: Hard to reverse once sent. A recall depends on the receiving bank.
Account and checks: Bank accounts on both sides, plus the banks’ own checks on large or unusual transfers.
Who holds the money: The banks in the chain, including intermediaries.

Crypto payment processors that hold funds

Speed to your money: The payment is confirmed in seconds, and your balance with the processor is credited in seconds to a day. Cashing out to a bank adds the normal bank days (next business day to about two).
Fees: Typically 0.5% to 2%. Around 1% to 1.5% is commonly quoted for stablecoin products from large companies, and about 2% + 25¢ at entry volume for a long-established crypto processor. Converting to bank currency can add 0.5% to 1.5%.
Reversal and chargebacks: The payer cannot charge back, and some of these products have no dispute process at all. Refunds are your choice and go back to the payer’s wallet.
Account and checks: A business account with verification: owner IDs, business registration and proof of address are typical, with daily limits that rise as you pass further checks (one processor’s first tier is $10,000 a day). Enterprise onboarding can take about a month.
Who holds the money: The processor, in its own ledger, until you are paid out or withdraw.

Same-coin stablecoin transfer (wallet to wallet)

Speed to your money: As fast as the chain: about 1 second on Solana, about 2 seconds on Base, Arbitrum and Optimism. Ethereum makes a block every 12 seconds and takes about 15 minutes to fully finalise one.
Fees: The network fee only: a fraction of a cent on Solana (the base fee is 0.000005 SOL). On Base the base fee is about $0.002 for a typical transaction at a $2,000 ETH price, plus a small data fee. Ethereum varies with demand.
Reversal and chargebacks: None. A confirmed transfer cannot be pulled back by the sender or a bank.
Account and checks: None. The catch is reach: the payer must already hold your coin on your chain.
Who holds the money: Nobody but you: from the payer’s wallet to yours.

A ZeroFee pay link (70+ chains)

Speed to your money: Seconds on a Relay route from an Ethereum L2 such as Base or Arbitrum (about 3 to 4 seconds end to end); about 17 to 47 seconds on a NEAR Intents route from the fast chains, Solana included; minutes from Bitcoin. Payers who hold your coin use the direct transfer above.
Fees: 0% from ZeroFee. The route’s own cost on top, measured on 14 Oct 2026 against the exchange mid-price: 0.10% to 1.18% on the Relay routes checked at $25; 0.85% to 1.92% on NEAR Intents routes at $25 and 0.62% to 0.90% at $250 (worst case, including a margin of about 0.5% that is refunded if unused). Fixed costs weigh most on small payments.
Reversal and chargebacks: None from us. A payment that cannot complete is refunded to the payer by the route provider. A completed payment cannot be pulled back; refunding a payer is a transfer you send yourself.
Account and checks: None with ZeroFee: no sign-up, no verification, nothing stored. The route providers apply their own minimums and coin lists.
Who holds the money: ZeroFee never does. The route provider (Relay or NEAR Intents) holds it for the seconds to minutes the order takes to fill, and then it is at your own address.

The trade-off in one line

Cards and processors give the payer an undo button and the merchant a chargeback risk, and pay you days later. Pay links and direct transfers give you finality and the money at your own address in seconds on the fast routes, and give the payer no undo. Pick by what your customers expect.

For developers: exact output in the API

A payment is an ordinary quote and swap with amountOut (deliver exactly this much of to) instead of amount. No key, the same endpoints, the same non-custodial flow. Full field lists are in the REST API reference; AI agents get the same through the MCP server.

quote, then create the payment

# 1. Quote: how much ETH on Base pays exactly 25 USDC on Solana?
curl -X POST https://zerofee.si/api/v1/quote \
  -H 'content-type: application/json' \
  -d '{
    "from": { "chain": "base", "token": "native" },
    "to":   { "chain": "sol",  "token": "USDC" },
    "amountOut": "25",
    "refundTo":  "<payer's Base address>",
    "recipient": "<merchant's Solana address>"
  }'
# → routes[0] is the route that asks the payer for LESS (Relay or NEAR Intents)
# → routes[0].amountIn / amountInFormatted = what the payer sends

# 2. Create the payment: a deposit address bound to what the payer agreed to send
curl -X POST https://zerofee.si/api/v1/swap \
  -H 'content-type: application/json' \
  -d '{
    "provider": "<routes[0].provider: relay or near>", "mode": "deposit",
    "from": { "chain": "base", "token": "native" },
    "to":   { "chain": "sol",  "token": "USDC" },
    "amountOut":   "25",
    "maxAmountIn": "<routes[0].maxAmountIn from step 1>",
    "refundTo":  "<payer's Base address>",
    "recipient": "<merchant's Solana address>"
  }'
# → depositAddress, amountFormatted (the exact ETH to send), trackingId, statusUrl, trackingLinks, expiresAt (a NEAR deposit stays open ~72 h)

# 3. Follow it until success, refunded or failed
curl "https://zerofee.si/api/v1/status?provider=<the same provider>&id=<trackingId>"

Give exactly one of amount, amountRaw or amountOut. amountOut is a decimal string in human units of the to token.
The quote's routes carry amountIn (raw) and amountInFormatted: what the payer sends. The output is exactly amountOut.
Pass the route's maxAmountIn (the quoted amountIn plus your slippage, raw units of from) when you create the payment; the payer then sends the fresh, exact amount, never more than that. If the fresh re-quote needs more, the call fails with 409 price_moved, nothing is reserved or built, and the fresh route is in error.details.route so you can ask the payer again.
mode is "deposit", the only mode: the response carries the deposit address the provider issued, and the payer sends to it from any wallet or exchange. There is no sender field and ZeroFee builds nothing for a wallet to sign.
Track with GET /api/v1/status?provider=<provider>&id=<trackingId>, with the same provider the quote chose (relay or near) and the trackingId exactly as /swap returned it, until success, refunded or failed.
Chain names and tickers are forgiving: "solana", "ethereum" and "USDC" (when exactly one listed token matches) all work.

Two helper endpoints

POST /api/v1/paylink makes a pay link from chain, token, amount, to and an optional label and note, and returns the url, a directUri, anyCoin, a ready quoteBody and warnings. Read-only.
POST /api/v1/x402/fund reads an HTTP 402 (x402) requirement and prices an exact-output deposit swap that delivers that asset into your own wallet on its network (with a refundTo on the chain you pay from), so your x402 client can pay it. Read-only; below a route's minimum delivery it funds the minimum plus 3%, and the rest stays in your wallet.

For AI agents

The MCP server has two read-only tools for payments, alongside amountOut on get_quote and maxAmountIn on the swap tools. Each is the same as its REST endpoint above:

create_payment_link makes the same /pay link the app makes, from chain, token (default "native"; "USDC" works), amount, to and an optional label and note. It returns the url, a directUri (Solana Pay or EIP-681), anyCoin, the request, a ready quoteBody and any warnings. Nothing is reserved or stored. A coin NEAR Intents doesn't list can be paid only in that same coin (anyCoin: false), and the response says so. Same as POST /api/v1/paylink.
fund_x402_payment helps an agent pay an HTTP 402 (x402) that asks for an asset it doesn't hold. Give it the 402's body, one accepts entry or the base64 PAYMENT-REQUIRED header (x402 v1 and v2), the agent's own wallet on that network, the coin it holds, and a refundTo address on the chain it pays from. It prices an exact-output swap that delivers exactly the asked amount into that wallet by deposit; the agent creates that swap with create_deposit_swap, sends to the deposit address, then pays the 402 itself with its x402 client. ZeroFee never signs or sends the x402 payment, and testnets are refused. Same as POST /api/v1/x402/fund.

Inputs and the step-by-step flow are in the MCP docs.

How it works

Relay or NEAR Intents, whichever asks the payer for less. A payment asks every provider that can promise an exact amount out, all at once, and offers the one that asks for less: Relay (from a “strict” deposit address) and NEAR Intents. So a payment works for any coin and chain pair either of them lists, not the full set of route providers a normal swap can use. NEAR's confidential mode, where it applies, is a feature of NEAR routes.
A private payment delivers at least the amount. It is the payer's choice (above). In the API it is privacy: "xmr" with amountOut; its routes say delivery: "at_least" and cushionBps, and /swap prices it at exactly your maxAmountIn. The ZK pool and Zcash run in the payer's browser, on the pay page.
Costs. ZeroFee adds 0%. The payer pays the route's own fee (NEAR Intents' is 0.20%, shown in the price), the swap spread and fixed delivery costs, such as creating your token account or gas on your chain. Fixed costs weigh most on small payments. Measured on 14 October 2026 against the exchange mid-price: a $25 payment on a NEAR route cost 0.85–1.92% all-in depending on the coin paid with (worst case, including the margin refunded if unused), and $250 cost 0.62–0.90%. Relay routes were cheaper in every pair checked: 0.10–1.18% at $25.
The margin (NEAR routes only). A NEAR price carries a small exact-output margin, about 0.5%, so you still get the full amount if the price moves a little. Whatever is not used is refunded to the payer, and the price shows the worst case. A Relay route is exact, or refunded: from a deposit address Relay uses a strict address tied to the order, so an underpayment is refunded and an overpayment fills the amount asked and the rest is refunded.
Timing. A NEAR deposit address stays open for about 72 hours, but the price is held only briefly. A deposit that arrives after the price has moved past the payer's slippage is refunded to the payer's refund address, and the merchant receives nothing for it. How long a payment takes to fill is in How fast is it.
Refunds go to the payer. If a payment can't complete, the route provider (Relay or NEAR Intents) returns the funds to the payer's refund address. Refunds of a completed payment are between you and your payer; ZeroFee can't pull money back.
Same-coin payments use the chain's standard transfer request (Solana Pay or EIP-681): no routing, only the network fee.

Check it at your address

Treat a payment as received when you see it at your address, not when a page says so, and for a large one, take a small test payment first. ZeroFee is Super intelligence audited: see Security and the risk disclosure.

Ready? Make your first pay link: pick your coin, enter the amount and your address, and share it.

PreviousFees NextWallet