Custom token payments: bring your own ERC-20, BEP-20 or TRC-20 token

A token only becomes usable at its activation time, a couple of minutes after approval, and is watched from then on with no backfill — never send anything to a deposit address before it shows as active. Request the token early so review is done before you launch, and ask connect@payaries.com if you have questions.

Custom tokens are requested from your merchant dashboard. You provide where the token lives — the chain and the contract address — and optionally a symbol and a note for the reviewer.

Bitcoin has no tokens. The symbol, name and decimals are read from the chain itself — anything you type for them is ignored, because wrong decimals would silently misprice real money.

The contract is checked on-chain before anything reaches a person. A request is refused straight away if there is no contract at that address or it doesn't expose a readable symbol and decimals, if it's already a built-in asset, or if you already have a request for it.

You're emailed when a request is received, when more information is needed, and when it is approved, declined, disabled or re-enabled. A decline or a disable always includes the reason.

Reviewers look for tokens that are unsafe to hold:

• contracts that impersonate a well-known token — a fake "USDT";
• tokens whose transfers can be blocked or reversed by their issuer;
• fee-on-transfer or rebasing tokens, where the amount received differs from the amount sent;
• contracts that can be upgraded to change behaviour.

A note saying who issues the token, a block explorer link and what it's for makes a decision faster.

• An approval is for your account only. Another merchant who wants the same token submits their own request.
• A token is watched from approval onward with no backfill. Never send anything to a custom token's deposit address before it shows as active — earlier transfers are not scanned for.
• You can have up to five requests awaiting a decision at once.