Terms of use

1.The service

UsePaid collects creator fees directed to its accounts, records recipient and deployer allocations under its distribution policy, and provides a request path for eligible manual distributions of native SOL or supported quote assets in their original form. Fee ownership and payment discretion are described in clause 9; claim timing and historical balances are addressed in clause 10. The site also provides token-launch tools and displays token, account and payment records.

UsePaid does not operate the underlying launchpad or trading market and does not provide financial, investment, legal or tax advice. It does not custody your personal wallet and never asks for its private key or seed phrase. Creator fees collected into UsePaid accounts are held and processed by UsePaid; they are not held in your personal wallet.

Token registration does not establish UsePaid approval of a token or its named recipient. Clauses 7, 8 and 11 describe deployer responsibilities and prohibited uses.

2.The operator

UsePaid is the operator of this site and the fee-processing service, referred to as “we” and “us.” UsePaid owns the treasury, Kraken account and historical X Money sender account, according to the operator’s supplied account information.

The operator is UsePaid. Contact and legal notices are described in clause 21. The governing-law provision in clause 19 does not state a place of incorporation.

3.Definitions

Deployer

The person who launches a token and directs its creator fees to UsePaid.

Recipient

The account identified for a potential distribution, including a named recipient or a deployer with a recorded reward allocation. Identification alone does not establish ownership of UsePaid’s fees.

Creator fees

Fees paid by the underlying launchpad or protocol in connection with trading in a token.

Fee collection

UsePaid’s on-chain collection of creator fees. This is separate from a recipient requesting a withdrawal.

Recipient claim

A request to transfer an eligible SOL or supported original quote-asset balance to a Solana wallet.

Activation time

The frozen manual-claim cutoff recorded in the database: 27 September 2026 at 11:03:32.440 UTC (6:03:32.440 a.m. CDT).

Quote retention anchor

The separate recorded time from which supported non-SOL fee assets may be retained in kind: 27 September 2026 at 23:57:08.692 UTC. Quote-asset claims also require a matched, finalized treasury sweep.

Historical balance

An earlier X Money balance or a credit sourced from a pre-activation collection; excluded from manual claims.

Fee-time review balance

A recorded credit whose fee source collection or credit booking falls before the activation cutoff. It is excluded from manual claims.

Eligible claim balance

A recorded SOL or supported original quote-asset allocation that meets the source, identity, sweep and accounting checks in clause 10 and is available for a distribution request, subject to clauses 9 and 10.

Held balance

An allocation withheld for review or a restriction. A held or reserved amount is not available for a second withdrawal.

Provider claim window

A third-party deadline for accepting a previously sent X Money payment. It is distinct from UsePaid’s collection cutoff and manual claim eligibility.

4.Acceptance

These terms apply to people who actively use UsePaid, launch a token through its tools, direct creator fees to its accounts, or request a recipient claim. Acceptance of an effective revision must be associated with the version presented for that action.

Being named by someone else, appearing in public records, or receiving an unsolicited payment does not itself constitute acceptance. A recipient who chooses to use the claim service is an active user for that use; clause 6 distinguishes these situations.

5.Eligibility

To actively use UsePaid you must be at least 18 and able to form a binding contract. You must comply with applicable sanctions and must not use the service for a sanctioned or restricted person or where such use is unlawful. Applicable restrictions may change; see the current OFAC sanctions programs and lists. Being passively named by a token does not make these representations on your behalf.

6.If a token names you

A token may name an X account without its owner’s knowledge or involvement. Naming an account, collecting fees attributed to it, or displaying its data does not imply consent, partnership, promotion or endorsement by that account holder.

You have no obligation to participate merely because a token names you. If you choose to request a manual claim, you must sign in with the account identified for that allocation and review the destination wallet and claim details. Owning a wallet alone does not authorize a claim against another account’s allocation.

You may request removal and opt-out under clause 13. Receiving funds does not make you a sponsor or endorser of a token.

7.If you launch a token

You are responsible for your token, its metadata, artwork and the lawfulness of its launch. Directing fees to UsePaid does not make UsePaid or the named recipient the issuer, promoter or sponsor of your token.

You must make the representations in clause 8 and comply with clause 11. Registration is not an endorsement or a guarantee that fees will be collected or paid. UsePaid may review, decline or remove a listing under clause 12.

8.Deployer representations

By directing a token's creator fees to the UsePaid treasury, you represent and warrant that: you have the lawful right to create the token and to direct its fees; the token's name, description, and artwork are lawful and do not infringe any third party's rights; you are not a sanctioned or restricted person and are not acting for one; you named the recipient handle in good faith and not to harass its owner or to imply endorsement; you will not claim any affiliation between the token and UsePaid, X, or any launchpad beyond what is factually true; you are complying with the terms of the launchpad the token was created on; and the information you provide is accurate.

