Paid $PAID

UsePaid lets a token assign creator-fee proceeds to a named recipient. Its public token pages display the token, recipient, payment destination, and payment history, creating a bridge between on-chain market activity and off-chain payouts.

• The service focuses on payment routing rather than token trading alone.
• Each integrated token can have its own recipient and public payment page.
• PAID is the protocol token supporting the service's economic loop.

For supported third-party tokens, UsePaid describes a split in which most assigned creator-fee proceeds are paid to the named recipient and a smaller service share funds open-market PAID purchases and burns. PAID's own creator fees are handled as protocol treasury revenue, so the exact route should be verified per token rather than assumed universally.

• Recipient identity and payment records are intended to be publicly visible.
• A service share can create PAID buy-and-burn demand.
• Fee routes and percentages must be checked on each integration page.

If more tokens assign creator fees through UsePaid, the protocol can receive more fees to fund PAID purchases and burns. This is a direct activity-to-token path, but it is not a guaranteed yield and does not entitle holders to the underlying recipient payments.

• Value capture depends on integrated-token trading volume.
• Buybacks should be reconciled with public payment and burn records.
• Burns reduce supply but do not guarantee price appreciation.

Creator fees are often opaque or discretionary. UsePaid's model makes the intended beneficiary visible and can align a token narrative with recurring payments to a creator, organisation, or public figure without claiming that the recipient launched the token.

• Public attribution can improve accountability.
• Recipients can benefit without operating token infrastructure themselves.
• Attribution does not necessarily equal endorsement or partnership.

The thesis strengthens with a larger set of active integrations, repeat payment recipients, growing aggregate routed volume, and transparent on-chain evidence of PAID purchases and burns.

• Growth in active fee-generating token integrations.
• Recurring recipient payments rather than isolated events.
• Public reconciliation of fees, buybacks, and burns.

UsePaid depends on third-party tokens maintaining volume and continuing to route fees through the service. Off-chain payout rails can fail or change, recipients may not endorse associated tokens, and a decline in integrations would weaken PAID buyback demand.

• Recipient naming must not be presented as automatic endorsement.
• Off-chain payment delivery introduces operational dependencies.
• The token has no documented revenue or governance entitlement for holders.