A launchpad with one
extra field: who gets paid.
Launch a token and choose one LinkedIn or GitHub profile. 90% of the revenue received by its vault or locked revenue allocation is assigned to the recipient and waits until they claim it.
Fees for builders, not noise.
PaidIn routes eligible creator revenue to a real builder you name by a LinkedIn or GitHub profile: a founder, the engineer behind a tool you use, an open-source maintainer or a member of a team that shipped something useful. Four.meme token tax and pump.fun creator fees provide the revenue through their respective protocols.
They do not need to know about it in advance, have a wallet, or sign up. Eligible revenue builds up as the launchpad collects and distributes it. When they are ready, they connect LinkedIn or GitHub, prove the profile is theirs, and claim to their own wallet, with PaidIn sponsoring eligible payouts.
One field
A normal launch: name, ticker, image. Then: who gets paid — one LinkedIn or GitHub username or profile link.
One recipient
Choose one LinkedIn or GitHub profile to receive the recipient share of creator fees.
Locked allocation
Confirm the revenue lock at launch. The recorded beneficiary and allocation cannot be edited; the same recipient can change their payout wallet through the binding flow.
Claim when ready
Collected revenue waits for the recipient to verify their LinkedIn or GitHub profile, bind a wallet and claim an eligible amount.
Launch in four moves.
Pick a network
Solana through pump.fun (SOL or USDC), or new BNB Chain tokens through Four.meme when enabled (BNB revenue). Existing tokens keep their vaults.
Make the token
Name, ticker, image, a description and links. A line saying where the fees go is added to the description.
Name who gets paid
Paste a LinkedIn or GitHub username or profile link. The bar shows the recipient’s share and PaidIn’s.
Approve the launch
Review the allocation, then approve the required launch transactions in your own wallet. Confirm the token and its revenue lock before leaving the launch flow.
PaidIn validates and simulates the prepared launch before asking you to approve its transactions. Four.meme first requires a wallet login message. Preparation can detect invalid details, balance problems or network failures, but simulation does not guarantee execution. Your wallet pays the launch and any first buy.
Where every fee goes.
The whole creator fee is routed — there is no buyback, burn, holder reward or launcher cut on PaidIn. The launcher earns nothing from the fee by design: you launch for someone else.
An example
A Four.meme token names one recipient with a 90% allocation. If its vault receives 0.1 BNB in tax revenue, 0.09 BNB belongs to that recipient and 0.01 BNB to PaidIn. Claim eligibility also depends on the payout wallet and minimum amount. These percentages apply to received revenue, not trading volume.
Two launchpads, one promise.
| Solana · pump.fun | BNB Chain · Four.meme | |
|---|---|---|
| Trade in | SOL or USDC | BNB |
| Revenue | pump.fun's creator fee (set by pump.fun) | The selected trade tax; Four.meme trading fees also apply |
| Where the allocation lives | pump.fun fee sharing, locked by PaidIn right after launch | A PaidIn vault locked before token creation |
| Fees arrive | In the trading asset, when distributed (PaidIn does this on its rounds and at every claim) | When Four.meme dispatches founder revenue; received WBNB is unwrapped to BNB on claim |
| After graduation | Keeps paying on PumpSwap | Keeps paying on PancakeSwap (the tax is part of the token) |
| Where a share waits | The person's PaidIn escrow on Solana | Inside the token's vault |
Existing Flap and Clanker tokens retain their original vaults. Other network integrations are offered only when their launch and payout flow has been verified.
Named on a token? Here is how you get paid.
Connect your profile
Sign in with LinkedIn or GitHub on Payday using the account named as the recipient. GitHub access uses public account data; private repositories are not requested.
Verify ownership
GitHub ownership is matched to the stable account ID. For LinkedIn, submit your profile URL and temporarily put the displayed code in your headline or About section for review.
Bind a wallet
Sign one message with your wallet on each network you are paid on — an EVM wallet for BNB Chain, a Solana wallet for Solana. No fee: PaidIn pays the gas.
Claim
Press Claim. Your share is paid from each vault (or your Solana escrow) straight to your bound wallet. Come back whenever more has built up.
- Nothing expires. Unclaimed fees are never swept to anyone; they wait for you indefinitely.
- A binding covers its registry. EVM tokens using the same identity registry share your payout destination. Older integrations may use another registry. Solana has its own wallet binding.
- Wallet changes have a waiting period. EVM changes use the delay configured in the selected registry; Solana changes wait 24 hours. Check the displayed effective time before claiming.
- Your own choice to give back. If you want, you can thank a token's community — PaidIn plans a tool for that — but you never have to.
What is locked, and who holds what.
Locked at launch
Who gets paid and each share. On BNB Chain the allocation is written into the vault contract; on Solana pump.fun's fee sharing is set and then locked so even its creator can no longer edit it.
BNB Chain: held by a contract
Fees sit in the token's vault, which has no owner. It pays the recipient's allocation to the wallet bound to their verified profile reference. Anyone can trigger a payout; it goes to the effective bound wallet.
Solana: held in your escrow
The recipient's revenue lands in an escrow address derived for them. PaidIn's server holds that escrow's key and sends eligible claims to the bound wallet. This route depends on PaidIn's escrow operations and key security.
What PaidIn can do
Verify who owns a profile, approve or reject that match, manage binding authorization and emergency controls, and sponsor operations. It cannot edit a locked EVM vault's beneficiaries or allocations. Registry administration and Solana escrow operations remain trust dependencies; see the detailed docs.
What it costs.
| Who | What | Roughly |
|---|---|---|
| Launcher, BNB Chain | Vault/token network fees, any protocol charge and optional first buy | Shown in the launch preview and wallet |
| Launcher, Solana | pump.fun's account rent, network fees and the one-time cost of locking the allocation | Estimate shown in the launch preview; network costs may change |
| Traders | Four.meme token tax and market fees, or pump.fun/PumpSwap trading and creator fees | Check the token and trade preview |
| Recipient | Sponsored binding and eligible claims; EVM cancellation can require wallet gas | Claim minimums apply |
| PaidIn | 10% of the creator fee | Locked in the same allocation |
Questions people ask.
Do the people I name have to agree first?
No. Their share simply waits. If they never claim it, it stays where it is — PaidIn does not take it. People can also opt out of being named on new launches.
Can I name myself?
You can name your own public LinkedIn profile or individual GitHub account, then verify ownership like any other recipient. PaidIn is designed to support builders.
Can the recipient or allocation be changed later?
No. That is the point: holders and the people named can trust that the fee goes where the launch page says, forever.
What if someone names a profile that is not theirs to name?
Being named does not mean endorsement, and that is stated on every token. People can block new launches from naming them and hide from discovery.
What if my wallet shows a security alert?
Cancel and inspect the alert. The launch dialog shows the expected destination. A successful simulation or official protocol address does not clear a wallet alert.
Who pays the gas to claim?
PaidIn. A payout only goes through when it is worth more than its gas, so very small amounts keep building up until they are.
Is PaidIn affiliated with LinkedIn, GitHub, pump.fun or Four.meme?
No. PaidIn verifies profile ownership through LinkedIn or GitHub and integrates launchpad protocols.