UsePaid

UsePaid is a cryptocurrency fee bridge that routes creator fees generated by tokens on supported launchpads, including Pump.fun and Pons, to designated X (formerly Twitter) accounts. Its original model paid recipients in dollars through X Money and used part of each fee collection to buy and burn its own token, PAID.^[1]

As of October 24, 2026, X Money payouts are paused. Current project documentation describes a manual-claims process through its portal for eligible fee allocations.^[1] For fees collected at or after September 29, 2026, the documented allocation is 65% to the recipient pool, 10% to the UsePaid treasury, and 25% to PAID buybacks and burns. Collections before that cutoff retain their recorded 80% recipient / 20% protocol split.^[1] The operating model changed after payment issues and a surge in fee volume, while the X Money process remains part of UsePaid's history.^[9]​

Overview

UsePaid describes itself as a bridge that turns a token's creator fees into funds for a recipient.^[1] “Creator fees” are fees a launchpad pays to a token's creator wallet for 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," while 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 deployer, rather than the recipient, initiates the arrangement. After launching a token on a supported venue, the deployer directs its creator fees to the UsePaid treasury and names an X account in the token's description as the intended recipient.^[1] The named recipient does not need to agree, know in advance, or hold a wallet to be named. Under the original X Money process, X Money controlled who could ultimately be paid, and UsePaid did not add another approval step.^[1] X Money payouts are now paused, and eligible allocations are handled through a manual-claims portal. The documented split for fees collected after September 29, 2026, is 65% to the recipient pool, 10% to the treasury, and 25% to PAID buybacks and burns; earlier collections retain their recorded split.^[1] In a September 16, 2026 article, the independent crypto exchange Bitrue described UsePaid as a fee bridge that routes eligible token creator fees to designated X accounts through X Money.^[3]​

Technology and Architecture

UsePaid’s mechanics combine on-chain and off-chain steps. A token first directs 100% of its creator fees to the UsePaid treasury; the fees are then claimed and converted on supported chains. Under the original payout process, the flow ended with dollar payouts through X Money alongside protocol buybacks of PAID.^[1]​^[7] X Money payouts are paused. Current documentation describes manual claims through a portal for eligible fee allocations. Fees collected at or after September 29, 2026, are allocated 65% to the recipient pool, 10% to the treasury, and 25% to PAID buybacks and burns; earlier collections retain their recorded split.^[1] These processes use launchpad-specific fee-routing rules, an indexer that detects eligible tokens and claims, a ledger of fee events and pending buybacks, and integrations with Kraken, deBridge, and X Money.

How It Works

UsePaid's original five-step flow began with a token launch and ended with a payout. First, the deployer permanently directs 100% of the token's creator fees to the UsePaid treasury. Second, the token's description names an X handle. Third, UsePaid's indexer detects the on-chain fee direction and registers the token automatically, without an approval step or queue. Fourth, UsePaid claims the accrued creator fees on a schedule and records each claim against its transaction signature. Under the earlier payout process, the recipient's share was sent in dollars through X Money from a pre-funded float, and a public reply confirmed the payment.^[1] X Money payouts are paused. The automatic X Money flow and its 80/20 split describe the earlier process, not the current route for new claims.^[1]

A token qualifies for the fee bridge only if it directs the entire fee—not a partial share—to UsePaid, and that direction must be permanent.^[1] For portal claims, current documentation says fees may be eligible if both fee collection and credit booking occurred at or after September 27, 2026 11:03:32.440 UTC, regardless of the token's age. The recipient signs in with the X account tied to the fee record, selects an asset available in the portal (SOL or an eligible retained original asset), provides their own Solana wallet, and submits a request for a worker to process.^[1] The portal marks requests as queued, processing, submitted, or confirmed; a payout is complete only when confirmed. A quote-asset claim also requires that the asset was retained and that the claimant provides proof of a finalized sweep.^[1] Earlier balances owed through X Money are separate from manual claims. A displayed balance or request status alone does not establish that a payout is complete.^[1]

Supported Venues

UsePaid supports one live launch venue and describes a second integration as paused, with a third 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 (Robinhood Chain), integrated but not operational. Its fees remain in escrow, and claiming and bridging are paused while Pons is not operational.^[7]
• Four.meme (BNB Chain), being explored; the project states it is not supported and may never be.^[1]

On both venues, the arrangement is intended to end 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, 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] Pons fees continue to accrue in escrow while the venue is not operational; claiming and bridging those fees are paused.^[7]​

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 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 trade. Each claim is recorded in the ledger under its transaction signature, preventing it from being recorded twice. The recipient's share and protocol cut are calculated when the claim is made and are not recalculated afterward. A failed claim creates no obligation and is retried; the fees remain accrued in the meantime.^[1]​^[3] For tokens launched on pons.family, fees continue to accrue in the fee escrow, but claiming and bridging them are paused while pons is not operational.^[7]

