At a glance
NEAR on Paymos
Supported assets
- USDT Tether USD
- USDC USD Coin
Confirmation speed
Confirmation depth is network-specific — Paymos tunes it to each chain's finality and shows thresholds where they apply.
Paymos accepts USDT and USDC on NEAR. Each invoice receives a dedicated address, and what arrives is added to the merchant's existing balance for that token rather than to a NEAR-only pot.
Supported assets on NEAR
NEAR accepts USDT and USDC. USD1, DAI and XAUT have no route here. The NEAR token itself is never the invoice asset — the sending wallet only needs enough of it to cover the transfer.
The ticker alone does not identify a route. USDT held on Tron or Ethereum pays a Tron or Ethereum invoice; the NEAR invoice is closed only by a transfer that actually crossed NEAR.
How a NEAR payment works
- The merchant creates an invoice through checkout, Payment Links, POS, a CMS plugin, Low-Code SDK, or REST API.
- The customer selects USDT or USDC on NEAR.
- Paymos assigns a dedicated deterministic address.
- The customer sends the exact displayed amount over NEAR.
- Paymos detects the transfer and waits until it counts the payment as confirmed.
- The confirmed amount joins the merchant's running balance for that token.
HMAC-SHA256-signed webhooks carry each status change to the merchant application, so reconciliation does not depend on watching NEAR directly.
A NEAR payment has no promised completion time
How quickly a NEAR transfer becomes a confirmed payment is not something Paymos fixes in advance, and it is not a figure worth designing a checkout around. The invoice status is what changes when the money is real.
Release the order on the Paymos invoice status, not on the payer's screenshot. A wallet broadcast says the transaction was submitted, nothing more.
NEAR gas and Paymos fees
The payer's wallet pays the network fee in NEAR. It goes to the network, changes with conditions there, and is never quoted here as a fixed amount. A wallet with stablecoins but no NEAR cannot send anything.
Paymos covers the network cost of accepting and consolidating the payment. Standard pricing is 1.0% per settled invoice; Enterprise is 0.3% on request. There is no setup fee, monthly fee, minimum volume, reserve, rolling reserve, or charge for unpaid, expired or cancelled invoices.
Same-asset settlement
USDT stays USDT and USDC stays USDC — no automatic swap into another asset or into fiat, and no charge folded into a rate.
The balance is the point of this page. Turning NEAR on does not open a ledger of its own: USDT taken here and USDT taken on Tron, TON or Plasma are one figure, and the payout network is chosen at withdrawal time from the whitelist.
NEAR is not one of the choices there. It takes payments and cannot be paid out to — a payout destination has to go on the whitelist, and NEAR addresses are not whitelistable. That does not strand anything: what arrives here is USDT or USDC in the same total as every other chain, and it leaves on one of the eleven networks payouts do run on.
Paymos adds no processing commission to withdrawals. A disclosed network fee may apply on the payout route, and it is less than that route costs to run.
When to enable NEAR
NEAR is worth enabling when customers already keep USDT or USDC there and hold NEAR for the fee. It widens the set of wallets that can pay without widening the merchant's accounting.
Do not route a customer by ticker or by a general speed claim. Show the exact network and let the payer use the one where the correct asset and its gas both sit.
Integration and custody controls
Hosted Checkout, Embedded Checkout, Payment Links and Low-Code SDK show the asset, network, amount, address and QR data. H2H REST API, POS and official CMS plugins support other workflows.
Outgoing transactions are signed on isolated infrastructure. Withdrawal whitelisting separately restricts payout destinations.
Frequently asked questions
Which assets can Paymos accept on NEAR?
USDT and USDC. NEAR itself is a gas token here, not a payment asset.
Can USDC from another chain pay a NEAR invoice?
No. The invoice names one network, and a transfer over any other one does not close it.
Does the customer need NEAR?
The sending wallet needs NEAR to pay the fee. That fee is separate from the amount the merchant is credited.
How long does a NEAR payment take?
There is no figure to quote. What you observe moves with the state of the network, which is why the invoice status — not a stopwatch — is the thing to build against.
Does Paymos convert the payment?
No, and it does not split the balance by network either — NEAR receipts land in the same USDT or USDC total as every other chain.
How do I enable NEAR payments?
Enable the supported NEAR assets in your integration. Compare the supported networks or review the USDT and USDC pages.