Cross-chain payments

The customer pays with a token on another chain. NEAR Intents converts it, and exactly the amount due arrives as USDC on Base.

On this page

When it is offered

In live mode only: NEAR Intents has no test networks.
On invoices, payment links and checkout that accept USDC on Base.
While the payment stays open for at least 20 more minutes.
While the profile has Accept other tokens on, in Settings, Accepted assets. It is on by default.

The list comes from NEAR Intents and is read again every 10 minutes. Stablecoins come first.
Popular chains include Ethereum, Arbitrum, Solana, Tron, BNB Chain, Polygon, Optimism and Avalanche.
Left out: Bitcoin, networks that need a memo (Stellar, XRP, TON) and tokens without a price.
Tokens the payment takes directly are paid directly instead.
A token whose minimum is above the amount due is greyed out and can't be picked.

On the pay page they choose Any token, then a chain and a token.
The page shows what to send, the fee and the time before any address.
They enter a refund address on the chain they pay from: their own wallet, not an exchange.
The browser checks NEAR Intents' signed quote, then shows the deposit address.
They send one ordinary transfer. The price holds for 15 minutes; after that the page asks for a new price.

Exactly the amount due arrives as USDC on Base. Your invoice is paid in full.
The customer pays the conversion fee and Base's network fee, shown in USD before paying.
What they send includes a 1% price buffer. The unused part goes back to their refund address, less a refund fee.
When the unused part is not larger than that fee, it may not come back. The page says so before they pay.
Your own fees and the move to your wallet work as for a direct payment.

Extra money, too little money and failed conversions go back to the customer's refund address.
Too little money waits until the quote's deadline, then goes back.
A deposit sent after the price window still converts or goes back.
Forwend holds none of this money: NEAR Intents returns it.
USDC that reaches Base after another token already paid the payment is held for the customer, as for a direct payment.

The customer sees four steps: payment received, converting to USDC, Base confirming, and paid.
Your payments list tags it via NEAR Intents.
Its page shows what the customer sent, the conversion and the USDC on Base, each with its transaction.
Paid still comes only from the USDC that arrives on Base, and the same webhooks follow.

In Settings, Accepted assets, turn off Accept other tokens. New quotes stop; a quote already given still finishes.