UsePaid announced its launch in August 2026, saying that users could pair a pump.fun token with an X handle so that creator fees would be paid to that account through X Money. During the launch period, the project reported that more than $8,000 had been paid, more than $80,000 was queued pending ACH payments, and $34,825 of PAID had been bought back and burned in a day.^[2] These are historical figures reported by the project during its launch period, not current service-status figures.

Under the earlier X Money process, each claim was divided according to a fixed 80/20 split applied at claim time, with no additional fees, discretion, or tiers. Eighty percent, the “recipient share,” was paid in dollars to the named X account through X Money. The remaining 20%, the “protocol cut,” was spent buying and burning PAID.^[1] PAID itself was the sole exception: its fees were not split and were held entirely as protocol treasury.^[1] For collections at or after September 29, 2026 05:29:01.939 UTC, the documented allocation is instead 65% to the recipient pool, 10% to the UsePaid treasury, and 25% to PAID buybacks and burns; earlier collections retain their recorded split.^[1]

Under the former X Money process, payouts were triggered when a recipient's share crossed a series of milestones: $5, then $10, $20, $50, $100, $250, $500, $1,000, and every $1,000 thereafter. Each threshold crossing sent the full balance. Balances below a threshold continued to accumulate, and nothing expired for a resolved recipient.^[1]​^[3] As a result, small amounts of creator fees did not necessarily lead to an immediate payment.^[3] Payments were drawn from a pre-funded X Money balance called the “float,” so they did not need to wait for an off-ramp. UsePaid also publicly replied from its account to confirm each payout, giving its amount and the token it came from.^[1] This automatic, milestone-based process is distinct from the current manual-claims route; X Money payouts remain paused.^[1]

Payment Pause and Manual Claims

Following a major increase in fee volume and reported failures to credit ACH deposits, UsePaid temporarily announced a $750-per-person payout cap. Protos reported that UsePaid cited a $1.54 million 24-hour volume spike, 26 times prior records, in connection with the interim cap. On September 27, 2026, UsePaid said it had paused X Money payouts while addressing payment issues; the project stated that existing balances remained safe.^[9] An independent account of the rollout reported that UsePaid opened a web claims portal on September 28, 2026.^[10] Project documentation describes manual portal claims and keeps earlier X Money balances separate from those claims. It does not document a resumed X Money route.^[1]

Under the documented eligibility rule, both fee collection and credit booking must occur at or after September 27, 2026 11:03:32.440 UTC; eligibility does not depend on token age. A claimant signs in with the X account tied to the fee record, chooses an asset available in the portal—SOL or an eligible retained original asset—provides their own Solana wallet, and submits a request for a worker to process.^[1] A quote-asset claim also requires that the asset was retained and that the claimant provides proof of a finalized sweep.^[1] The portal marks requests as queued, processing, submitted, or confirmed; only confirmation indicates a completed payout. A displayed balance or an earlier request status does not establish that a payout has settled.^[1] The independent report described manual payouts as primarily in SOL, but said its account of whether claims were being paid was unverified at publication.^[10]

X Money and Held Balances

Under the earlier X Money payout process, payments settled into X Money, and recipients needed an account open to receiving payments. X Money was configured on X and available to X Premium members. UsePaid could not open or change a user's X Money account, and it checked whether a handle could 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, so access could not be assumed for every X user globally.^[3] X Money payouts are now paused.^[1]

Under that earlier policy, any X account could be named, whether or not it could yet receive payments, so UsePaid held money for recipients who could not be paid. A balance was held for seven days. If the recipient opened an X Money account during that window, the balance became payable and was sent on the next run. If the account still could not receive payments after seven days, the balance was recycled into the PAID buyback. UsePaid stated that this was the only thing that ever happened to an unclaimed balance.^[1] This seven-day hold and recycling policy describes the earlier automatic X Money process, not the current manual-claims procedure. Current documentation keeps historical X Money balances separate from portal claims, and new X Money payouts remain paused.^[1] Under the earlier arrangement, users who wanted to stop receiving payments had to turn off incoming payments in their own X Money settings, because UsePaid had no opt-out on its site. A user could ask on X to have a handle removed from the site.^[1]​

Cross-Chain Treasury

A token earns fees on the chain where it launched, but PAID has a single market and burn instruction, both on Solana. Protocol cuts earned on other chains therefore have to reach Solana before they can be spent. UsePaid's example is fees earned on Robinhood Chain through pons: they would cross once to Solana at the treasury through the deBridge cross-chain protocol, which the project describes as the only bridge in its path. However, pons is not operational, so its fees remain in the fee escrow rather than being claimed or bridged.^[5]​^[7] Recipient payouts do not use that bridge. Regardless of the fee's originating chain, the recipient's share settles in dollars through X Money from the pre-funded float.^[1]​

Off-Ramp Operations

