No-custody payment rail

Send testnet value with clarity.

Review a ROKO Network payment request, verify every detail, and hand the final transaction to your own wallet. Apps can prepare the intent; only you can authorize the transfer.

Review payment request Build a payment link

No custody No seed phrases User-signed only

Testnet beta

No money or real-world value is exchanged here.

This page runs experimental ROKO testnet software. ROKO and CATBOT test tokens have no monetary value. Scammers may copy ROKO pages or messages: use only payments.roko.network, never share a seed phrase or private key, and cancel any wallet prompt you did not initiate.

Review first

This sends testnet tokens

0 ROKO

Recipient: No recipient loaded
Address: Add a recipient address
Token: Native ROKO
Policy: Allowed by registry
Memo: Optional
Source: Manual request

Scam check: verify the recipient, amount, token, and domain before signing. This is beta testnet software and the tokens have no monetary value. ROKO will never ask for your seed phrase, private key, payment, deposit, or remote wallet control.

What happens next

Connect the wallet you want to send from.
Confirm you are on ROKO Network and review the exact asset, amount, and recipient.
Press “Review testnet transfer in wallet.” Your wallet will show the final testnet transaction.
If anything looks different in your wallet, cancel and ask in the official ROKO support channel.

I understand this is beta ROKO testnet software, these tokens have no monetary value, and signing sends only the testnet amount shown from my connected wallet.

Wallet not connected.

Generic flow

Apps prepare requests. Wallets move test tokens.

An app, operator, or user creates a payment request with recipient, amount, asset, token, memo, and source metadata.
The sender opens this page, confirms the testnet-only warning, connects their own wallet, reviews the request, and signs.
The site checks the token against the local ROKO registry before enabling wallet submission.
CatBot can use this same generic flow for tips and gifts without custodying sender funds.

User checklist

Pay only after these match.

1. Domain

Use payments.roko.network. If a link uses another domain, stop and ask official ROKO support.

2. Recipient

Compare the address shown here with the address shown in your wallet. Cancel if they differ.

3. Asset

Check the token policy. Allowed assets can be signed; unlisted or blocked assets stay review-only.

4. Amount

The amount shown is the testnet-token amount your wallet will send. Test tokens have no monetary value, but testnet transactions still cannot be reversed after signing.

5. Wallet preview

Your wallet is the final confirmation screen. If the preview looks different from this page, reject it.

6. Secrets

Never enter a seed phrase, private key, recovery phrase, or remote-control code into this page or chat.

CatBot walkthrough

From a chat command to a wallet signature.

CatBot maps a Telegram username to a registered public address and prepares a CATBOT request. It never receives the sender's wallet keys and never signs the payment.

Open CatBot Official support ROKO Explorer Clowder beta

CATBOT is the amount sent

A request for 10 CATBOT sends exactly 10 CATBOT test tokens to the recipient.

ROKO pays network gas

Your wallet shows a separate, small native ROKO gas estimate. CatBot may separately help eligible new wallets with testnet setup gas.

1 / Register

/wallet 0xYourPublicAddress

Only a public 0x address belongs here. Never send CatBot any wallet secret.

2 / Request

/tip @username 10 Thanks for helping

/pay and /gift use the same no-custody CATBOT flow.

Diagram showing a CatBot command resolving a public recipient address, opening ROKO Payments, and asking the sender's wallet to sign a CATBOT transfer. — CatBot carries public request facts. Your browser wallet controls the transaction and signature.

3 / Verify before connecting

Domain: payments.roko.network
Network: ROKO beta testnet
Chain ID: 52370 / 0xcc92
CATBOT: 0xbbFD…336f9

Annotated comparison of the ROKO Payments request and a browser wallet confirmation, highlighting network, token, recipient, amount, gas, and cancel controls. — The wallet preview is final. Reject it if the chain, token, recipient, or amount differs from this page.

Token registry

Allowed payment assets

The registry is allowlist-first and published as /token-registry.json. Disallowed or unlisted ERC-20 contracts are shown for review but blocked before wallet signing.

Agent-readable site summary

Integration contract

Payment intents may be passed as ordinary query parameters (to, amount, asset, token, memo, recipient, source) or as base64url JSON in intent. Static hosting cannot read an HTTP POST body; opaque short intent IDs require a future API service. Asset selection is governed by /token-registry.json. Native ROKO and approved ERC-20 test tokens can be signed; disallowed or unlisted ERC-20 contracts are blocked. The current network is a beta testnet, and no listed token represents money or real-world value.