UsePaid
UsePaid is a cryptocurrency fee bridge that routes the creator fees generated by tokens on supported launchpads to designated X (formerly Twitter) accounts, paying the recipients in dollars through X Money.[1] The protocol works by having a token point its creator fees at the UsePaid treasury; UsePaid then claims those fees on chain, converts 80% into dollars and pays them to the X account named in the token's description, and spends the remaining 20% buying and burning its own token, PAID.[1]
Overview
UsePaid positions itself as a bridge that turns a token's creator fees into dollars in a recipient's pocket.[1] "Creator fees" are the fees a launchpad pays to a token's creator wallet in respect of trading in that token; UsePaid's model redirects those fees from the deployer to a chosen X user.[1] The project's marketing summarizes the concept as pairing "any pump fun token to a handle to start sending them fiat," and its interface displays a running stream of named payouts to figures such as Elon Musk, Vlad Tenev, Sam Altman, Naval, Garry Tan, and Ansem.[2][4]
The system is designed so that a deployer, rather than the recipient, initiates the arrangement. A deployer launches a token on a supported venue, points its creator fees at the UsePaid treasury, and names an X account in the token's description as the party the fees are for.[1] The named recipient does not need to agree, know in advance, or hold a wallet; control over who may ultimately be paid rests with X Money, and UsePaid does not add a second layer of approval.[1] The independent crypto exchange Bitrue described UsePaid in a 16 September 2026 article as a fee bridge that routes eligible token creator fees to designated X accounts through X Money.[3]
How It Works
UsePaid describes a five-step mechanical flow from token launch to payout. First, a deployer points 100% of a token's creator fees at the UsePaid treasury permanently. Second, the token's description names a handle. Third, the token registers itself automatically when UsePaid's indexer detects the fee direction on chain — there is no approval step and no queue. Fourth, UsePaid claims the accrued creator fees on a schedule and records each claim against its transaction signature. Fifth, the recipient's share is sent through X Money from a pre-funded float, and a public reply confirms the payment.[1]
A token qualifies only if it meets two rules: the whole fee must be directed to UsePaid (100%, not a partial share), and the direction must be permanent.[1] Fee detection is automated rather than polled; the project's interface references detection via a Solana onProgramAccountChange subscription over the pump.fun fees program, filtered on the treasury public key, described as "instant, no polling."[4]
Supported Venues
UsePaid supports two live launch venues and describes a third as under exploration:
- pump.fun (Solana), live. Fees are directed after a token is created, using pump.fun's fee-sharing feature. This is also where the PAID token itself is issued.[1]
- pons.family (Robinhood Chain), live. Fees are directed at creation, by setting UsePaid as the token's fee wallet.[1]
- four.meme (BNB Chain), being explored; the project states it is not supported and may never be.[1]
On both live venues, the arrangement ends with UsePaid as the token's permanent fee recipient, and it cannot be moved afterward.[1] On pump.fun, fees are directed after the coin is created through pump.fun's fee-sharing screen, which lets a creator split fees across up to ten wallets; adding the UsePaid treasury at 100% makes the token appear in its sharing configuration as a shareholder. That configuration stays editable until its authority is revoked, so a token is detected but not payable until the revoke flag is set — revoking the authority makes the direction permanent.[1] On pons.family, the fee wallet is set at launch, and because the contract lets only the current recipient hand the fee wallet on, assigning it to the UsePaid treasury is self-locking: once it is UsePaid's treasury, the deployer cannot take it back.[1]
Naming a Recipient
The X account that gets paid is read from the token's description. UsePaid requires an exact line of the form "Fees to via UsePaid," used anywhere in the description, with the handle bracketed by "Fees to" and "via UsePaid" so that only one reading is possible.[1] If that specific line is missing, UsePaid falls back first to the first handle appearing in the description and then to the X account the token is linked to, both of which the project describes as less reliable.[1] Description length differs by venue: pons.family allows 256 characters, while pump.fun allows considerably more.[1] Several token addresses associated with the system carry a trailing "paid" suffix as a vanity marker.[4]
The documentation lists common reasons a token fails to register, in rough order of likelihood: the sharing configuration gives UsePaid only a partial share rather than the whole fee; on pump.fun the configuration's authority has not yet been revoked; fees are directed to an address that is not the UsePaid treasury; nothing in the description names a recipient and the token is not linked to an X account; or the token is too recent for the scheduled indexer to have seen it.[1]
Fee Claiming and Payouts
Creator fees accrue to the UsePaid treasury as a token trades and are claimed on a schedule rather than per individual trade. Each claim is written to the ledger keyed on its own transaction signature so that a claim cannot be recorded twice, and the recipient's share and protocol cut are computed at claim time and not recalculated afterward. A failed claim creates no obligation and is retried, with the fees remaining accrued in the meantime.[1][3]
Every claim is divided under a fixed 80/20 split applied per claim at claim time, with no additional fees, discretion, or tiers. Eighty percent — the "recipient share" — is paid to the named X account in dollars through X Money, while the 20% "protocol cut" is spent buying PAID and burning it.[1] The sole exception is PAID itself, whose own fees do not split and are held entirely as protocol treasury.[1]
Payouts are triggered by a series of milestones. A recipient's share builds until it crosses $5, then $10, $20, $50, $100, $250, $500, $1,000, and every $1,000 thereafter; each crossing sends the full balance. Balances below a milestone continue to accumulate, and nothing expires for a resolved recipient.[1][3] Because of this structure, small amounts of creator fees do not necessarily result in an immediate payment.[3] When a payout is sent, it draws on a pre-funded X Money balance called the "float," so a payment does not have to wait on an off-ramp, and UsePaid publicly replies from its account to confirm each payout with the amount and the token it came from.[1]
The site's recent payments log records individual transfers with recipient, token address, timestamp, and transaction ID. Examples from 15 September 2026 include $50.00 sent to Nikita Bier (@nikitabier), $10.00 and $5.00 sent to Ashley St. Clair (@stclairashley), $5.00 to rasmr (@rasmr_eth), and $10.00 and $5.00 sent to ☆Chris☆ (@prguitarman).[4]
X Money and Held Balances
Payments settle into X Money, and the only requirement to receive them is an X Money account that is open to receiving. X Money is configured on X and is available to X Premium members; UsePaid cannot open or change a user's X Money account, and it checks whether a handle can be paid before opening a payable balance.[1] As of September 2026, X stated that X Money was rolling out to select users in the United States, meaning access could not be assumed for every X user globally.[3]
Because any X account can be named regardless of whether it can yet receive, UsePaid holds money for recipients who cannot be paid. A held balance stays held for seven days: if the recipient opens an X Money account within that window, the balance becomes payable and is sent on the next run. If seven days pass and the account still cannot receive, the held balance is recycled into the PAID buyback, which UsePaid states is the only thing that ever happens to an unclaimed balance.[1] To stop receiving payments, a user turns off incoming payments in their own X Money settings, since UsePaid provides no opt-out on its own site; removal of a handle from the site can be requested by asking on X.[1]
The PAID Token
PAID is the token that anchors UsePaid's value-accrual mechanism. It lives on Solana and was issued via pump.fun, with the contract address 98kfF7rmsg1QDUEoCqNE7g7M1FdrTt92TEp2CLzypump.[3][2] The project describes PAID strictly as its value-accrual mechanism and explicitly not as a governance token or a fee token. Holding PAID does not change the 80/20 split, does not change who can launch a token, and does not change who gets paid; nothing about the bridge is gated behind it, and holders receive no entitlement to fees, governance, or protocol features.[5][3]
The 20% protocol cut funds a buy-and-burn process. UsePaid buys PAID on the open market from the same market as everyone else, at whatever the price is when it buys, with "no special route and no discount," and sends the purchased tokens to a burn address. Both the buy and the burn occur on chain so the entire path can be checked by anyone, with the stated effect that supply only ever goes down.[5] The accounting works by recording each claimed fee as a fee event keyed on the claim's transaction signature, then writing 20% of that event to the ledger as a pending buyback tied to the originating fee event for later reconciliation. Recycled held balances are recorded separately from protocol-cut buybacks so the two sources can be distinguished rather than blended.[5]
At the time the project's documentation was published, PAID had not yet been issued, and the protocol cut accrued in the ledger as pending buybacks rather than being spent. The project stated that its first burn would not be a promise about future revenue but the spending of a balance that already exists by the time it happens, and its disclosures state that the buyback depends on fees actually being claimed and should not be interpreted as a guaranteed price-support mechanism.[5][3]
Tokenomics
PAID launched on Solana via pump.fun with a total supply of approximately 986,520,430 tokens, a figure that decreases over time as the protocol’s buyback-and-burn mechanism removes tokens from circulation.[6] Every eligible fee UsePaid processes is split 80/20, with 80% paid to the designated X account in dollars through X Money and the remaining 20% used to buy PAID on the open market and burn it, aligning the token’s value-accrual role with the fee-bridge flow described above.[1][5][6] Public sources describing PAID do not disclose any further breakdown of allocations between parties or detailed vesting schedules beyond this overall supply and mechanism.[6]
Cross-Chain Treasury
Because a token earns fees on whatever chain it launched on but PAID has a single market and a single burn instruction, both on Solana, protocol cuts earned on other chains must reach Solana before they can be spent. UsePaid gives the example of fees earned on Robinhood Chain through pons, which cross to Solana at the treasury once, over the deBridge cross-chain protocol, and the project states this is the only bridge anywhere in its path. Recipient payouts never touch that bridge — the recipient's share settles in dollars through X Money from the pre-funded float regardless of which chain the fee came from.[5][1]
Off-Ramp Operations
UsePaid's site exposes the mechanics by which claimed Solana fees are converted to dollars and moved into X Money, using the exchange Kraken as an intermediary. In representative activity dated 15 September 2026, SOL was sent to a Kraken deposit address, swapped on Kraken's SOL/USD market as a market order, and the resulting dollars were transferred to an X Money checking account by ACH through a Plaid transfer.[4] One recorded sequence swapped 25 SOL at an average price of $96.73 per SOL for a gross of $2,418.25, from which Kraken took a fee of $8.46 (0.35%), leaving $2,409.79 that was then sent to X Money via ACH. A parallel sequence swapped 25 SOL at an average of $96.43 per SOL for a gross of $2,410.75, a fee of $8.44, and $2,402.31 transferred onward.[4] The interface also logs on-ramp deposits, including $309.32 and $232.05 received from Kraken via ACH on 15 September 2026, and $11.02 received on 14 September 2026.[4]
Developments
UsePaid's presence on X was established in August 2026, and its pinned announcement declared the project "officially live," inviting users to pair a pump.fun token to any X handle so that creator fees would be paid to that account in dollars through X Money.[2] Shortly after launch, the account reported that more than $8,000 had been paid to X Money users and more than $80,000 was queued to be sent as ACH payments came through, describing the period as "Day 1, Block Chain 1."[2] The account also stated that $34,825 of PAID had been "bought back and burnt" in a single day and praised X Money, noting that its ACH settlement occurred "in under a few hours."[2] These figures are the account's own statements. On 16 September 2026, Bitrue published an explainer on the project, advising that because PAID is newly launched and volatile, traders should verify its contract address and current market data before trading.[3]