9.Payments and the split

Fee ownership and discretionary distributions. For fees directed to UsePaid under this revision, and to the extent the directing party has authority to transfer them and applicable law permits, all creator fees received in UsePaid’s treasury are owned by UsePaid. Receipt in the treasury does not, by itself, create a debt or an obligation to pay a named recipient or deployer. UsePaid chooses whether to offer and make distributions under this program and is not obligated to distribute those fees merely because an account is named or an estimated allocation is displayed. Displayed allocations describe the program’s distribution calculation; they do not, by themselves, transfer ownership or guarantee payment.

Existing rights and mandatory law. This ownership and discretion provision applies prospectively. It does not cancel obligations arising under an earlier accepted version, a separate binding agreement or applicable law; recharacterize historical X Money balances; or undo completed payments. Funds legally belonging to another person remain subject to that person’s rights and any applicable reporting or delivery duties. The 14-day program window is not a declaration that property is legally abandoned.

For standard creator fees collected at or after the recorded activation time, 65% is allocated to the recipient pool, 10% to UsePaid treasury, and 25% to buybacks and burns, subject to the execution-cost policy below. The boundary is the fee collection timestamp, not token age, trade time, credit-booking time or claim-request time. Earlier collections keep their original 80% beneficiary / 20% protocol split even if processed later. Existing allocations and historical X Money balances are not recalculated.

A recorded deployer reward is deducted from the recipient pool, not added on top. Its existing basis is preserved: a reward stated as a percentage of total creator fees remains on that basis; a reward stated as a percentage of the recipient pool applies to that pool. For example, a 10% total-fee deployer reward under the new policy leaves 55% for the named recipient, 10% for the deployer, 10% for treasury and 25% for buybacks and burns. Each fee source records its split. Under the new policy, integer rounding remainders stay in treasury. The separate PAID-token treasury-fee policy below is unchanged.

For supported quote fees retained after the quote retention anchor, each recorded recipient or deployer allocation remains in that original quote asset while available, reserved or held. The collection-time buyback portion (25% after activation; 20% for earlier collections) remains allocated separately to $PAID buyback and burn under the policy below; protocol actions do not spend protected recipient or deployer allocations. Native SOL credits remain SOL, and any separate verified conversion proceeds follow their recorded allocation. These accounting protections do not override the ownership, existing-rights or expiry provisions in this clause and clause 10.

Historical dollar valuations and payment totals are reporting records, not promises to convert those amounts at today’s SOL price. Network costs, conversion execution and integer rounding can affect a recorded SOL amount.

An allocation or pending buyback is not a completed purchase or burn. Clause 13 explains opt-out treatment. Past recycling records are not rewritten by this revision.

10.Payouts and unclaimed payments

Current status. X Money payouts are paused. SOL claims can be requested manually through the claim portal when both fee-source collection and credit booking meet the activation cutoff, subject to recipient eligibility, available funding and send controls. Token age does not determine eligibility. Supported original quote-asset claims are available when shown in the portal and permitted by their separate send controls. Earlier X Money balances remain separate. The following rules describe claim eligibility and processing.

Fee-time boundary. A fee source must be collected and its corresponding credit booked both at or after the activation cutoff in clause 3. This cutoff applies regardless of token age; token creation timing is not a separate eligibility requirement. Supported non-SOL claims have an additional source-retention requirement: the fee source must be collected after the quote retention anchor, matched to an exact finalized treasury sweep and allocated under the recorded recipient/deployer split. A pre-activation collection remains historical even if its credit is booked later.

Claimable assets. An eligible native SOL credit uses its recorded lamport allocation. An eligible supported quote-asset credit uses the recipient’s or deployer’s exact recorded share in that original asset; a conversion to SOL is not required for that retained balance. The recorded collection-time buyback portion continues under the buyback-and-burn allocation in clause 9 and is processed separately. Unsupported assets, unmatched or unverified sweeps, fee-time review balances, other review holds, identity or attribution issues, opted-out accounts, amounts released after expiry, recycled amounts and previously reserved or settled allocations are excluded.

Request and destination. Sign in with the account identified for the allocation, review each eligible asset and its exact amount, enter a Solana wallet you control and confirm the address. A request covers one asset at a time. Claims are queued for a worker; only one open request per account is permitted. Available treasury funding and the service’s send controls must permit processing. Incorrect addresses may result in irreversible loss.

Transaction status. Queued, processing and submitted requests are not completed payments. A transfer settles only after a successful finalized chain receipt matches its recorded destination and amount. An unknown outcome stays reserved for review; inspect the existing request rather than attempting a replacement withdrawal. An authoritative chain failure can release its reservation.