UsePaid's site shows how claimed Solana fees were converted to dollars and moved into X Money, with the exchange Kraken acting as an intermediary. In representative activity dated September 15, 2026, SOL was sent to a Kraken deposit address, sold on Kraken's SOL/USD market in a market order, and the resulting dollars were transferred by ACH to an X Money checking account through a Plaid transfer.^[4] One recorded sequence sold 25 SOL at an average price of $96.73 per SOL, producing a gross of $2,418.25. Kraken charged $8.46 (0.35%), leaving $2,409.79, which was then sent to X Money via ACH. A parallel sequence sold 25 SOL at an average price of $96.43 per SOL, producing a gross of $2,410.75; after an $8.44 fee, $2,402.31 was transferred onward.^[4] The interface also logs on-ramp deposits, including $309.32 and $232.05 received from Kraken via ACH on September 15, 2026, and $11.02 received on September 14, 2026.^[4]​

The PAID Token

PAID is the token that anchors UsePaid's value-accrual mechanism. It lives on Solana and was issued via pump.fun; after launch it began trading on Solana markets and on exchanges such as Bitrue.^[6]​^[2] In its September 16, 2026 explainer, Bitrue described PAID as newly launched and volatile and advised readers to verify its contract address and current market data before trading.^[3] 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 fee 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 buy-and-burn process uses PAID purchases 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] For earlier fee collections retaining their recorded split, the protocol cut was 20%. For collections under the policy active from September 29, 2026 05:29:01.939 UTC, 25% funds buybacks and burns alongside a separate 10% treasury allocation.^[1] The accounting records each claimed fee as a fee event keyed on the claim's transaction signature, then writes the applicable buyback allocation 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]

Before launch, the project's documentation described PAID as not yet issued and the protocol cut as accruing in the ledger as pending buybacks; it characterized the future first burn as spending a balance that already existed by the time it happened.^[5] That was the documented pre-launch state, not the current status: PAID has since launched on Solana via pump.fun, and UsePaid Analytics reported that 104.57 million PAID had been bought and burned as of October 24, 2026.^[6][11] UsePaid's disclosures state that buybacks depend on fees actually being claimed and do not guarantee a particular price outcome.^[5]​^[3]

UsePaid Analytics reported cumulative total claimed fees of $6,237,189.50, $1,347,453.22 spent on buybacks, and 104.57 million PAID tokens bought and burned in data updated October 24, 2026.^[11] The dashboard notes that 11,294 unpriced fee records are excluded from dollar totals, that recorded totals may be incomplete because a ledger refresh does not prove every chain event was indexed, and that pending allocations are distinct from completed burns.^[11]

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] After launch, PAID began trading on Solana and on centralized exchanges such as Bitrue.^[6] Earlier fee collections retain their recorded split, including the 20% allocation to PAID buybacks and burns. For collections at or after September 29, 2026 05:29:01.939 UTC, 25% funds buybacks and burns, while a separate 10% goes to the UsePaid treasury and 65% to the recipient pool.^[1] Where applicable, deployer rewards are drawn from the recipient pool and are not an additional allocation.^[1] This allocation links PAID’s value-accrual role to the fee-bridge flow described above.^[5] UsePaid's disclosures state that buybacks depend on fees actually being claimed and do not guarantee any particular price outcome.^[5]​

Ecosystem and Interface

UsePaid’s ecosystem centers on launchpads and chains whose creator-fee systems can direct 100% of fees to the protocol’s treasury, with specific supported venues and cross-chain mechanics described in the Technology and Architecture section.^[1]

The main UsePaid web interface exposes a live stream of recent payments, showing for each transfer the recipient’s X handle, token address, timestamp, amount, and transaction identifiers.^[4] It also logs off-ramp operations such as swaps of SOL to USD on Kraken and subsequent ACH transfers into X Money, alongside on-ramp deposits from Kraken into the linked checking account.^[4] On October 13, 2026, the UsePaid X account reported more than $2.5 million sent or claimed across X Money and manual claims: $1,918,920.59 through X Money and $669,540.85 through manual claims.^[2] A separate capital-flow view describes how fees from pump.fun are claimed on a schedule, converted to dollars through Kraken, and split between X Money payouts and PAID buybacks, and explains that pons fees remain in the fee escrow while pons is not operational and that claiming and bridging those fees are paused.^[7] The project’s current documentation also describes a manual-claims portal for eligible fee allocations, with requests processed by a worker and statuses that distinguish a request from a confirmed payout.^[1] UsePaid Analytics reports cumulative claimed-fee and PAID buyback-and-burn figures, subject to its stated coverage and pricing caveats.^[11]

Team and Governance

UsePaid describes itself as an independent product and states that PAID is a value-accrual token only, not a governance token or a fee token.^[8]​^[5] Holding PAID does not change the fee split or control who can launch tokens or who gets paid. It also grants no entitlement to protocol fees or on-chain governance rights.^[5] The protocol presents no on-chain governance mechanism and does not describe its operating decisions as subject to token-holder votes or other PAID-based control structures.^[5]​