How IDPay works
IDPay is a fee bridge. A token points its creator fees at us, we claim them on chain, and 80% is paid out automatically to the WeChat ID it named, as USDT on BNB Chain, ready to cash out to WeChat Pay. Nobody has to sign up to be named.
Contents
- Overview
- Supported venue
- Directing fees
- Naming the recipient
- The 80/20 split
- How claims work
- Getting your fees
- WeChat Pay setup
- Held balances
- The public record
- The treasury
- The protocol share
- Stopping payments
- If a token is not registering
- Glossary
1Overview
IDPay turns a token's creator fees into yuan in someone's WeChat balance. A deployer launches a tax token on Flap and points its fees at the IDPay treasury. The token's description names a WeChat ID, and that ID is who the fees are for. Everything between the two is mechanical.
Fees accrue to the treasury as the token trades, IDPay records each claim, the recipient share is converted to yuan and paid through WeChat Pay, and the protocol keeps the rest. Every step is recorded against the claim that produced it, and every payout is published with its transfer reference.
The recipient is not asked to do anything first. There is no account to make and no wallet to connect. A WeChat ID can be named by a token its owner has never heard of, and the balance waits for them.
- A token directs its fees. The deployer sets the IDPay treasury as the token's beneficiary with 100% of the marketing share, permanently. See section 3.
- The description names a WeChat ID. One line says who the fees belong to. See section 4.
- The token registers itself. The indexer sees the beneficiary on chain and registers the token. There is no approval step.
- Fees are claimed. Flap forwards the marketing share to the treasury; IDPay records each increase as a claim against the token.
- The recipient is paid in yuan. The recipient share is sent through WeChat Pay from a pre-funded float, and the payment is published.
2Supported venue
| Venue | Chain | Status | How fees are directed |
|---|---|---|---|
| Flap (flap.sh) | BNB Chain | Live | At creation, as the tax token's beneficiary |
| four.meme | BNB Chain | Not supported | Creator fees there cannot be redirected at creation |
IDPay launches Flap Tax Token V3 tokens (tokenVersion = 6). Standard non-tax tokens have no creator fee to route and are not supported.
3Directing fees
A Flap tax token has one beneficiary, set in the launch transaction, that receives the marketing share of every tax collected. Two rules hold. It has to be the whole marketing share (mktBps = 10000), because a partial share would mean the payout we publish is a fraction of what the token earned with no way for the recipient to tell which. And it has to be permanent: Flap's tax token contracts have no setter for the beneficiary, so the assignment made at creation is its own lock.
| When | At creation, in Portal.newTokenV6 |
|---|---|
| What we watch | VanityTokenCreated(token, creator, beneficiary) and the Tax Token Helper's marketingWallet |
| Made permanent by | The assignment itself. Nobody can move it, including us |
The launch page does all of this for you. If you launch through Flap's own site or a bot, set the beneficiary to the treasury shown on the launch page, mktBps to 10000, and the other distribution fields to 0.
4Naming the recipient
The WeChat ID that gets paid is read from the token's description. Put this line in it, with the WeChat ID you want paid:
Fees to WeChat: your_wechat_id via IDPay
Use it exactly, anywhere in the description. Write whatever else you like around it. A WeChat ID (微信号) is 6 to 20 characters, starts with a letter, and may contain letters, digits, underscores and hyphens. It is the ID a person sets in WeChat → Me → Profile, not their display name and not a phone number.
The wording matters. A description can mention several accounts, and without a fixed line there is no way to tell which one is meant to be paid. "Fees to WeChat" and "via IDPay" bracket the ID so only one reading is possible. If the line is missing, the token is registered as unnamed: its fees still accrue to a balance for the token, and the operator can assign the recipient once the deployer says who it was for.
5The 80/20 split
Every claim divides the same way. There is no discretion in it, no schedule to negotiate, and no tier that changes it.
| To the recipient | 80%, quoted in yuan and paid as USDT on BNB Chain to the wallet linked to the WeChat ID |
|---|---|
| Protocol share | 20%, held in the treasury; it funds the float, the conversions and the infrastructure |
| Applied | Per claim, at claim time, at that moment's BNB/CNY rate |
| Fees we add | None. Flap's own protocol rate is taken before the tax reaches the treasury |
6How claims work
Creator fees do not arrive continuously. On the bonding curve the tax is paid in BNB with every trade and forwarded to the tax processor; after graduation to PancakeSwap the tax accrues in the token itself and is liquidated to BNB when it crosses a threshold. Either way the marketing share reaches the treasury, and the helper contract's totalQuoteSentToMarketing for the token goes up.
Each increase is written to the ledger as a claim, keyed on the token and the amount, with the BNB/CNY rate at that moment. The recipient share and the protocol cut are both computed then, and neither is recalculated afterwards. Claims for tokens quoted in a stablecoin are valued at par; claims in other quote tokens are recorded but marked unpriced until the operator values them.
Payout milestones
Payouts land at milestones. A recipient's share builds until it crosses ¥50, then ¥100, ¥200, ¥500, ¥1,000, ¥2,500, ¥5,000, ¥10,000, and every ¥10,000 after. Each crossing sends the full balance. Balances below a milestone keep building; nothing expires for a linked recipient. If the WeChat ID cannot receive yet, the balance is held. See section 9.
7Getting your fees
If a token has named your WeChat ID, the money is already yours. It is sent once the balance crosses a milestone and your WeChat ID is linked.
- A token names your WeChat ID. Somebody launches a token and points its creator fees at you.
- Fees accrue and are claimed. Trading generates tax. Flap forwards it to the treasury; we record it.
- A payout wallet is set at launch. The launcher names your WeChat ID and a BNB Chain wallet in the same form. If they know your wallet, it is yours from the first payout. If they used their own, they hand it to you with one signature on the payout wallet page.
- 80% is paid to you, automatically. The treasury sends USDT to the payout wallet on chain the moment the balance crosses a milestone. Cash it out to WeChat Pay or Alipay whenever you like through Binance P2P, where yuan buyers pay your WeChat directly.
You are not required to acknowledge anything or agree to anything. Receiving a payment does not make you a customer of IDPay or a promoter of the token that named you.
8Wallet and cash-out
Payouts are on-chain transfers of USDT on BNB Chain, so the only requirement on your side is a wallet address on BNB Chain: MetaMask, Binance Wallet, OKX, or the deposit address of your Binance account. No identity check, no bank, no merchant account, on either side.
Turning USDT into yuan in your WeChat balance is one step you do yourself: sell it on Binance P2P (or any Chinese OTC desk) and choose WeChat Pay or Alipay as the way the buyer pays you. It is the most common way people in China move between stablecoins and yuan, and IDPay never touches that leg.
The payout wallet is the Wallet: 0x… line the launch form writes into the token description. It can be moved, at any time, by a signature from the wallet that currently receives. That is the only control, and it is why nobody at IDPay can redirect anyone's fees: there is no approval step and no operator in the loop.
9Held balances
Any WeChat ID can be named, linked or not. Where an ID cannot yet receive, the money is not lost and it is not sent anywhere else. It is held for them.
| Who can be named | Any WeChat ID |
|---|---|
| Held for | 30 days from the first payout that could not be sent |
| Once a payout wallet exists | Paid on the next run, automatically |
| If they never do | Recycled into the protocol treasury |
10The public record
Every payout is published on the payments page with the WeChat ID, the amount, the tokens it came from and the BNB Chain transaction hash, which anyone can verify on BscScan. We do this so the recipient can find out at all. Most were not asked before their ID was named, so the payment is usually the first they hear of it, and the record is what they can check it against.
11The treasury
The treasury is one address on BNB Chain. Every registered token's marketing share lands there. Its balance is shown live on the payments page; conversions out of it into yuan are recorded on the capital flow page. Payouts do not wait on a conversion: the recipient share settles from a pre-funded WeChat Pay float, and the float is topped up in batches.
12The protocol share
The protocol cut is held in the treasury. It pays for the float, the conversions, the RPC and the servers. It gates nothing: holding anything does not change the split, does not change who can launch, and does not change who gets paid.
13Stopping payments
There is no opt-out switch on this site, deliberately. Who may pay you is a setting on your WeChat account. If your WeChat ID is not linked, nothing is ever sent, and after the hold period the balance is recycled. If you would also prefer your WeChat ID not to appear on this site, message the IDPay account on WeChat and it is removed.
14If a token is not registering
Registration is automatic, so a token that has not appeared has failed one of a short list of conditions, in rough order of how often each is the cause:
| Not a tax token | Standard Flap tokens have no beneficiary. Only Tax Token V3 (address ends in 7777) can direct fees. |
|---|---|
| Wrong beneficiary | The beneficiary is an address that is not the IDPay treasury. Check it against the launch page. |
| Partial share | mktBps is below 10000. The token is detected but flagged, because its claims would not reflect what it earned. |
| No WeChat ID or wallet in the description | The launch form always writes both lines. A token launched elsewhere without them registers as unnamed, its share is held, and after 30 days it is recycled into the protocol. |
| Too recent | The indexer reads the chain every few seconds. A token created moments ago has not been seen yet. The launch page registers immediately; the register tab does the same for a token launched elsewhere. |
15Glossary
| Creator fees | The marketing share of a Flap tax token's trading tax, paid to the token's beneficiary. |
|---|---|
| Beneficiary | Flap's field for the address that receives the marketing share. Set at creation, never movable. |
| Claim | An increase in the tax processor's cumulative payout to the treasury for one token, recorded in the ledger. |
| Recipient share | 80% of a claim, payable to the named WeChat ID. |
| Protocol share | 20% of a claim, held in the treasury. |
| Held balance | A recipient share recorded but not yet payable, because the WeChat ID is not linked. Held 30 days. |
| Float | The pre-funded WeChat Pay merchant balance payouts are sent from, so a payment does not wait on a conversion. |
| Treasury | The BNB Chain address a token's creator fees are directed to. |
| Payout wallet | The BNB Chain address a WeChat ID's share is sent to. Set at launch; movable only by a signature from the wallet that currently receives. |