Historical funds. Earlier X Money balances remain separate. They are not automatically converted, written off or made claimable in SOL or quote assets. Quote-fee sources before the quote retention anchor, and sources that miss the fee-time cutoff or lack a matched sweep, remain recorded or held for review under their evidence state. Recipient and deployer quote-asset allocations stay protected from protocol buybacks. Any future migration or settlement route requires a separate decision and reconciliation; no completion date or route is promised. Accounting and spending controls separate these allocations in a shared treasury; this does not mean separate custody wallets or guaranteed solvency.

Previously sent X Money payments. Any provider acceptance deadline is governed by that provider’s actual policy and record. A pending payment is not proof of recipient acceptance or settlement.

14-day manual-claim window. Each eligible SOL or supported original quote-asset allocation has its own claim window of 14 days (336 hours), starting when that allocation first becomes available to claim. Later allocations receive their own window and do not reset an earlier allocation’s clock. Allocations already available when this policy is introduced receive a full 14 days after notice of the new policy; no earlier time is counted against them. An allocation that becomes available later starts its clock at that later time. This program window is separate from any X Money provider deadline.

Unclaimed allocations after the window. Subject to the existing-rights and mandatory-law protections in clause 9, an allocation for which no valid claim request is received within its window will be removed from the manual-claim program and allocated 100% to UsePaid’s treasury wallet. Assets already in that wallet will be retained and reclassified in the accounting records; assets held elsewhere will be transferred to it. No additional on-chain transfer is implied when the assets are already in the treasury.

Timely requests, holds and notice. A valid request received before the deadline preserves its covered allocation while processing, even if final settlement occurs later. Reserved, submitted or uncertain transfers cannot be released to treasury while their outcome is unresolved. A period when UsePaid’s claim service or send controls prevent a valid request from being processed does not count toward the window. Review and legal holds remain protected while being resolved under clauses 12 and 14. UsePaid must retain evidence of availability, notice, applicable deadlines and any extensions before releasing an allocation; if that evidence is missing, the allocation remains protected. Existing enforceable rights are not extinguished merely by posting this revision.

Claims through X. The proposed @UsePaid claim fees "SOLANA_WALLET" command is planned and is not implemented as an available claim path.

11.Prohibited uses

You may not use UsePaid, directly or through a token, to launder money or move proceeds of crime, to evade sanctions, to commit fraud, to engage in manipulative or deceptive trading practices, to impersonate any person, or to do anything unlawful. You may not name a handle in order to harass, defame, or extort its owner, or to imply that its owner endorses, sponsors, or is involved with a token or with UsePaid. You may not use a token's name, description, or artwork in a way that infringes anyone's intellectual property or publicity rights. You may not interfere with the service or attempt to circumvent a removal, a do-not-pay listing, or any other decision made under these Terms, including by relaunching a token for a handle that has opted out.

12.Reserved rights

We may refuse, delay, or decline to register a token, to display a handle, or to make a payout, and we may delist a token or suspend any part of the service, where we believe in good faith that doing so is required by law, by sanctions, by a court or government order, or by an action of X, X Money, a launchpad, an exchange, or a bank, or that a token, a handle, or a payout involves fraud, abuse, or a breach of these Terms. An amount withheld under this section is held, and is paid or otherwise resolved when the reason for withholding is resolved. We are not liable for a refusal, delay, or withholding made in good faith under this section.

13.Removal and do-not-pay

You may ask that your account be removed from public listings and blocked from payments. Use the opt-out flow, contact @UsePaid on X from the account concerned, or send reasonable proof of account control to admin@usepaid.app. We aim to honor removal within seven days.

An effective opt-out blocks further payouts and hides the account’s listings. It does not undo a completed transfer or delete on-chain records. It is not a promise that the underlying protocol stops earning or collecting fees.

In-flight, reserved, settled or uncertain transfers are preserved until their outcome is resolved. A payment previously sent through X Money follows clause 10.

14.Taxes

You are responsible for your own taxes. Amounts received through UsePaid may be taxable to the recipient, and directing a token's fees may have tax consequences for the deployer; what applies depends on your circumstances and your jurisdiction, and UsePaid does not characterize any payment for tax purposes. UsePaid does not provide tax advice and does not currently issue tax documents. Where law requires it, we may collect tax information, report a payment, or withhold from it, and we may condition a payout on the recipient providing information the law requires us to collect. A payout conditioned this way is treated as a held balance until the information is provided.

15.Intellectual property

The UsePaid name, marks, site design and written content belong to UsePaid. Third-party token artwork, account images, names and service marks belong to their respective owners and are displayed to identify records or services. Display does not grant UsePaid a license or prove that the content is authorized.

X account data, checkmarks and non-affiliation

UsePaid is independent and is not affiliated with, sponsored by, endorsed by or operated by X Corp. or X Money. Display of an account, token, badge or payment record does not imply participation, consent or endorsement by the account holder.

Blue and gold checkmarks are displayed only when supported by the available X account-status data for the identified account. They reflect status reported by X, not verification or certification by UsePaid. Data may be cached, delayed, changed or unavailable and does not guarantee current identity, trustworthiness, payment eligibility or receipt of funds. If the source or badge type cannot be confirmed, no checkmark is displayed.

X determines its account labels. This disclosure does not state that X authorized UsePaid or its use of a mark. See the disclosures page for related information.

16.No warranty

The service is provided as-is and as-available, without warranties of any kind, whether express or implied, including any implied warranty of merchantability, fitness for a particular purpose or non-infringement.

On-chain systems fail, RPC providers go down, claims revert, launchpads change their fee mechanics, and third-party rails change their rules without notice. UsePaid does not guarantee that any fee will be claimable, that any claim will succeed, that any payment will settle, that any figure shown is current, or that the service will be available at any given time.

17.Limitation of liability

To the fullest extent permitted by law, UsePaid is not liable for indirect, incidental, special, consequential or exemplary loss, or for loss of profits, revenue, data, goodwill or token value, however caused.

UsePaid's total liability arising out of or relating to the service is limited to the total protocol cut it actually retained in respect of the token giving rise to the claim in the twelve months before the event. Nothing in these terms excludes liability that cannot lawfully be excluded.

Tokens are high risk. UsePaid is not responsible for the value or behaviour of any token, including $PAID, and is not responsible for the acts of any launchpad, chain, bridge or payment rail it depends on.

18.Indemnity

As an active user accepting the effective Terms under clause 4, you will indemnify, defend, and hold harmless the Operator and its owners, officers, employees, and agents from and against any claims, losses, liabilities, and expenses, including reasonable attorneys' fees, arising out of or relating to your token, its name, description, or artwork, the handle it names, your breach of these Terms, or your violation of law or of any third party's rights.

19.Disputes, arbitration, and governing law

This section applies to active users who accept the effective Terms under clause 4. Merely being named by a token or receiving an unsolicited payment does not bind an account holder to these dispute provisions.

Informal resolution first. Before starting arbitration or any proceeding, you must send a written description of the dispute to admin@usepaid.app and give us 30 days to resolve it with you. We will do the same before starting a proceeding against you.

Agreement to arbitrate. Any dispute, claim, or controversy arising out of or relating to these Terms, the site, the protocol, a token registered with it, a payout, a held balance, or $PAID will be resolved by final and binding arbitration administered by the American Arbitration Association under its applicable rules, rather than in court. The Federal Arbitration Act governs this section. The arbitration will be decided by one arbitrator, seated in the state in which UsePaid is organized, and conducted by videoconference or on written submissions unless the arbitrator finds an in-person hearing necessary. Judgment on the award may be entered in any court with jurisdiction.

What stays in court. Either party may bring an individual claim in small claims court if it qualifies there, and either party may seek injunctive relief in court to protect intellectual property or to stop unauthorized use of the service.

Individual basis only. Disputes will be arbitrated only on an individual basis. Neither party may participate in a class, collective, consolidated, or representative action, and the arbitrator may not consolidate claims or preside over any form of representative proceeding. This waiver of class and representative proceedings is an essential part of this section. If a court finds it unenforceable as to a particular dispute, that dispute must be decided in court, and the rest of this section still applies to everything else.

Jury waiver. To the extent a dispute proceeds in court, both parties waive any right to a jury trial.

Who decides what. The arbitrator decides all questions about the interpretation, applicability, and enforceability of this section, except that a court decides the enforceability of the class and representative waiver above.

Opt-out. You may opt out of this arbitration section by sending a notice to admin@usepaid.app within 30 days of first accepting these Terms, stating your name, the handle or wallet you use, and that you opt out of arbitration. Opting out does not affect any other part of these Terms.

Time limit. Any claim must be brought within one year of the date it accrued, or it is permanently barred, to the fullest extent the law allows.

Governing law and venue. These Terms and any dispute under them are governed by the law of the state in which UsePaid is organized, without regard to its conflict of laws rules. Any matter that belongs in court under this section must be brought in the state or federal courts located in that state, and both parties consent to their jurisdiction.

20.Changes to these terms

An effective revision must identify its version, and material changes must be noted on the site. The version shown and recorded when a user accepts must agree. Revisions do not retroactively change historical balances or transaction outcomes.

21.Contact

Contact UsePaid at @UsePaid on X or admin@usepaid.app. Legal and dispute notices, arbitration opt-outs and removal requests may be sent to that email address. UsePaid cannot delete on-chain records or override a third-party provider’s rules.