These Terms of Service are entered into between you and DiscPay Ltd, a company registered in England and Wales under company number 17224498, with its registered office at 167-169 Great Portland Street, 5th Floor, London, W1W 5PF, England, trading as DiscPay.

These Terms govern your access to and use of DiscPay, including the DiscPay website, Discord bot, generated store pages, token systems, owner onboarding, operator tools, payment-linked workflows, reward catalogue tools, transaction records, support tools, and any related services provided by DiscPay Ltd.

This document is intended to define the relationship between DiscPay, Discord server owners, operators, staff members, buyers, and other users of DiscPay. DiscPay is a technical infrastructure provider. DiscPay is not Discord, is not Stripe, does not own or control Discord servers, does not hold buyer funds, and does not act as the seller of server rewards unless expressly stated otherwise.

1. Introduction And Acceptance

1.1 These Terms

These Terms of Service, together with any policies, notices, or additional terms expressly incorporated by reference, govern your access to and use of DiscPay.

DiscPay provides technical infrastructure that allows Discord server owners to configure payment-linked token balances, generated store pages, reward catalogue tools, operator permissions, transaction records, fulfilment workflows, support flows, and related systems for use in connection with their Discord communities.

These Terms apply to all use of DiscPay, including use by Server Owners, Operators, Staff, Buyers, server members, and any other person who accesses or interacts with DiscPay.

1.2 Acceptance of these Terms

By accessing or using DiscPay, inviting or configuring the DiscPay Discord bot, completing onboarding, connecting a Stripe account, creating or managing a store page, configuring rewards, granting permissions to staff, purchasing Tokens, redeeming Tokens, using DiscPay as an Operator or Staff member, or otherwise interacting with DiscPay, you agree to be bound by these Terms.

If you do not agree to these Terms, you must not access or use DiscPay.

If you use DiscPay on behalf of a Discord server, business, organisation, community, or other entity, you confirm that you have authority to bind that server, business, organisation, community, or entity to these Terms. If you do not have that authority, you must not use DiscPay on its behalf.

1.3 Different types of users

Different parts of these Terms apply to different types of users.

Sections relating to onboarding, Stripe accounts, store configuration, pricing, tax, reward fulfilment, permissions, operators, staff, and server compliance primarily apply to Server Owners.

Sections relating to permissions, token adjustments, reward handling, fulfilment records, support tickets, and operational actions may apply to Operators and Staff.

Sections relating to Token purchases, Token balances, reward requests, refunds, disputes, chargebacks, and buyer conduct may apply to Buyers.

Where a section applies only to a particular category of user, this may be stated expressly. Where no limitation is stated, the section applies to all users to the extent relevant.

1.4 Additional policies

DiscPay may publish additional policies, notices, summaries, or guidance that apply to use of the service. These may include, without limitation:

1. a Privacy Policy;
2. a Data Collection Notice or data collection summary;
3. a Refund and Chargeback Policy;
4. a Prohibited Use Policy;
5. a Cookie Policy;
6. onboarding notices;
7. checkout notices;
8. support and enforcement procedures; and
9. technical or operational documentation.

Where any additional policy is expressly incorporated into these Terms, that policy forms part of these Terms.

If there is a conflict between these Terms and an additional policy, these Terms will apply unless the additional policy expressly states that it overrides a specific section of these Terms.

1.5 Privacy Policy and data use

Use of DiscPay may involve the collection and processing of personal data and technical data, including Discord user identifiers, Discord usernames, Discord display names, Discord avatar or icon references, server identifiers, server names, server icons, email addresses provided by users, country information, Stripe-related references, transaction metadata, Token balances, logs, security records, OAuth/session information, and error metadata.

DiscPay’s handling of personal data is described in its Privacy Policy. By using DiscPay, you acknowledge that DiscPay will collect, use, store, and process data as described in the Privacy Policy and any applicable Data Collection Notice.

Server Owners must ensure that they understand the data collected during onboarding and operation of DiscPay before completing onboarding or enabling DiscPay for their server.

1.6 Changes to DiscPay

DiscPay may add, remove, modify, suspend, restrict, or replace features at any time. This may include changes to onboarding flows, store pages, checkout limits, Token bundles, reward tools, operator permissions, supported payment methods, supported countries, logging systems, recovery tools, security features, and integrations with third-party platforms.

DiscPay may make changes for operational, commercial, technical, security, fraud-prevention, legal, payment-processing, platform-compliance, or user-safety reasons.

Where a change materially affects your legal rights or obligations, DiscPay will provide notice where reasonably practical. Some changes may need to take effect immediately, including changes required for security, fraud prevention, legal compliance, payment processor requirements, Discord platform requirements, or emergency operational reasons.

1.7 No legal, tax, financial, or professional advice

DiscPay does not provide legal, tax, accounting, financial, business, payment, compliance, or professional advice.

Server Owners are responsible for determining their own legal, tax, accounting, and regulatory obligations in relation to the products, services, rewards, access, roles, benefits, or other items they offer through or in connection with DiscPay.

Buyers and Server Owners should seek independent advice where necessary.

2. Definitions

2.1 “DiscPay”

“DiscPay” means the service operated by DiscPay Ltd, trading as DiscPay, including the DiscPay website, Discord bot, store pages, onboarding systems, Token systems, reward tools, transaction records, support systems, operator tools, logs, integrations, and related services.

In these Terms, “DiscPay”, “we”, “us”, and “our” refer to DiscPay Ltd.

2.2 “User”

“User”, “you”, or “your” means any person or entity that accesses, uses, configures, manages, purchases through, redeems through, or otherwise interacts with DiscPay.

This includes Server Owners, Operators, Staff, Buyers, and other users.

2.3 “Discord”

“Discord” means the Discord platform, services, software, websites, applications, APIs, bots platform, servers, and related systems operated by Discord or its affiliated entities.

DiscPay is independent from Discord and is not owned, operated, controlled, endorsed, sponsored, or approved by Discord.

2.4 “Stripe”

“Stripe” means Stripe and its affiliated entities, services, APIs, payment-processing tools, Stripe Connect systems, checkout tools, dispute systems, tax tools, onboarding systems, and related payment infrastructure.

Payments made through DiscPay-supported flows are processed by Stripe or another supported payment processor. DiscPay does not hold buyer funds.

2.5 “Server”

“Server” means a Discord server, guild, community, or other Discord-based environment in which DiscPay is installed, configured, used, or made available.

2.6 “Server Owner”

“Server Owner” means the person who owns or controls a Discord Server for the purposes of Discord permissions and who completes, attempts to complete, or is required to complete DiscPay onboarding for that Server.

A Server Owner may also be a business, organisation, group, or other legal entity where the person completing onboarding acts on behalf of that entity.

A Server Owner is responsible for the Server’s use of DiscPay, including onboarding information, Stripe connection, pricing, taxes, reward configuration, staff permissions, fulfilment, disputes, compliance, and the actions of authorised Operators and Staff.

2.7 “Operator”

“Operator” means a person granted operational permissions by a Server Owner to use certain DiscPay tools, commands, dashboards, workflows, or administrative features in relation to a Server.

Operators may only use DiscPay to the extent authorised by the Server Owner and by the permissions granted to them within DiscPay.

2.8 “Staff”

“Staff” means a person who is granted specific permissions by a Server Owner or authorised Operator to perform limited actions within DiscPay, such as viewing records, handling fulfilment, creating or responding to tickets, adding Tokens, removing Tokens, adjusting balances, managing reward requests, or performing other permitted operational actions.

Staff permissions may vary depending on the configuration chosen by the Server Owner.

2.9 “Buyer”

“Buyer” means a person who purchases Tokens, attempts to purchase Tokens, receives Tokens, holds a Token balance, redeems Tokens, requests rewards, or otherwise interacts with a DiscPay store, checkout, Token balance, or reward workflow.

A Buyer may also be a member of a Server, but a person does not need to be a Server Owner or Operator to be a Buyer.

2.10 “Token” or “Tokens”

“Token” or “Tokens” means server-specific internal accounting units used by DiscPay to track a Buyer’s eligibility to request, redeem, or receive rewards configured by a Server Owner.

Tokens are specific to the Server for which they are purchased or credited. Tokens are not universal across DiscPay.

Tokens are not money, electronic money, stored value, cryptocurrency, securities, financial instruments, gift cards, vouchers, cash-equivalent value, or legal tender.

Tokens are not transferable between users, are not transferable between Servers, and cannot be redeemed for cash through DiscPay.

2.11 “Token Balance”

“Token Balance” means the number of Tokens recorded by DiscPay for a particular Buyer in relation to a particular Server.

A Token Balance is an internal technical record. It does not represent money held by DiscPay, money owed by DiscPay, stored value, a deposit, a bank balance, or a right to withdraw funds.

2.12 “Reward”

“Reward” means any role, access right, digital item, digital service, server benefit, server perk, custom product, code project, art product, SaaS access, Minecraft server access, community benefit, or other item or service offered by a Server Owner or their authorised Operators or Staff in connection with Tokens.

Rewards are configured, described, offered, controlled, and fulfilled by Server Owners and their authorised Operators or Staff.

Unless DiscPay expressly states otherwise in writing, DiscPay does not create, sell, control, deliver, or guarantee Rewards.

2.13 “Reward Catalogue”

“Reward Catalogue” means any list, menu, command, dashboard, store, Discord interface, or other system through which a Server Owner displays, configures, manages, or offers Rewards that may be requested or redeemed using Tokens.

A Reward Catalogue may exist inside Discord, through DiscPay commands, through generated store pages, through dashboards, through tickets, or through other supported interfaces.

2.14 “Store” or “Store Page”

“Store” or “Store Page” means a DiscPay-generated or DiscPay-supported web page, checkout page, interface, or other environment through which Buyers may view, select, or purchase Token bundles or related offerings for a particular Server.

A Store Page may display Server-specific information such as Server name, Server icon, Token bundles, checkout buttons, pricing, cart details, legal notices, and other purchase-related information.

2.15 “Checkout”

“Checkout” means the payment flow through which a Buyer purchases Tokens using Stripe or another supported payment processor.

Checkout may involve redirection to Stripe or other payment interfaces. DiscPay does not control all aspects of the payment processor’s checkout, verification, fraud review, payment-method rules, dispute process, or payment approval process.

2.16 “Stripe Connected Account”

“Stripe Connected Account” means the Stripe account connected by a Server Owner for the purpose of receiving payments, managing payouts, handling payment records, processing refunds or disputes, and complying with Stripe’s requirements.

The Server Owner is responsible for their Stripe Connected Account, including accurate onboarding information, tax details, business details, identity verification, payout settings, disputes, refunds, and compliance with Stripe’s terms.

2.17 “Transaction”

“Transaction” means a payment, attempted payment, checkout session, purchase record, Token credit, refund, reversal, dispute, chargeback, manual import, adjustment, or related record processed or recorded through or in connection with DiscPay.

A Transaction may involve data from Stripe, DiscPay, Discord, a Server Owner, or a Buyer.

2.18 “Chargeback” or “Dispute”

“Chargeback” or “Dispute” means a payment challenge, cardholder dispute, payment reversal request, bank dispute, payment-method dispute, refund claim, or similar process initiated through Stripe, a card network, a bank, a payment method, or other relevant payment system.

Chargebacks and Disputes are handled through Stripe, payment networks, payment processors, banks, or applicable payment rules. DiscPay does not control those external processes.

2.19 “Permission”

“Permission” means any authority, role, command access, dashboard access, operational power, or configuration right granted within DiscPay by a Server Owner or authorised user.

Permissions may include, without limitation, the ability to view logs, view balances, add Tokens, remove Tokens, adjust balances, manage rewards, respond to tickets, update settings, access transaction records, or perform other administrative actions.

2.20 “Prohibited Use”

“Prohibited Use” means any use of DiscPay that is illegal, unsafe, abusive, fraudulent, misleading, high-risk, prohibited by these Terms, prohibited by DiscPay policy, prohibited by Stripe, prohibited by Discord, or otherwise determined by DiscPay to create unacceptable legal, security, payment, chargeback, fraud, platform, or reputational risk.

Prohibited Use includes, without limitation, use involving illegal goods or services, physical products, gift cards, cash-out, gambling, loot boxes, chance-based paid rewards, adult sexual goods or services, regulated goods or services without approval, scams, fraud, malware, hacking, doxxing, extremist activity, or services intended to violate another platform’s terms.

2.21 “DiscPay Admin”

“DiscPay Admin” means a person authorised by DiscPay to operate, support, investigate, moderate, restrict, suspend, or enforce DiscPay systems, policies, accounts, stores, servers, rewards, users, logs, or transactions.

2.22 “Terms”

“Terms” means these Terms of Service, including any policies or additional terms incorporated by reference.

3. Discpay’S Role And Third-Party Platforms

3.1 DiscPay as an infrastructure provider

DiscPay provides technical infrastructure for Discord server monetisation workflows.

DiscPay may provide tools for Server Owners to:

1. complete onboarding;
2. connect a Stripe account;
3. generate or manage store pages;
4. offer Token bundles;
5. record Token balances;
6. configure or display reward catalogues;
7. grant permissions to Operators and Staff;
8. view logs and transaction records;
9. process or import payment-related records;
10. create or manage fulfilment workflows;
11. support manual or automated reward handling; and
12. manage related operational features.

DiscPay’s role is to provide infrastructure and records. DiscPay does not become the owner, operator, seller, guarantor, employer, agent, partner, or representative of a Server Owner merely because the Server Owner uses DiscPay.

3.2 Server Owners are responsible for their Servers

Server Owners are responsible for their own Servers and for the products, services, roles, access, benefits, Rewards, descriptions, prices, fulfilment promises, community rules, moderation decisions, tax obligations, refunds, disputes, and legal compliance connected to their use of DiscPay.

Server Owners are also responsible for the actions and omissions of Operators, Staff, and any other users to whom they grant permissions.

DiscPay does not control Discord Servers and is not responsible for a Server Owner’s community, rules, moderation decisions, bans, removals, failed fulfilment, reward descriptions, reward quality, reward availability, or disputes with Buyers except to the limited extent expressly stated in these Terms.

3.3 DiscPay is not the seller of server rewards

Unless DiscPay expressly states otherwise in writing, DiscPay is not the seller of Rewards offered by Server Owners.

A Buyer who purchases Tokens for a Server is purchasing access to server-specific Tokens recorded by DiscPay for that Server. Any Reward offered in exchange for or in connection with those Tokens is offered by the relevant Server Owner, not by DiscPay, unless DiscPay expressly states otherwise.

DiscPay does not guarantee that a Server Owner will provide any particular Reward, maintain any particular Reward Catalogue, keep a Server available, keep a Buyer unbanned, continue using DiscPay, or continue offering any specific benefit.

3.4 DiscPay does not hold buyer funds

DiscPay does not hold Buyer funds.

Payments are processed by Stripe or another supported payment processor. Funds may be processed, held, delayed, paid out, reversed, refunded, disputed, frozen, or otherwise handled according to the rules and systems of Stripe, the relevant payment processor, banks, payment networks, and applicable law.

DiscPay may receive or store payment-related metadata, transaction references, Stripe account references, checkout references, and related records in order to operate the service, credit Tokens, prevent fraud, support recovery, maintain logs, enforce these Terms, and assist with dispute or transaction history.

3.5 No banking, e-money, escrow, or financial services

DiscPay does not provide banking services, deposit accounts, payment accounts, escrow services, money transmission, electronic money, stored-value services, financial services, investment services, securities services, crypto-asset services, lending, insurance, or regulated payment services.

Tokens are not money and do not represent funds held by DiscPay.

Nothing in DiscPay should be understood as creating a bank account, payment account, wallet, deposit, stored-value balance, claim to funds, investment, security, or right to cash redemption.

3.6 Relationship with Stripe

Stripe is a third-party payment processor.

Server Owners may be required to create, connect, verify, maintain, or operate a Stripe Connected Account in order to use certain DiscPay features.

Server Owners are responsible for complying with Stripe’s terms, requirements, verification processes, payout rules, tax tools, dispute procedures, refund rules, prohibited-business rules, risk reviews, and other payment-processing requirements.

DiscPay is not responsible for Stripe’s decisions, actions, delays, restrictions, account holds, account closures, onboarding requirements, payout delays, payment failures, dispute outcomes, chargeback outcomes, refund processing, fraud reviews, or other payment-processor conduct.

If Stripe restricts, suspends, closes, delays, or otherwise affects a Server Owner’s Stripe Connected Account, DiscPay may be unable to provide some or all payment-related features for that Server.

3.7 Relationship with Discord

Discord is a third-party platform.

DiscPay is independent from Discord and is not owned, operated, controlled, endorsed, sponsored, approved, or guaranteed by Discord.

DiscPay depends on Discord APIs, bot functionality, permissions, server availability, account availability, platform rules, developer rules, moderation systems, and technical access. These dependencies are outside DiscPay’s control.

DiscPay does not guarantee that Discord access, bot functionality, server access, API functionality, command functionality, role functionality, messages, tickets, webhooks, OAuth, or other Discord-dependent features will remain available, uninterrupted, or unchanged.

If Discord changes its rules, APIs, permissions, technical systems, bot policies, developer policies, monetisation policies, or enforcement approach, DiscPay may need to change, restrict, suspend, remove, or discontinue features.

Users, Server Owners, Operators, Staff, and Buyers must not represent DiscPay as an official Discord product, Discord-operated payment service, Discord-approved monetisation programme, or Discord-controlled reward system.

DiscPay provides independent Discord-related payment infrastructure and automation tooling. Any use of Discord names, icons, identifiers, OAuth, bot commands, channels, roles, or server metadata is for technical integration and identification only.

3.8 Compliance with third-party terms

Users must comply with all applicable third-party terms when using DiscPay, including the terms, policies, rules, and requirements of Discord, Stripe, payment-method providers, banks, hosting providers, and any other relevant third-party services.

A Server Owner must not use DiscPay to sell, provide, facilitate, advertise, or support anything that violates Discord’s rules, Stripe’s rules, another platform’s rules, applicable law, or DiscPay’s Prohibited Use restrictions.

DiscPay may suspend, restrict, disable, remove, or terminate any Server, Store, Reward, user, permission, checkout flow, or Token-related feature if DiscPay believes that the relevant activity may violate third-party terms or create legal, payment, security, fraud, platform, or reputational risk.

3.9 No partnership or agency

Use of DiscPay does not create a partnership, joint venture, employment relationship, franchise, fiduciary relationship, agency relationship, payment-service relationship, or representative relationship between DiscPay and any Server Owner, Operator, Staff member, Buyer, or other user.

Server Owners are independent from DiscPay. Operators and Staff act under the authority of the relevant Server Owner, not under the authority of DiscPay, unless expressly authorised by DiscPay in writing.

3.10 Service limitations

DiscPay is provided as a technical service and may be subject to limitations, errors, delays, interruptions, maintenance, third-party outages, configuration issues, permission issues, security controls, payment-processor delays, Discord API limitations, and other operational constraints.

DiscPay may use logs, recovery tools, transaction imports, duplicate-detection systems, queue processing, manual review, fraud-prevention systems, and administrative controls to maintain the integrity of the service.

However, DiscPay does not guarantee that every payment, Token credit, Reward request, ticket, message, webhook, import, balance update, or operational action will occur instantly or without error.

Further provisions relating to service availability, technical failures, recovery, disclaimers, and liability are set out later in these Terms.

4. Eligibility And Legal Capacity

4.1 Eligibility to use DiscPay

You may use DiscPay only if you are legally permitted to do so in your location and are able to comply with these Terms, applicable law, Discord’s terms and policies, Stripe’s terms and policies, and any other relevant third-party requirements.

DiscPay may restrict access to the service, or to particular features of the service, based on country, payment-processor availability, legal requirements, fraud risk, platform risk, technical limitations, or other operational reasons.

DiscPay is intended to be available only where its supported payment processors, including Stripe, support the relevant onboarding, payment, payout, and compliance flows. DiscPay may refuse, suspend, or restrict access where a Server Owner, Server, Buyer, or transaction is located in or connected to an unsupported country or region.

4.2 Server Owner eligibility

To complete onboarding for a Server, you must be the Discord Server Owner or otherwise have authority recognised by DiscPay to act on behalf of the Server Owner.

By completing onboarding, you confirm that:

1. you are the owner or authorised controller of the relevant Discord Server;
2. you have authority to bind yourself and, where applicable, the relevant business, organisation, community, or entity to these Terms;
3. you are legally old enough and have legal capacity to sell products or services in your location;
4. you are legally permitted to use Stripe or any other supported payment processor connected through DiscPay;
5. the information you provide during onboarding is accurate, complete, and not misleading;
6. you will keep your account, Server, payment, tax, contact, and compliance information accurate and up to date;
7. you will comply with all applicable laws, regulations, tax obligations, payment-processor rules, Discord rules, and DiscPay policies; and
8. you will not use DiscPay for any Prohibited Use.

4.3 Legal capacity confirmation

During onboarding, DiscPay may require the Server Owner to confirm that they are legally old enough and have legal capacity to sell products or services in their location.

This confirmation is a material part of the onboarding process. DiscPay may refuse, suspend, restrict, or terminate access if DiscPay believes that the confirmation is false, inaccurate, incomplete, misleading, or no longer valid.

DiscPay may require additional verification, support contact, documentation, or re-confirmation if there is uncertainty about a Server Owner’s legal capacity, authority, country, Stripe eligibility, or compliance position.

4.4 Business, organisation, or community use

If you use DiscPay on behalf of a business, organisation, community, group, brand, or other entity, you confirm that you have authority to act on behalf of that entity and to bind that entity to these Terms.

If you do not have that authority, you must not complete onboarding, connect a Stripe account, configure a Store, grant permissions, create Rewards, accept payments, or otherwise use DiscPay on behalf of that entity.

Where a Server is operated by multiple people, a business, an organisation, or a community team, the person completing onboarding remains responsible for ensuring that DiscPay is used lawfully and in accordance with these Terms.

4.5 Buyers and general users

Buyers and other users may use DiscPay only if they are legally permitted to do so and are able to comply with these Terms.

By purchasing Tokens, attempting to purchase Tokens, holding a Token Balance, redeeming Tokens, requesting Rewards, or otherwise using DiscPay as a Buyer, you confirm that you are legally permitted to make the relevant purchase and use the relevant service in your location.

DiscPay may restrict, suspend, or refuse access to Buyers or other users where required for legal, payment, fraud-prevention, platform, safety, or operational reasons.

4.6 No circumvention of eligibility rules

You must not attempt to bypass DiscPay’s eligibility, country, verification, onboarding, payment, security, suspension, or enforcement restrictions.

This includes, without limitation, using false information, misleading account details, unauthorised Stripe accounts, unauthorised Discord accounts, VPNs or proxies to hide restricted activity, another person’s identity or payment account, or any other method designed to avoid DiscPay’s eligibility or compliance controls.

DiscPay may suspend or terminate access if it believes that eligibility rules have been bypassed or abused.

5. Server Owner Onboarding

5.1 Owner-only onboarding

Server onboarding must be completed by the Server Owner unless DiscPay expressly approves another process.

DiscPay uses owner-only onboarding to protect payment integrity, prevent unauthorised monetisation, reduce fraud risk, avoid unauthorised Stripe account connections, and ensure that the person accepting legal responsibility for the Server has authority to do so.

Operators, Staff, moderators, administrators, or other Server members may not complete owner onboarding unless they are also the Server Owner or have been expressly approved by DiscPay through a supported process.

5.2 Email verification

DiscPay may require email verification before onboarding can be completed.

The Server Owner must provide a valid email address that they control and can access. DiscPay may use this email address for onboarding verification, legal notices, support, security alerts, payment-related notices, enforcement notices, and other communications relating to the Server’s use of DiscPay.

The Server Owner is responsible for keeping their email address accurate and up to date.

If the Server Owner loses access to the email address, provides an incorrect email address, or fails to respond to required communications, DiscPay may restrict, suspend, or disable some or all Server features until the issue is resolved.

5.3 Required onboarding acceptance

During onboarding, the Server Owner may be required to accept or confirm:

1. these Terms;
2. DiscPay’s Privacy Policy;
3. DiscPay’s Data Collection Notice or data collection summary;
4. legal capacity to sell products or services in their location;
5. authority to configure DiscPay for the relevant Server;
6. responsibility for Rewards, fulfilment, taxes, staff permissions, disputes, and compliance; and
7. any additional onboarding notices, platform requirements, or payment-processor requirements presented during onboarding.

The Server Owner must not complete onboarding unless they understand and agree to these requirements.

5.4 Onboarding records

DiscPay may record onboarding information and acceptance records, including timestamps, Discord Server identifiers, Discord user identifiers, email addresses, country information, acceptance confirmations, Stripe-related references, technical metadata, logs, and other records reasonably required to operate the service, evidence acceptance, maintain security, prevent abuse, support payment workflows, and enforce these Terms.

These records may be stored and processed in accordance with DiscPay’s Privacy Policy and Data Collection Notice.

The Server Owner acknowledges that accurate onboarding records are necessary because DiscPay involves payment-linked workflows, Token balances, Server-specific records, staff permissions, transaction history, security controls, and compliance obligations.

5.5 Accuracy of onboarding information

The Server Owner must provide accurate, complete, current, and non-misleading information during onboarding and throughout use of DiscPay.

The Server Owner must not provide false information, use another person’s details without authorisation, connect a Stripe account they are not authorised to use, misrepresent their country, misrepresent their legal capacity, misrepresent their authority over a Server, or otherwise provide misleading onboarding information.

DiscPay may suspend, restrict, terminate, reset, or require re-onboarding if it believes onboarding information is inaccurate, incomplete, outdated, fraudulent, misleading, or no longer valid.

5.6 Stripe onboarding and payment activation

Certain DiscPay features may require the Server Owner to connect and maintain a Stripe Connected Account.

DiscPay may treat a Server as incomplete, inactive, limited, or unable to use payment-related features until the required Stripe onboarding, verification, account setup, and status checks are complete.

DiscPay is not responsible for Stripe’s onboarding requirements, account verification decisions, payout delays, account restrictions, account closures, identity checks, tax requirements, dispute handling, refund handling, risk reviews, or prohibited-business decisions.

If Stripe rejects, restricts, suspends, closes, or otherwise limits the Server Owner’s Stripe Connected Account, DiscPay may disable or restrict checkout, Store access, payment-linked Token purchases, or other payment-related functionality for the relevant Server.

5.7 Initial approval and continuing review

A Server may be treated as approved after onboarding is completed, provided that required information, acceptance steps, and payment setup have been completed to DiscPay’s satisfaction.

However, approval is not permanent or unconditional.

DiscPay may review, restrict, suspend, disable, or terminate a Server at any time if DiscPay believes that the Server, Server Owner, Operators, Staff, Buyers, Rewards, Store, payment activity, Token activity, or related conduct may violate these Terms, violate DiscPay policy, violate Discord rules, violate Stripe rules, violate applicable law, create fraud risk, create chargeback risk, create security risk, create reputational risk, or otherwise create unacceptable risk for DiscPay.

5.8 Changes after onboarding

After onboarding is complete, some Server settings may be locked, restricted, or changeable only through supported processes.

DiscPay may require support review, additional verification, re-confirmation, or manual approval for changes involving sensitive information, including ownership, country, Stripe account references, legal details, payment settings, tax-related settings, or other high-risk configuration.

DiscPay may refuse or delay changes where required for security, payment integrity, fraud prevention, legal compliance, platform compliance, or operational reasons.

5.9 Support-assisted changes

DiscPay may allow certain changes through a support-assisted process, such as a support ticket, email verification, additional checks, manual review, or other approved workflow.

DiscPay is not required to approve every requested change.

Where a requested change affects legal responsibility, payment processing, Stripe account connection, Server ownership, tax responsibility, Token records, or dispute handling, DiscPay may require additional evidence before applying the change.

5.10 Suspension for non-payment or policy breach

DiscPay may suspend, restrict, or disable a Server’s access to DiscPay if required fees are unpaid, if the Server breaches these Terms, if the Server engages in Prohibited Use, if Stripe or Discord risk is identified, or if DiscPay determines that continued service would create unacceptable legal, payment, fraud, security, platform, operational, or reputational risk.

Suspension may include disabling checkout, hiding or disabling Store Pages, freezing or limiting Token redemption, removing Rewards, restricting Operators or Staff, restricting owner access, preserving records, or preventing further purchases.

Suspension does not necessarily delete existing records, Token Balances, transaction history, logs, or Server configuration.

6. Server Ownership Changes

6.1 Ownership changes require re-onboarding

If ownership or effective control of a Discord Server changes, DiscPay may reset, wipe, disable, suspend, or revoke the Server’s onboarding status and require the new Server Owner to complete onboarding before the Server can continue using DiscPay.

This rule exists to protect payment integrity, legal responsibility, Stripe account accuracy, tax responsibility, contact accuracy, Token records, Buyer protection, and Server accountability.

A new Server Owner must not rely on the previous Server Owner’s onboarding, Stripe account connection, legal confirmations, email address, country information, tax position, or acceptance records.

6.2 No automatic transfer of Stripe accounts

A Stripe Connected Account linked to one Server Owner must not be treated as automatically transferable to a new Server Owner.

If Server ownership changes, the new Server Owner may be required to connect their own Stripe Connected Account and complete any required Stripe onboarding, verification, account setup, and compliance checks.

DiscPay may disable checkout, Store Pages, payment-linked Token purchases, payout-related features, or other payment-related functions until the new Server Owner has completed the required onboarding process.

6.3 Previous owner access

If Server ownership changes, DiscPay may revoke, restrict, or disable the previous Server Owner’s access to owner-level DiscPay features for that Server.

DiscPay may also revoke, restrict, or review Operators, Staff, permissions, Store settings, reward catalogues, payment settings, and other configuration connected to the previous Server Owner.

DiscPay may preserve historical records, including transaction records, Token Balances, logs, Stripe-related references, support records, and acceptance records, where necessary for payment integrity, fraud prevention, legal compliance, dispute handling, tax or accounting records, security, or service continuity.

6.4 New owner responsibility

A new Server Owner who completes onboarding becomes responsible for the Server’s future use of DiscPay from the point they complete onboarding and are approved by DiscPay.

The new Server Owner is responsible for ensuring that Rewards, permissions, staff access, Store settings, Token-related workflows, tax obligations, contact information, and Stripe information are accurate and appropriate.

DiscPay may require the new Server Owner to review, update, confirm, or remove existing configuration before payment-related features are restored.

6.5 Existing Token Balances after ownership change

DiscPay may preserve existing Token Balances and transaction records after a Server ownership change.

However, preservation of Token Balances does not guarantee that the new Server Owner will offer the same Rewards, maintain the same Reward Catalogue, provide the same fulfilment commitments, honour previous informal promises, or continue using DiscPay in the same way as the previous Server Owner.

DiscPay may require review, restrictions, or additional controls where an ownership change creates risk to Buyers, Server Owners, payment integrity, or DiscPay.

6.6 Failure to notify DiscPay

If a Server Owner, Operator, Staff member, Buyer, or other user knows or reasonably suspects that Server ownership has changed, they should notify DiscPay through the available support contact or supported process.

If a Server continues using DiscPay after an ownership change without completing required re-onboarding, DiscPay may suspend, restrict, disable, reverse, or review affected features, Transactions, permissions, Stores, Rewards, or Token workflows.

6.7 Disputes over ownership

DiscPay is not responsible for resolving internal disputes over Discord Server ownership, moderation control, business ownership, partnership disputes, community disputes, or staff disputes.

DiscPay may rely on Discord ownership status, available technical signals, support evidence, Stripe information, email verification, legal records, or other information that DiscPay considers relevant.

Where ownership is disputed, DiscPay may suspend or restrict the affected Server, disable checkout, freeze sensitive features, preserve records, and require additional evidence before restoring access.

6.8 DiscPay discretion

DiscPay has discretion to determine whether re-onboarding, suspension, review, or additional verification is required after an ownership change or suspected ownership change.

DiscPay may act before completing a full investigation where it believes immediate action is necessary to protect Buyers, Server Owners, payment integrity, Token records, Stripe compliance, Discord compliance, security, legal compliance, or DiscPay’s platform integrity.

7. Operators, Staff, And Permissions

7.1 Owner control of permissions

The Server Owner is responsible for controlling who may access, configure, operate, or manage DiscPay features for their Server.

DiscPay may allow a Server Owner to grant permissions to Operators, Staff, administrators, moderators, fulfilment personnel, or other authorised users. These permissions may allow such users to access or perform actions within DiscPay, depending on the features available at the time and the permissions granted by the Server Owner.

The Server Owner is responsible for granting permissions carefully and only to users they trust.

7.2 Operators

An Operator is a user authorised by the Server Owner to perform operational actions in relation to a Server’s use of DiscPay.

Operator permissions may include, without limitation, the ability to view Server configuration, view transaction records, view Token Balances, manage reward workflows, assist with fulfilment, use operational commands, manage Store-related settings, access support tools, or perform other actions made available by DiscPay.

Operators are not independent account owners unless separately approved by DiscPay. Operators act under the authority of the relevant Server Owner.

The Server Owner remains responsible for the actions, omissions, configuration choices, and misuse of Operators.

7.3 Staff and direct permission holders

A Server Owner may grant specific permissions to Staff or other direct permission holders.

These permissions may include limited or specific access, such as:

1. viewing Token Balances;
2. viewing transaction records;
3. viewing reward requests;
4. responding to fulfilment tickets;
5. adding Tokens;
6. removing Tokens;
7. adjusting Token Balances;
8. marking rewards as fulfilled;
9. managing or reviewing logs;
10. using specific DiscPay commands; or
11. performing other permitted actions supported by DiscPay.

Staff and direct permission holders may only use DiscPay within the scope of the permissions granted to them.

7.4 Owner responsibility for authorised users

The Server Owner is responsible for all actions and omissions of Operators, Staff, direct permission holders, administrators, moderators, or other users authorised to access DiscPay features for the Server.

This includes responsibility for:

1. incorrect Token adjustments;
2. unauthorised Token removals;
3. excessive Token additions;
4. false fulfilment markings;
5. mishandled reward requests;
6. inaccurate support responses;
7. misuse of transaction records;
8. improper access to Buyer information;
9. poor configuration choices;
10. failure to remove permissions from former Staff; and
11. any other misuse of permissions.

DiscPay is not responsible for losses, disputes, failed fulfilment, balance errors, reward issues, or other problems caused by the Server Owner’s chosen Operators, Staff, permission holders, or internal management decisions, except to the extent directly caused by DiscPay’s own system error.

7.5 Permission scope and limitations

Permissions may be limited by role, command, action type, Server, feature, workflow, or other controls made available by DiscPay.

DiscPay may add, remove, rename, modify, restrict, or replace permission types at any time for operational, security, legal, fraud-prevention, payment, compliance, or product reasons.

A permission being available in DiscPay does not mean it is safe, appropriate, or legally suitable for every Server. The Server Owner is responsible for deciding which users should receive which permissions.

The Server Owner must not grant sensitive permissions to users who are not trusted, not trained, not legally suitable, or not authorised to act on behalf of the Server.

7.6 Sensitive permissions

Some permissions may be considered sensitive because they affect Token Balances, transaction records, Buyer records, reward fulfilment, payment-linked workflows, Store settings, or compliance-related information.

Sensitive permissions may include, without limitation:

1. adding Tokens;
2. removing Tokens;
3. editing Token Balances;
4. viewing Buyer balances;
5. viewing transaction history;
6. managing refund-related records;
7. importing or reviewing payment records;
8. configuring Rewards;
9. changing Store or checkout-related settings;
10. granting permissions to other users; and
11. accessing logs or security-related records.

DiscPay may restrict, log, require additional checks for, or refuse certain sensitive permission actions where necessary to protect Buyers, Server Owners, payment integrity, security, or platform integrity.

7.7 Balance editing permissions

If a Server Owner grants a user permission to add, remove, or adjust Tokens, the Server Owner accepts responsibility for the consequences of that permission.

Balance editing can affect Buyer trust, reward eligibility, transaction records, dispute handling, and Server integrity.

Users with balance editing permissions must only make changes that are accurate, authorised, and justified. They must not alter Token Balances fraudulently, maliciously, carelessly, deceptively, or for personal gain.

DiscPay may log balance edits and may investigate, reverse, restrict, or suspend balance-editing activity where it suspects abuse, fraud, error, misuse, chargeback risk, refund inconsistency, duplicate crediting, or other harmful conduct.

7.8 Reward and fulfilment permissions

If a Server Owner grants a user permission to manage Rewards, fulfilment tickets, reward requests, or fulfilment records, the Server Owner accepts responsibility for that user’s actions.

Users with reward or fulfilment permissions must not falsely mark Rewards as fulfilled, mislead Buyers, ignore fulfilment obligations, remove reward requests without proper reason, or use DiscPay tools to conceal failed fulfilment.

DiscPay does not guarantee that Operators or Staff will correctly fulfil Rewards. Fulfilment remains the responsibility of the Server Owner and their authorised users.

7.9 Permission misuse

Permission misuse includes, without limitation:

1. using DiscPay permissions for unauthorised purposes;
2. modifying Token Balances without proper reason;
3. creating false transaction or fulfilment records;
4. removing Tokens to punish Buyers unfairly;
5. adding Tokens for personal benefit or favouritism;
6. accessing Buyer information without a legitimate Server-related reason;
7. sharing private logs or transaction records outside authorised channels;
8. concealing chargebacks, refunds, disputes, failed fulfilment, or abuse;
9. granting access to unauthorised users;
10. continuing to use permissions after authority has been withdrawn;
11. using permissions to harass, threaten, exploit, or mislead Buyers; or
12. otherwise acting in a way that harms Buyers, Server Owners, DiscPay, Stripe, Discord, or payment integrity.

DiscPay may restrict, suspend, remove, reverse, or investigate any action that appears to involve permission misuse.

7.10 Revoking permissions

The Server Owner is responsible for removing permissions from users who no longer require access.

This includes, without limitation, former Staff, former moderators, former administrators, former Operators, compromised accounts, untrusted users, inactive users, or users who no longer act on behalf of the Server.

DiscPay may provide tools to revoke or modify permissions, but the Server Owner remains responsible for monitoring permission access and acting promptly where access is no longer appropriate.

DiscPay may also revoke, restrict, or suspend permissions directly where necessary to protect the service, Buyers, payment integrity, security, or compliance.

7.11 Compromised accounts

If a Server Owner, Operator, Staff member, or other authorised user believes that their Discord account, email account, Stripe account, device, session, token, password, or other access method has been compromised, they must take immediate steps to secure the account and notify DiscPay where the compromise may affect DiscPay.

DiscPay may suspend, restrict, or disable affected permissions, Store Pages, checkout flows, Token edits, reward workflows, or other features while investigating a suspected compromise.

DiscPay is not responsible for losses, failed fulfilment, Token adjustments, unauthorised actions, or disputes caused by compromised accounts, except to the extent directly caused by DiscPay’s own system error.

7.12 Logs and audit records

DiscPay may create and retain logs, audit records, transaction records, command records, permission records, balance adjustment records, fulfilment records, support records, error records, and security records relating to Operator, Staff, Server Owner, Buyer, or system activity.

These records may be used to:

1. operate DiscPay;
2. support Token balance integrity;
3. investigate disputes;
4. investigate fraud or abuse;
5. support payment recovery or imports;
6. identify unauthorised access;
7. enforce these Terms;
8. comply with legal obligations;
9. protect Buyers, Server Owners, and DiscPay; and
10. improve service reliability and security.

Logs and audit records may not capture every action, may be delayed, may contain technical limitations, and may be subject to retention periods described in DiscPay’s Privacy Policy.

7.13 Visibility of operational actions

Certain operational actions may be visible to the Server Owner, Operators, Staff, Buyers, or other users depending on the feature, configuration, permissions, and interface used.

For example, Token adjustments, reward requests, purchase announcements, fulfilment tickets, command usage, or balance-related actions may be visible to authorised users or, where configured, to members of the Server.

Server Owners are responsible for understanding and configuring visibility settings appropriately.

DiscPay may change how operational actions are displayed, logged, notified, or made visible for product, legal, security, transparency, or abuse-prevention reasons.

7.14 No resale or unauthorised access to permissions

Users must not sell, rent, lend, transfer, share, or otherwise provide DiscPay permissions, access, sessions, accounts, commands, dashboards, logs, or operational tools to unauthorised persons.

A Server Owner must not allow unauthorised third parties to operate DiscPay on behalf of the Server unless such access is permitted by DiscPay and complies with these Terms.

DiscPay may suspend or terminate access where permissions are sold, shared, transferred, abused, or used by unauthorised persons.

7.15 No reliance on permissions as proof of employment or agency

Being granted Operator, Staff, or other DiscPay permissions does not make a user an employee, agent, contractor, representative, partner, or legal delegate of DiscPay.

Operators and Staff act under the authority of the relevant Server Owner, not under the authority of DiscPay.

DiscPay is not responsible for employment, payment, compensation, management, scheduling, internal disputes, or other arrangements between Server Owners and their Operators, Staff, moderators, administrators, or community members.

7.16 DiscPay administrative controls

DiscPay may use administrative controls to review, restrict, revoke, suspend, or override permissions where necessary to protect the service, Buyers, Server Owners, payment integrity, security, legal compliance, Stripe compliance, Discord compliance, or platform integrity.

DiscPay may also disable specific commands, restrict sensitive actions, require additional verification, freeze Token editing, disable reward fulfilment tools, or suspend operational access during investigations.

DiscPay is not required to provide advance notice before taking administrative action where DiscPay believes immediate action is necessary.

7.17 Owner duty to supervise

The Server Owner must supervise the Server’s use of DiscPay and must take reasonable steps to ensure that Operators, Staff, and other authorised users understand and comply with these Terms.

This includes ensuring that authorised users do not misuse Token editing, reward fulfilment, Buyer records, transaction records, logs, or other DiscPay tools.

Failure to supervise Operators, Staff, or permission holders may result in suspension, restriction, or termination of the Server’s access to DiscPay.

7.18 Effect of permission errors

Errors in permissions, role configuration, Discord permissions, DiscPay permissions, command access, staff access, or dashboard access may affect the operation of DiscPay.

The Server Owner is responsible for reviewing configuration and reporting suspected permission errors promptly.

DiscPay may attempt to provide tools, logs, support flows, or recovery options, but DiscPay does not guarantee that all permission errors can be prevented, detected, reversed, or corrected.

7.19 Survival of responsibility

The Server Owner’s responsibility for actions taken by authorised users may continue after permissions are revoked, after a Staff member leaves, after an Operator is removed, after a dispute begins, after a Server is suspended, or after the Server stops using DiscPay, to the extent the relevant actions occurred while the user had permission or access.

This includes responsibility for Token adjustments, reward fulfilment actions, misuse of Buyer information, transaction-handling errors, and other actions taken under the Server Owner’s authority.

8. Stripe, Payments, Fees, And Taxes

8.1 Payment processing through Stripe

DiscPay uses Stripe, including Stripe Connect, to support payment processing for Token purchases and related payment-linked workflows.

When a Buyer purchases Tokens through a DiscPay-supported checkout flow, the payment is processed by Stripe or another payment processor supported by DiscPay. DiscPay does not process card payments directly, does not store full payment card details, and does not control all payment-method rules, payment approvals, fraud checks, disputes, reversals, chargebacks, or payout decisions.

Stripe may require Buyers, Server Owners, or Stripe Connected Accounts to comply with Stripe’s own terms, identity checks, verification requirements, fraud controls, payment rules, tax tools, account restrictions, and compliance processes.

8.2 Server Owner as merchant

Unless DiscPay expressly states otherwise in writing, the Server Owner is the seller, merchant, or responsible operator for the Rewards, products, services, access rights, roles, benefits, or other items offered by or in connection with their Server.

The Server Owner is responsible for:

1. the goods, services, Rewards, access, roles, benefits, or other items offered through or in connection with their Server;
2. the accuracy of Reward descriptions and related information;
3. the lawfulness of what they offer;
4. fulfilment of Rewards;
5. customer support for their Buyers;
6. refund handling where applicable;
7. chargeback and dispute cooperation;
8. tax obligations;
9. compliance with Stripe’s terms;
10. compliance with Discord’s terms;
11. compliance with applicable law; and
12. any promises, representations, or commitments made to Buyers.

DiscPay provides infrastructure and records. DiscPay does not become the seller of a Server Owner’s Rewards merely because the Server Owner uses DiscPay.

8.3 Stripe Connected Account responsibility

A Server Owner may be required to create, connect, verify, and maintain a Stripe Connected Account in order to use payment-related DiscPay features.

The Server Owner is responsible for their Stripe Connected Account, including:

1. providing accurate personal, business, tax, country, and identity information;
2. maintaining accurate payout details;
3. completing Stripe verification requirements;
4. responding to Stripe requests;
5. handling Stripe account restrictions;
6. managing Stripe disputes and chargebacks;
7. complying with Stripe’s prohibited-business and restricted-business rules;
8. complying with Stripe’s tax, reporting, and compliance requirements; and
9. keeping the Stripe Connected Account in good standing.

DiscPay is not responsible for Stripe’s decisions regarding a Server Owner’s Stripe Connected Account.

If Stripe restricts, suspends, rejects, closes, freezes, delays, reviews, or otherwise limits a Stripe Connected Account, DiscPay may restrict or disable payment-related features for the affected Server.

8.4 DiscPay does not hold Buyer funds

DiscPay does not hold Buyer funds.

Payments may be processed, received, settled, paid out, reversed, refunded, delayed, frozen, disputed, or otherwise handled through Stripe, the Server Owner’s Stripe Connected Account, payment-method providers, card networks, banks, or other payment infrastructure.

DiscPay may receive or store payment-related metadata and references, such as Stripe account references, checkout session references, transaction identifiers, payment status information, Token credit records, import records, dispute records, and related logs.

Such records are used to operate DiscPay, credit Tokens, maintain transaction history, support recovery tools, prevent duplicate credits, investigate abuse, enforce these Terms, and support payment-linked workflows.

These records do not mean that DiscPay holds Buyer funds or owes Buyers a cash balance.

8.5 No regulated payment or financial service

DiscPay does not provide banking, payment accounts, stored-value accounts, electronic money, escrow, money transmission, financial services, securities services, investment services, crypto-asset services, lending, insurance, deposit-taking, or regulated payment services.

Tokens are internal server-specific accounting units and do not represent money held by DiscPay.

No Token Balance should be understood as a deposit, bank balance, wallet balance, payment account, stored-value account, e-money balance, financial instrument, security, investment, or right to withdraw funds.

8.6 DiscPay platform fee

DiscPay may charge a platform fee for use of its infrastructure, tools, Store systems, Token systems, payment-linked workflows, logs, recovery tools, operational features, and related services.

Unless otherwise stated by DiscPay, the standard DiscPay platform fee is 3% of applicable payment volume processed through DiscPay-supported checkout flows.

This fee is separate from any Stripe fees, payment-method fees, bank fees, tax amounts, currency conversion fees, chargeback fees, dispute fees, refund costs, or other third-party charges.

DiscPay may deduct, collect, invoice, record, or otherwise account for its platform fee through supported payment, Stripe, invoicing, or accounting workflows.

8.7 Fee changes

DiscPay may change its platform fees, pricing model, invoicing method, billing process, free trial structure, minimum charges, payment terms, or other commercial terms.

Where reasonably practical, DiscPay will provide at least 14 days’ notice before a material fee increase affecting existing Server Owners.

DiscPay may make immediate or shorter-notice changes where required for legal compliance, payment-processor requirements, Stripe requirements, Discord requirements, fraud prevention, security, abuse prevention, chargeback risk, tax reasons, technical reasons, or emergency operational reasons.

Continued use of DiscPay after a fee change takes effect constitutes acceptance of the changed fees.

If a Server Owner does not accept a fee change, the Server Owner must stop using DiscPay before the change takes effect.

8.8 Non-payment of DiscPay fees

If a Server Owner fails to pay amounts owed to DiscPay, or if DiscPay is unable to collect applicable fees, DiscPay may suspend, restrict, disable, or terminate some or all DiscPay features for the affected Server.

This may include, without limitation:

1. disabling checkout;
2. disabling Store Pages;
3. restricting Token purchases;
4. restricting Token redemption;
5. restricting reward catalogue tools;
6. restricting Operator or Staff access;
7. limiting support access;
8. preserving but restricting Server records;
9. suspending imports or recovery tools; and
10. preventing further use until outstanding amounts are resolved.

Suspension for non-payment does not necessarily delete Token Balances, transaction history, logs, Server records, or other retained data.

8.9 Stripe fees and third-party fees

Stripe, payment-method providers, banks, card networks, currency-conversion providers, or other third parties may charge fees.

These fees may include, without limitation:

1. payment processing fees;
2. currency conversion fees;
3. chargeback fees;
4. dispute fees;
5. refund-related fees;
6. payout-related fees;
7. cross-border fees;
8. tax tool fees; and
9. other third-party charges.

DiscPay is not responsible for third-party fees unless expressly stated otherwise in writing.

Server Owners are responsible for understanding the fees that apply to their Stripe Connected Account and payment activity.

8.10 Taxes

Server Owners are responsible for all taxes, duties, levies, charges, assessments, reporting obligations, invoicing obligations, accounting obligations, registration obligations, and other governmental obligations connected to their use of DiscPay, their Stripe Connected Account, their Token sales, their Rewards, their Buyers, and their business activity.

This may include, without limitation, VAT, sales tax, goods and services tax, income tax, corporation tax, digital services tax, withholding tax, marketplace reporting obligations, accounting records, receipts, invoices, and any other applicable tax obligations.

DiscPay does not provide tax advice and does not guarantee that any tax tool, tax estimate, tax setting, Stripe feature, record, report, export, or integration will satisfy a Server Owner’s legal or tax obligations.

Server Owners should seek independent tax or accounting advice where necessary.

8.11 Stripe Tax and tax tools

DiscPay may allow, support, reference, or integrate with Stripe Tax or other tax-related tools.

Any tax tool is provided by the relevant third party and may be subject to separate terms, limitations, configuration requirements, and country-specific rules.

The availability of a tax tool does not transfer tax responsibility from the Server Owner to DiscPay.

The Server Owner remains responsible for deciding whether a tax tool is appropriate, configuring it correctly, reviewing its outputs, collecting or remitting taxes where required, issuing invoices or receipts where required, and complying with applicable tax law.

8.12 Buyer payment responsibility

A Buyer is responsible for ensuring that they are authorised to use the payment method used at Checkout.

A Buyer must not use stolen, unauthorised, fraudulent, disputed, or improperly obtained payment methods.

A Buyer must not initiate payments fraudulently, abuse chargeback processes, misrepresent transactions, purchase Tokens for prohibited purposes, or attempt to obtain Tokens or Rewards without valid payment.

DiscPay may restrict, suspend, investigate, or ban Buyers who engage in suspected payment abuse, fraud, unauthorised payments, chargeback abuse, or other harmful payment activity.

8.13 Payment approval is not guaranteed

A payment may be declined, delayed, reviewed, cancelled, blocked, refunded, reversed, or disputed for reasons outside DiscPay’s control.

Payment approval may depend on Stripe, banks, card networks, fraud systems, payment-method providers, authentication requirements, country restrictions, account status, risk checks, payment limits, or other external factors.

DiscPay does not guarantee that any payment attempt will succeed.

DiscPay also does not guarantee that Token delivery, Token crediting, transaction recording, Discord notification, reward ticket creation, or Store updates will occur instantly after payment.

8.14 Delayed or failed payment-linked processing

If a payment succeeds but DiscPay does not immediately credit Tokens, generate a notification, create a ticket, update a record, or perform another payment-linked action, the transaction may require automated retry, manual import, manual review, support assistance, or other recovery steps.

DiscPay may provide import tools, transaction records, duplicate-detection systems, queue processing, logs, and recovery workflows to help handle delayed or failed processing.

However, DiscPay does not guarantee instant processing, and Server Owners remain responsible for reviewing records, handling Buyer support, and using available recovery tools where appropriate.

8.15 Duplicate payments and duplicate credits

DiscPay may use transaction identifiers, Stripe references, logs, deduplication logic, and other controls to reduce the risk of duplicate Token credits or duplicate fulfilment.

If DiscPay detects or reasonably suspects duplicate payment records, duplicate Token credits, duplicate imports, duplicate fulfilment, system errors, or abuse, DiscPay may correct Token Balances, reverse credits, restrict redemption, freeze related activity, or require manual review.

A Buyer is not entitled to keep Tokens that were credited because of a duplicate, error, failed payment, refunded payment, reversed payment, disputed payment, fraudulent payment, or system fault.

8.16 Currency and exchange rates

Payments may be made in currencies supported by Stripe, the relevant payment method, the relevant Stripe Connected Account, and the applicable Store configuration.

Currency availability may vary by country, payment method, Stripe account, payment processor, or DiscPay configuration.

Where currency conversion applies, exchange rates, conversion fees, bank fees, card issuer fees, cross-border fees, and other charges may be determined by Stripe, banks, card networks, payment-method providers, or other third parties.

DiscPay is not responsible for exchange rates, conversion fees, foreign transaction fees, or bank charges unless expressly stated otherwise in writing.

8.17 Payouts to Server Owners

Payouts to Server Owners are handled through Stripe or the relevant supported payment processor.

DiscPay does not guarantee payout timing, payout availability, payout method support, payout approval, payout amount after fees, Stripe account standing, payout eligibility, or payout success.

Payouts may be delayed, paused, restricted, reversed, frozen, or otherwise affected by Stripe, payment processors, banks, card networks, tax requirements, identity verification, risk checks, legal requirements, or disputes.

8.18 Refunds, reversals, and disputes

Refunds, reversals, chargebacks, and disputes may affect payment records, Token Balances, Server Owner revenue, Stripe account standing, Buyer access, and reward fulfilment.

Further provisions relating to refunds, disputes, chargebacks, and related Token adjustments are set out later in these Terms.

Nothing in this section limits any mandatory rights that a Buyer may have under applicable law.

9. Stores, Checkout Pages, Pricing, And Limits

9.1 Store Pages

DiscPay may allow Server Owners to create, generate, update, or use Store Pages for their Servers.

A Store Page may display information such as:

1. the Server name;
2. the Server icon;
3. Token bundles;
4. prices;
5. checkout buttons;
6. cart information;
7. legal notices;
8. payment processor information;
9. purchase limits;
10. support information; and
11. other information selected, configured, or supported by DiscPay.

DiscPay may create static, generated, dynamic, hosted, or otherwise supported Store Pages depending on the features available at the time.

9.2 Store Page responsibility

The Server Owner is responsible for ensuring that information connected to their Store Page is accurate, lawful, non-misleading, and compliant with these Terms.

This includes responsibility for any Server name, Server icon, descriptions, Reward references, pricing-related information, support promises, fulfilment expectations, and other Server-specific information displayed through or in connection with the Store Page.

DiscPay may remove, modify, restrict, disable, or refuse Store Page content that DiscPay believes is illegal, misleading, unsafe, prohibited, infringing, high-risk, abusive, non-compliant, or otherwise inappropriate for DiscPay.

9.3 Store Page generation and updates

DiscPay may provide tools for generating or updating Store Pages.

Store generation or updates may depend on Discord data, Server metadata, Server icon availability, Store templates, configuration files, payment status, Stripe status, system availability, permissions, and other technical requirements.

DiscPay does not guarantee that Store generation or updates will occur instantly, continuously, or without error.

If Store generation fails, updates are delayed, Server metadata is unavailable, or a Store Page becomes outdated, the Server Owner may need to retry, use supported update tools, contact support, or wait for recovery.

9.4 Pricing rules

DiscPay may set, recommend, restrict, or control Token bundle pricing, Store pricing, checkout values, minimum amounts, maximum amounts, supported packages, supported currencies, and related pricing rules.

At launch or during early versions, Token bundle pricing may be set by DiscPay.

DiscPay may later allow Server Owners to configure some or all prices, bundles, discounts, limits, or related settings.

If configurable pricing becomes available, Server Owners will be responsible for ensuring that their pricing is accurate, lawful, non-misleading, tax-compliant, and consistent with applicable rules.

9.5 Price changes

DiscPay may change Token bundles, package sizes, price points, supported currencies, pricing display rules, minimum purchase amounts, maximum purchase amounts, checkout caps, or pricing configuration options.

Where pricing changes affect a Server Owner’s Store, DiscPay may apply the changes automatically, require Server Owner confirmation, require Store regeneration, restrict old pricing, or provide other update processes.

DiscPay is not responsible for losses caused by a Server Owner failing to review pricing, update Store settings, communicate changes to Buyers, or configure pricing correctly where configurable pricing is available.

9.6 Checkout limits

DiscPay may apply checkout limits, including maximum transaction amounts, minimum transaction amounts, Token bundle limits, daily limits, Server limits, Buyer limits, risk limits, country limits, or other restrictions.

Checkout limits may be applied for legal, security, fraud-prevention, chargeback, risk, technical, payment-processor, or operational reasons.

DiscPay may change, remove, reduce, increase, or make configurable any checkout limit at any time.

A checkout limit displayed on a Store Page or enforced in a client-side interface may also be supported by server-side validation, payment-processor controls, or other security checks. A Buyer or Server Owner must not attempt to bypass checkout limits.

9.7 No bypassing checkout controls

Users must not attempt to bypass Store, cart, pricing, checkout, payment, Token, risk, or purchase-limit controls.

This includes, without limitation:

1. manipulating client-side code;
2. altering checkout requests;
3. forging payment metadata;
4. bypassing cart limits;
5. splitting purchases to avoid risk controls;
6. misrepresenting Buyer identity;
7. using unauthorised payment methods;
8. attempting to generate unauthorised Token credits;
9. abusing import or recovery tools; or
10. otherwise interfering with payment-linked workflows.

DiscPay may suspend, restrict, reverse, or investigate activity that appears to bypass or abuse checkout controls.

9.8 Store availability

DiscPay does not guarantee that Store Pages will always be available, accessible, updated, error-free, or compatible with every device, browser, country, payment method, or Discord environment.

Store availability may be affected by maintenance, hosting issues, payment-processor issues, Discord issues, Server configuration, domain issues, SSL or certificate issues, security controls, abuse prevention, legal restrictions, or other technical or operational factors.

DiscPay may disable or restrict a Store Page where necessary to protect Buyers, Server Owners, payment integrity, legal compliance, Discord compliance, Stripe compliance, security, or platform integrity.

9.9 Store access and Buyer eligibility

DiscPay may restrict access to a Store Page, Checkout, Token purchase, or related feature based on country, Server membership, Discord OAuth status, user identity, payment method, fraud risk, abuse risk, Server status, Stripe status, or other eligibility requirements.

DiscPay may add, remove, or modify access requirements over time.

A Buyer is not guaranteed the ability to access every Store, purchase Tokens for every Server, or use every payment method.

9.10 Server membership checks

DiscPay may support or require Discord OAuth, Server membership checks, account linking, or other identity checks before allowing a Buyer to access a Store, purchase Tokens, view balances, redeem Tokens, or request Rewards.

These checks may be used to reduce fraud, prevent mistaken purchases, enforce Server-specific Token rules, support fulfilment, or protect Server Owners and Buyers.

DiscPay does not guarantee that membership checks, OAuth checks, role checks, or Discord identity checks will always be accurate, available, instant, or error-free.

9.11 Store suspension

DiscPay may suspend, disable, hide, remove, or restrict a Store Page at any time if DiscPay believes that:

1. the Server is no longer eligible;
2. the Server Owner has not completed required onboarding;
3. Stripe status is incomplete, restricted, rejected, or unsafe;
4. the Store contains prohibited or misleading content;
5. the Server is engaged in Prohibited Use;
6. payment activity creates fraud, chargeback, legal, or security risk;
7. Discord or Stripe compliance is at risk;
8. fees are unpaid;
9. ownership is disputed or has changed;
10. the Store creates reputational risk for DiscPay; or
11. suspension is otherwise necessary to protect the platform.

Store suspension does not necessarily delete records, Token Balances, logs, transaction history, or Server configuration.

9.12 Store content and intellectual property

A Server Owner must not use a Store Page to display content they do not have the right to use.

This includes, without limitation, names, logos, icons, artwork, trademarks, copyrighted material, branding, images, text, or other content belonging to another person or organisation.

A Server Owner is responsible for ensuring that any Server name, Server icon, description, Reward information, or other Store content does not infringe the rights of others.

DiscPay may remove or restrict content if DiscPay believes it may infringe intellectual property rights, mislead Buyers, violate law, breach platform rules, or expose DiscPay to risk.

9.13 No guarantee of sales or revenue

DiscPay does not guarantee that a Server Owner will make sales, receive revenue, attract Buyers, retain Buyers, avoid chargebacks, avoid refunds, avoid disputes, or successfully monetise their Server.

Any examples, estimates, projections, analytics, pricing suggestions, or performance information provided by DiscPay are for informational purposes only and do not guarantee results.

Server Owners are responsible for their own business decisions, pricing, community management, fulfilment, legal compliance, marketing, and Buyer relationships.

9.14 Buyer review before purchase

Buyers are responsible for reviewing the relevant Store Page, Token bundle, price, Server, notices, and any available Reward information before making a purchase.

A Buyer should not purchase Tokens if they do not understand that Tokens are server-specific, non-transferable, not cash-redeemable, and dependent on the relevant Server’s continued use of DiscPay and Reward availability.

A Buyer should also understand that Rewards are offered and fulfilled by the Server Owner, not by DiscPay, unless DiscPay expressly states otherwise.

9.15 Store and checkout records

DiscPay may create and retain Store records, checkout records, cart records, transaction records, Token credit records, Stripe references, import records, logs, metadata, and related technical records.

These records may be used to operate Store Pages, support checkout, credit Tokens, prevent duplicate credits, investigate disputes, support refunds or chargebacks, enforce these Terms, improve reliability, and maintain platform integrity.

Further provisions relating to data, logs, privacy, and retention are set out later in these Terms and in DiscPay’s Privacy Policy.

10. Tokens And Token Balances

10.1 Nature of Tokens

Tokens are server-specific internal accounting units used by DiscPay to track a Buyer’s eligibility to request, redeem, or receive Rewards configured by a Server Owner.

Tokens exist only within the DiscPay system and only in relation to the specific Server for which they are purchased, credited, granted, adjusted, or otherwise recorded.

Tokens are not money. Tokens are not electronic money. Tokens are not stored value. Tokens are not cryptocurrency. Tokens are not securities. Tokens are not financial instruments. Tokens are not gift cards. Tokens are not vouchers. Tokens are not legal tender. Tokens are not deposits. Tokens are not bank balances. Tokens are not payment account balances. Tokens are not cash-equivalent value.

A Token Balance is an internal technical record used by DiscPay to support Server-specific Reward workflows.

10.2 Server-specific Tokens

Tokens are specific to the Server for which they are purchased, credited, granted, or recorded.

A Buyer who purchases or receives Tokens for one Server may not use those Tokens in another Server unless DiscPay expressly provides a supported feature allowing this and updates these Terms or applicable policies accordingly.

Server-specific Tokens help ensure that each Server Owner remains responsible for their own Rewards, Token workflows, pricing, fulfilment, disputes, and Server economy.

DiscPay does not operate a universal Token economy across all Servers.

10.3 No transfer between users

Tokens may not be transferred, sold, gifted, traded, assigned, exchanged, loaned, rented, or otherwise moved from one user to another unless DiscPay expressly provides a supported feature allowing this.

A Buyer must not attempt to sell, trade, transfer, or exchange Tokens with another user outside DiscPay.

A Server Owner, Operator, Staff member, or Buyer must not create informal or unsupported systems that allow Tokens to be transferred between users in a way that bypasses DiscPay’s intended functionality, payment controls, fraud controls, or Server-specific Token rules.

DiscPay may reverse, restrict, freeze, suspend, or remove Token Balances or related features if it believes Tokens have been transferred, traded, sold, or exchanged in an unsupported or abusive way.

10.4 No transfer between Servers

Tokens may not be transferred between Servers.

A Buyer may not move Tokens from one Server to another Server.

A Server Owner may not treat Tokens purchased for another Server as valid for their own Server unless DiscPay expressly supports such a feature.

DiscPay may reject, reverse, restrict, or ignore any attempt to transfer Tokens between Servers.

10.5 No cash-out or redemption for money

Tokens cannot be redeemed for cash through DiscPay.

A Buyer is not entitled to withdraw money from DiscPay in exchange for Tokens.

A Server Owner must not use DiscPay to offer cash-out, cash redemption, cash-equivalent redemption, money transfer, stored-value redemption, cryptocurrency redemption, gift-card redemption, or other financial redemption of Tokens.

DiscPay does not support, facilitate, approve, or guarantee any external arrangement in which a user or Server Owner attempts to exchange Tokens for money, cryptocurrency, gift cards, financial assets, or cash-equivalent value outside DiscPay.

Any such external arrangement is outside DiscPay, unsupported by DiscPay, and may result in suspension, restriction, termination, Token reversal, Store disabling, or other enforcement action.

10.6 No ownership interest or investment value

Tokens do not give a Buyer any ownership interest in DiscPay, a Server, a Server Owner, a business, a project, a Reward, a community, or any asset.

Tokens are not investments and must not be marketed, described, or used as investments.

A Server Owner must not suggest that Tokens will increase in value, generate profit, provide financial return, represent shares, represent debt, represent ownership, represent an investment opportunity, or provide any right to revenue, dividends, resale profit, financial yield, or appreciation.

DiscPay may restrict or suspend any Server that describes or uses Tokens in a way that creates financial, investment, securities, crypto-asset, e-money, stored-value, or regulatory risk.

10.7 Token purchases

A Buyer may purchase Tokens through a DiscPay-supported Store, Checkout, or payment flow.

Token purchases may be subject to supported countries, payment-method availability, Stripe status, Store status, Server eligibility, risk controls, checkout limits, fraud checks, Discord OAuth or membership checks, and other restrictions.

A Token purchase is not complete merely because a Buyer begins a checkout process. DiscPay may require confirmation from Stripe or another supported payment processor before Tokens are credited.

A payment may be delayed, declined, reviewed, reversed, refunded, disputed, or otherwise affected by Stripe, payment processors, banks, card networks, payment methods, risk systems, or applicable law.

10.8 Token crediting

After a successful payment, DiscPay may credit Tokens to the Buyer’s Token Balance for the relevant Server.

Token crediting may depend on payment confirmation, transaction records, queue processing, Stripe events, import tools, duplicate-detection systems, Discord identifiers, Server identifiers, Buyer identifiers, and other technical requirements.

DiscPay does not guarantee instant Token crediting.

If Token crediting is delayed, missing, duplicated, incorrect, or otherwise affected by technical failure, Stripe delay, queue failure, Discord issue, Server configuration issue, or other cause, the relevant transaction may require retry, import, manual review, support assistance, or correction.

10.9 Token Balance

A Token Balance is the number of Tokens recorded by DiscPay for a Buyer in relation to a specific Server.

A Token Balance does not represent money held by DiscPay.

A Token Balance does not create a right to withdraw cash, demand payment, receive a refund from DiscPay, or transfer value to another user or Server.

A Token Balance may be used only within the supported DiscPay workflows for the relevant Server, subject to these Terms, the Server Owner’s Reward configuration, Server access, DiscPay’s technical functionality, and applicable restrictions.

10.10 No guaranteed availability of Tokens

DiscPay aims to maintain accurate Token Balance records, but Token availability may be affected by technical failures, maintenance, security controls, suspected abuse, disputes, chargebacks, refunds, Stripe issues, Discord issues, Server suspension, Store suspension, enforcement action, ownership changes, or other operational issues.

DiscPay may temporarily restrict, freeze, hide, delay, or disable access to Token Balances or Token redemption while investigating issues, performing maintenance, applying corrections, preventing abuse, or enforcing these Terms.

10.11 No Token expiry by default

Unless otherwise stated by DiscPay or configured through a supported feature, Tokens do not expire by default.

However, the absence of a default expiry date does not guarantee that Tokens will always be usable.

Token usability may depend on:

1. the relevant Server continuing to use DiscPay;
2. the relevant Server remaining available on Discord;
3. the relevant Server not being suspended by DiscPay;
4. the relevant Store or Reward workflow remaining active;
5. the Buyer retaining access to the relevant Server;
6. the relevant Rewards remaining available;
7. DiscPay’s continued ability to provide the service;
8. Stripe and Discord functionality;
9. compliance with these Terms; and
10. applicable law and platform restrictions.

10.12 Tokens after leaving or being banned from a Server

If a Buyer leaves a Server or is banned, removed, kicked, restricted, muted, or otherwise prevented from accessing a Server, their Token Balance for that Server may remain recorded by DiscPay.

However, the Buyer may be unable to use, redeem, request Rewards with, or otherwise benefit from those Tokens while they lack access to the relevant Server or while Server-specific restrictions apply.

DiscPay is not responsible for a Server Owner’s moderation decisions, including bans, removals, access restrictions, role removals, channel restrictions, or community-rule enforcement.

If a Buyer later rejoins the Server or is unbanned, their Token Balance may remain available, subject to DiscPay’s records, Server status, enforcement actions, technical limitations, and these Terms.

10.13 Tokens after Server disconnection

If a Server stops using DiscPay, disconnects DiscPay, has payment features disabled, has its Store suspended, or otherwise becomes inactive, DiscPay may preserve Token Balances, transaction records, logs, and related records for that Server.

Preserving Token records does not guarantee that Tokens will remain usable, that the Server will reconnect, that Rewards will remain available, that the Server Owner will continue honouring previous Reward structures, or that DiscPay will be able to restore full functionality.

If the Server later reconnects or resumes using DiscPay, DiscPay may attempt to preserve or restore relevant Token records where technically and operationally possible.

DiscPay may require re-onboarding, Server Owner verification, Stripe reconnection, configuration review, or other steps before Tokens may be used again.

10.14 Tokens after Server ownership change

If Server ownership changes, DiscPay may preserve existing Token Balances and transaction records, but may require the new Server Owner to complete onboarding before Token purchases, redemption, Reward workflows, or other features continue.

Preservation of Token Balances after an ownership change does not guarantee that the new Server Owner will offer the same Rewards, honour informal promises made by the previous Server Owner, maintain the same catalogue, maintain the same pricing, or operate the Server in the same way.

DiscPay may restrict or freeze Token use during ownership review, re-onboarding, Stripe reconnection, or dispute investigation.

10.15 Tokens and Rewards

Tokens may be used to request, redeem, or become eligible for Rewards configured by the relevant Server Owner.

The number of Tokens required for a Reward, the availability of a Reward, the description of a Reward, the method of fulfilment, the timing of fulfilment, and any Server-specific conditions are controlled by the Server Owner and their authorised Operators or Staff, unless DiscPay expressly states otherwise.

DiscPay does not guarantee that any particular Reward will remain available.

A Server Owner may change, remove, replace, pause, restrict, or update Rewards, subject to these Terms, applicable law, and any specific commitments made to Buyers.

10.16 No guaranteed Reward value

Tokens do not have a fixed monetary value, resale value, cash value, market value, or guaranteed Reward value.

Any Token bundle price, Reward cost, or Server-specific redemption rate is part of the relevant Server’s configuration or DiscPay-supported pricing system and does not mean that Tokens can be exchanged for cash or have independent monetary value.

A Server Owner must not mislead Buyers by suggesting that Tokens have guaranteed cash value, resale value, investment value, or universal value outside the relevant Server.

10.17 Promotional or manually granted Tokens

A Server Owner, Operator, Staff member, or DiscPay may grant, credit, adjust, or award Tokens manually or promotionally where supported.

Promotional or manually granted Tokens may be subject to additional restrictions, review, reversal, correction, or removal.

Unless expressly stated otherwise, promotional or manually granted Tokens have the same non-cash, non-transferable, server-specific nature as purchased Tokens.

Promotional Tokens do not entitle a Buyer to cash, refunds, compensation, or replacement value.

10.18 Incorrect, duplicate, or unauthorised Tokens

A Buyer is not entitled to keep Tokens that were credited incorrectly, duplicated, granted without authorisation, generated through abuse, credited because of a system error, credited because of a failed payment, credited because of a refunded payment, credited because of a reversed payment, credited because of a disputed payment, or credited because of fraudulent activity.

DiscPay may correct, reverse, freeze, restrict, remove, or adjust Tokens where DiscPay believes that the Token Balance is incorrect, duplicated, unauthorised, abusive, fraudulent, or inconsistent with transaction records.

DiscPay may also restrict redemption while investigating suspected incorrect or unauthorised Token credits.

10.19 Token records and transaction integrity

DiscPay may maintain Token records, transaction records, balance records, adjustment records, import records, refund records, dispute records, fulfilment records, logs, and other technical records to support Token integrity.

These records may be used to:

1. credit Tokens;
2. prevent duplicate credits;
3. correct errors;
4. support refund or chargeback handling;
5. investigate abuse;
6. investigate fraud;
7. support Server Owner records;
8. respond to support requests;
9. preserve balance continuity if a Server reconnects;
10. enforce these Terms; and
11. protect DiscPay’s platform integrity.

DiscPay may rely on its internal records, Stripe records, Discord identifiers, logs, support records, and other available evidence when determining Token Balance issues.

10.20 No right to demand manual adjustment

A Buyer, Server Owner, Operator, or Staff member does not have an automatic right to demand that DiscPay manually adjust a Token Balance.

DiscPay may review Token Balance issues, but is not required to make a correction unless DiscPay determines that a correction is appropriate.

Server Owners may have tools to adjust Token Balances within their Server, but such adjustments remain subject to these Terms, logs, permissions, dispute handling, and enforcement review.

10.21 Token misuse

Token misuse includes, without limitation:

1. attempting to generate Tokens without valid payment or authorisation;
2. exploiting bugs to increase Token Balances;
3. using duplicate payments or imports to obtain extra Tokens;
4. selling or trading Tokens outside DiscPay;
5. attempting to cash out Tokens;
6. using Tokens for prohibited goods or services;
7. using Tokens to facilitate fraud, scams, gambling, or illegal activity;
8. manipulating Token records;
9. abusing refund or chargeback processes after using Tokens;
10. misleading Buyers about Token value or transferability; or
11. otherwise using Tokens in a way that violates these Terms.

DiscPay may suspend, restrict, reverse, freeze, remove, or investigate Tokens, Token Balances, Users, Stores, Rewards, or Servers involved in suspected Token misuse.

11. Token Visibility, Adjustments, And Corrections

11.1 Buyer visibility

A Buyer may be able to view their own Token Balance for a Server through supported DiscPay commands, Store interfaces, dashboards, Discord workflows, or other supported tools.

DiscPay does not guarantee that balance displays will always be instant, available, accurate in real time, or accessible through every interface.

If there is a difference between a displayed balance and DiscPay’s internal records, DiscPay may rely on its internal records, Stripe records, transaction logs, adjustment logs, and other available evidence to determine the correct balance.

11.2 Server Owner, Operator, and Staff visibility

Server Owners, Operators, and Staff may be able to view Token Balances, transaction records, reward requests, fulfilment records, adjustment history, logs, or other information depending on their permissions.

Server Owners are responsible for granting such visibility only to trusted users with a legitimate operational reason to access the information.

Users with access to Token or transaction information must not misuse, disclose, sell, publish, exploit, or access such information for unauthorised purposes.

11.3 Public or Server-visible Token activity

Certain Token-related activity may be visible within a Server depending on the features enabled, permissions granted, workflows used, and settings configured.

For example, DiscPay may support or later support purchase announcements, reward request notices, fulfilment tickets, leaderboards, public acknowledgements, balance-related displays, or other Server-visible features.

Server Owners are responsible for understanding and configuring visibility settings appropriately.

Where Token-related information is made visible to other Server members, Server Owners should ensure that Buyers are given appropriate notice and that visibility is not misleading, abusive, harassing, or unfair.

DiscPay may restrict or disable public visibility features where they create privacy, safety, harassment, fraud, payment, or platform risk.

11.4 Balance adjustments by Server Owners and authorised users

Server Owners, Operators, or Staff may be able to add, remove, or adjust Tokens if they have been granted the required permissions.

Any balance adjustment must be accurate, authorised, justified, and consistent with these Terms.

Balance adjustments must not be used fraudulently, maliciously, deceptively, unfairly, or for personal gain.

The Server Owner is responsible for balance adjustments made by authorised users for their Server.

11.5 Balance adjustments by DiscPay

DiscPay may add, remove, freeze, reverse, restrict, or adjust Tokens where DiscPay believes it is necessary or appropriate.

This may include adjustments relating to:

1. duplicate credits;
2. failed payments;
3. refunded payments;
4. reversed payments;
5. chargebacks;
6. payment disputes;
7. fraudulent payments;
8. unauthorised payments;
9. system errors;
10. queue processing errors;
11. import errors;
12. incorrect manual adjustments;
13. abuse of permissions;
14. ownership changes;
15. legal or payment-processor requirements;
16. Prohibited Use;
17. technical inconsistencies; or
18. enforcement of these Terms.

DiscPay may make such adjustments with or without advance notice where necessary to protect payment integrity, Buyer protection, Server integrity, legal compliance, fraud prevention, or platform security.

11.6 Token freezing

DiscPay may temporarily freeze, restrict, or disable Token redemption, Token editing, Token purchasing, or Token-related workflows for a Buyer, Server, Store, Reward, or Transaction.

This may occur during investigation of fraud, chargebacks, refunds, ownership changes, duplicate credits, suspicious activity, permission abuse, Prohibited Use, legal risk, Stripe risk, Discord risk, or other platform concerns.

A freeze does not necessarily mean that Tokens have been removed.

A freeze may remain in place until DiscPay determines that the issue has been resolved or that further action is appropriate.

11.7 Effect of refunds and disputes on Tokens

If a payment is refunded, reversed, disputed, charged back, found fraudulent, found unauthorised, or otherwise invalidated, DiscPay may remove, reverse, freeze, or adjust Tokens connected to that payment.

This may apply even if the Buyer has already used some or all of the Tokens, requested a Reward, received a Reward, or caused the Server Owner or Staff to begin fulfilment.

If Tokens connected to a refunded, reversed, or disputed payment have already been used, DiscPay may record a negative adjustment, restrict future use, support Server Owner enforcement, suspend the Buyer’s access to DiscPay features for that Server, or take other appropriate action.

11.8 Effect of fulfilled Rewards on Token corrections

If a Buyer receives a Reward and the related payment is later refunded, reversed, disputed, charged back, or found fraudulent, DiscPay may still remove or adjust the related Tokens.

DiscPay may not be able to reverse a Reward already fulfilled by a Server Owner, especially where the Reward was external, manual, digital, custom, consumed, or otherwise not technically reversible.

The Server Owner remains responsible for deciding what action to take regarding fulfilled Rewards, subject to applicable law, Stripe rules, Discord rules, and these Terms.

11.9 Negative balances

DiscPay may support, record, or display a negative Token Balance where Tokens have been used before a refund, reversal, chargeback, dispute, fraud finding, duplicate correction, or other adjustment.

A negative balance may restrict further purchases, redemption, Reward requests, or access to DiscPay features until resolved.

DiscPay is not required to offer a negative balance feature, but may use internal records to track unresolved Token deficits or disputed activity.

11.10 Logs of adjustments

DiscPay may log Token adjustments, including who made the adjustment, when it was made, the amount changed, the reason where available, related transactions, related Rewards, related disputes, and other relevant metadata.

Logs may be visible to Server Owners, authorised Operators, authorised Staff, DiscPay Admins, or other users where supported and appropriate.

Logs may be used to investigate disputes, support refund handling, detect abuse, correct errors, enforce permissions, and protect platform integrity.

11.11 Disputing a Token Balance

A Buyer who believes their Token Balance is incorrect should use the available support process, Server support route, ticket system, or other supported method.

Depending on the issue, the Buyer may need to contact the Server Owner, the relevant Staff, Stripe, their payment provider, or DiscPay.

DiscPay may require transaction references, Discord identifiers, payment information, screenshots, support records, or other information to investigate a Token Balance issue.

DiscPay is not required to adjust a Token Balance where the available records do not support the requested adjustment.

11.12 Server Owner balance review

Server Owners should regularly review Token records, transaction records, fulfilment records, and adjustment logs for their Server.

Server Owners are responsible for identifying suspected staff misuse, fulfilment inconsistencies, refund-related issues, chargeback-related issues, incorrect manual adjustments, and other operational problems.

DiscPay may provide logs or tools to assist with review, but DiscPay does not guarantee that every issue will be detected automatically.

11.13 No compensation for Token restrictions

Unless required by applicable law, DiscPay is not required to provide cash compensation, replacement value, substitute Tokens, alternative Rewards, or other compensation because Tokens are restricted, frozen, delayed, adjusted, removed, or made temporarily unusable in accordance with these Terms.

This does not limit any mandatory consumer rights that may apply.

11.14 Token integrity takes priority

DiscPay may prioritise Token integrity, payment integrity, fraud prevention, security, compliance, and platform protection over immediate Token availability.

Where DiscPay believes that allowing Token purchases, Token redemption, balance editing, Reward requests, or fulfilment workflows to continue would create unacceptable risk, DiscPay may restrict those features until the risk is resolved.

11.15 Survival of Token records

Token records, transaction records, adjustment records, logs, and related metadata may survive Server disconnection, Server suspension, Buyer suspension, ownership changes, Store suspension, or termination of access where retention is necessary for payment integrity, fraud prevention, legal compliance, dispute handling, accounting, security, balance restoration, or enforcement of these Terms.

Further provisions relating to data retention and privacy are set out later in these Terms and in DiscPay’s Privacy Policy.

12. Rewards, Catalogues, And Fulfilment

12.1 Reward tools

DiscPay may provide tools that allow Server Owners to create, configure, display, manage, or process Rewards connected to a Server.

These tools may include, without limitation:

1. reward catalogues;
2. Discord commands;
3. Store-related notices;
4. ticket creation;
5. fulfilment workflows;
6. Operator or Staff tools;
7. transaction records;
8. Token redemption records;
9. webhook, websocket, API, or notification systems;
10. logs and audit records; and
11. other supported reward-management features.

DiscPay may add, remove, modify, restrict, or replace reward-related tools at any time for product, operational, legal, fraud-prevention, security, payment, platform-compliance, or user-safety reasons.

12.2 Server Owner responsibility for Rewards

The Server Owner is responsible for all Rewards offered, listed, described, advertised, requested, redeemed, delivered, or fulfilled through or in connection with their Server.

This responsibility includes, without limitation:

1. deciding what Rewards are offered;
2. ensuring Rewards are lawful;
3. ensuring Rewards comply with these Terms;
4. ensuring Rewards comply with Discord’s rules;
5. ensuring Rewards comply with Stripe’s rules;
6. ensuring Rewards do not violate third-party rights or third-party platform terms;
7. accurately describing Rewards;
8. setting any Token cost or eligibility conditions;
9. honouring fulfilment commitments;
10. training Operators and Staff;
11. handling Buyer support;
12. handling fulfilment disputes;
13. maintaining accurate fulfilment records; and
14. removing unavailable, misleading, unlawful, or prohibited Rewards.

DiscPay is not responsible for a Server Owner’s Reward choices, Reward descriptions, Reward quality, Reward availability, fulfilment delays, Staff conduct, or failure to provide Rewards, except to the limited extent directly caused by DiscPay’s own system error.

12.3 Rewards are offered by Server Owners

Unless DiscPay expressly states otherwise in writing, Rewards are offered by the relevant Server Owner, not by DiscPay.

A Buyer who uses Tokens to request or redeem a Reward is dealing with the relevant Server Owner for the provision, quality, timing, support, and fulfilment of that Reward.

DiscPay provides infrastructure to record, notify, route, or support the Reward workflow. DiscPay does not create, sell, provide, supervise, inspect, guarantee, or fulfil Server Rewards unless expressly stated otherwise.

12.4 Reward descriptions

Server Owners must ensure that Reward descriptions are accurate, complete, lawful, and not misleading.

A Reward description should clearly describe what the Buyer can expect to receive, any important limits, any eligibility requirements, any delivery method, any estimated delivery time, any relevant restrictions, and any other material information that a reasonable Buyer would need before redeeming Tokens.

A Server Owner must not exaggerate, misrepresent, conceal, or omit important information about a Reward.

DiscPay may remove, disable, restrict, or require changes to Reward descriptions that DiscPay believes are misleading, unlawful, prohibited, risky, infringing, abusive, unclear, or otherwise unsuitable.

12.5 Reward availability

A Reward may be unavailable, limited, paused, removed, changed, or replaced.

Server Owners are responsible for keeping Reward availability accurate and up to date.

If a Reward becomes unavailable after a Buyer has requested or redeemed it, the Server Owner is responsible for handling the issue with the Buyer, which may include providing the Reward, offering an alternative, restoring Tokens, cancelling the request, or taking another appropriate action.

DiscPay does not guarantee that any specific Reward will remain available.

12.6 Changes to Rewards

Server Owners may change, remove, pause, restrict, or replace Rewards, subject to these Terms, applicable law, payment-processor rules, Discord rules, and any specific commitments made to Buyers.

Server Owners must not change Rewards in a way that is deceptive, unfair, fraudulent, or designed to avoid fulfilment obligations after Buyers have already purchased or redeemed Tokens.

Where a Buyer has already redeemed Tokens for a specific Reward, the Server Owner should handle any change fairly and consistently with the Reward description, Server rules, applicable law, and these Terms.

12.7 Reward catalogues

A Reward Catalogue may be made available through Discord commands, dashboards, Store Pages, ticket systems, bot messages, web interfaces, or other supported systems.

A Reward Catalogue may show available Rewards, Token costs, descriptions, fulfilment instructions, conditions, restrictions, or related information.

Server Owners are responsible for configuring and maintaining their Reward Catalogues.

DiscPay may restrict, suspend, remove, or modify Reward Catalogue functionality if necessary to protect Buyers, Server Owners, payment integrity, legal compliance, Discord compliance, Stripe compliance, security, or platform integrity.

12.8 Manual fulfilment

DiscPay may support manual fulfilment workflows.

Manual fulfilment may involve creating a ticket, sending a Discord notification, notifying Staff, recording a request, posting a transaction event, using a webhook or websocket, or otherwise alerting authorised users that a Buyer has purchased Tokens or requested a Reward.

Where fulfilment is manual, the Server Owner and their authorised Operators or Staff are responsible for reviewing the request, verifying the relevant records, communicating with the Buyer where appropriate, and providing the Reward.

DiscPay does not guarantee that Staff will see, respond to, or correctly handle a manual fulfilment request.

12.9 Automated or semi-automated fulfilment

DiscPay may support automated or semi-automated fulfilment features, including integrations, webhooks, websockets, API endpoints, role assignment tools, notifications, or other systems.

Automated or semi-automated fulfilment may depend on Discord permissions, bot availability, Server configuration, third-party systems, API availability, Staff configuration, webhook endpoints, internet connectivity, payment records, Token records, and other technical factors.

DiscPay does not guarantee that automated or semi-automated fulfilment will always be successful, instant, uninterrupted, or error-free.

Server Owners remain responsible for monitoring fulfilment, handling failures, reviewing logs, and providing support to Buyers.

12.10 Tickets and support workflows

DiscPay may create or support ticket-based workflows for Reward requests, fulfilment issues, transaction issues, or Buyer support.

A ticket may include information such as Buyer identifiers, Server identifiers, Token amounts, Transaction references, requested Rewards, timestamps, Staff actions, fulfilment status, notes, and related metadata.

Server Owners and authorised Staff are responsible for handling tickets appropriately, responding in a reasonable manner, and not misusing Buyer information.

DiscPay may access, preserve, restrict, review, or use ticket records where necessary for support, security, fraud prevention, dispute handling, enforcement, legal compliance, or platform integrity.

12.11 Staff fulfilment conduct

Operators and Staff involved in fulfilment must act within the permissions granted to them and in accordance with these Terms.

Operators and Staff must not:

1. falsely mark Rewards as fulfilled;
2. ignore Reward requests without proper reason;
3. mislead Buyers about fulfilment;
4. request unauthorised additional payment outside DiscPay;
5. remove Tokens to avoid fulfilment;
6. use fulfilment tools for harassment or retaliation;
7. share Buyer data without authority;
8. conceal failed fulfilment;
9. manipulate fulfilment records;
10. create false support records; or
11. otherwise misuse DiscPay systems.

The Server Owner is responsible for supervising Staff and correcting fulfilment problems caused by authorised users.

12.12 Buyer responsibility when requesting Rewards

A Buyer is responsible for reviewing the relevant Reward description, Server rules, Token cost, eligibility requirements, delivery method, and any applicable restrictions before requesting or redeeming a Reward.

A Buyer must provide accurate information where required for fulfilment.

A Buyer must not request Rewards fraudulently, use another person’s account, abuse support workflows, harass Staff, submit false claims, misuse chargebacks, exploit bugs, or attempt to receive Rewards without valid Tokens or valid payment.

DiscPay may restrict, suspend, or investigate Buyers who abuse Reward workflows.

12.13 No guarantee of Reward quality

DiscPay does not guarantee the quality, suitability, legality, availability, timing, safety, usefulness, accuracy, compatibility, performance, or outcome of any Reward offered by a Server Owner.

Rewards may be digital, manual, subjective, creative, custom, access-based, role-based, community-based, or dependent on third-party platforms.

A Buyer accepts that Rewards offered by Server Owners may vary in quality, scope, delivery time, and availability.

Any dispute about Reward quality or fulfilment should first be raised with the relevant Server Owner or Staff, unless the issue concerns DiscPay’s own systems.

12.14 Digital and custom Rewards

Some Rewards may be digital, custom, creative, access-based, or manually produced.

Examples may include art, code projects, SaaS access, Minecraft SMP access, Discord roles, server access, community perks, or other non-physical digital benefits.

Digital or custom Rewards may be difficult or impossible to return, reverse, revoke, or inspect after delivery.

The Server Owner is responsible for setting clear expectations around digital or custom Rewards, including scope, delivery time, revision limits, usage rights, support limits, access duration, and any relevant restrictions.

12.15 Access-based Rewards

Some Rewards may involve access to a Server, channel, role, Minecraft server, software tool, private group, or other access-controlled environment.

Access-based Rewards may depend on Discord permissions, third-party systems, account status, moderation decisions, technical availability, Server rules, or other conditions.

DiscPay does not guarantee continued access to any Server, role, channel, third-party platform, Minecraft server, SaaS tool, or community space.

Server Owners remain responsible for access-based Reward configuration and fulfilment.

12.16 No physical products

Unless DiscPay expressly approves otherwise in writing, DiscPay must not be used to sell, arrange, redeem, or fulfil physical products.

Server Owners must not use Rewards, Store Pages, Token systems, or DiscPay workflows to sell or distribute physical goods, shipped items, tangible products, or other physical merchandise.

This restriction is intended to reduce fulfilment risk, shipping risk, consumer-law complexity, fraud risk, tax complexity, payment risk, and platform risk.

12.17 No prohibited Rewards

Server Owners must not offer Rewards that constitute Prohibited Use.

This includes, without limitation, illegal goods or services, gift cards, cash-equivalent items, cryptocurrency redemption, financial products, gambling, paid raffles, loot boxes, chance-based paid rewards, prohibited adult goods or services, regulated goods or services without approval, malware, hacking services, account sales, stolen goods, or services intended to violate another platform’s terms.

Further provisions relating to Prohibited Use are set out later in these Terms.

12.18 External fulfilment

Some Rewards may be fulfilled outside Discord or outside DiscPay, such as through third-party platforms, external websites, SaaS tools, Minecraft servers, custom files, email delivery, or other external systems.

Where Rewards are fulfilled externally, the Server Owner remains responsible for the external fulfilment process, including accuracy, delivery, access, support, third-party terms, privacy obligations, and legal compliance.

DiscPay is not responsible for external systems, external accounts, external delivery, external access, external files, external software, or third-party platform failures.

12.19 Fulfilment records

DiscPay may record fulfilment-related information, including Reward requests, Token costs, Buyer identifiers, Server identifiers, Staff actions, ticket activity, fulfilment status, timestamps, notes, logs, and related metadata.

Fulfilment records may be used to support Buyer requests, Server Owner review, Staff accountability, dispute handling, Token corrections, refund or chargeback review, fraud prevention, enforcement, and platform integrity.

Fulfilment records may not capture every action and may be subject to technical limitations, permission settings, retention periods, and privacy rules.

12.20 No guarantee of Server continuity

DiscPay does not guarantee that a Server will remain active, available, moderated, accessible, or connected to DiscPay.

A Server may be deleted, disabled, banned, transferred, abandoned, suspended, restricted, disconnected, or otherwise made unavailable by Discord, the Server Owner, DiscPay, or another relevant party.

If a Server becomes unavailable, Rewards connected to that Server may become unavailable or unusable.

DiscPay may preserve records where appropriate, but does not guarantee that Rewards can be restored, recreated, or fulfilled after Server unavailability.

12.21 Server rules and moderation

Server Owners control their own Server rules and moderation decisions, subject to these Terms and applicable third-party rules.

DiscPay is not responsible for Server moderation decisions, including bans, kicks, mutes, role removals, channel restrictions, access restrictions, or community-rule enforcement.

A Buyer who is banned, removed, or restricted by a Server Owner may be unable to use Tokens or receive Rewards for that Server, even if the Token Balance remains recorded.

Server Owners should apply moderation decisions fairly and should not use moderation tools to avoid legitimate fulfilment obligations.

12.22 DiscPay review of Rewards

DiscPay may review, restrict, suspend, remove, hide, disable, or require changes to any Reward, Reward Catalogue, fulfilment workflow, Store content, or related feature if DiscPay believes it may violate these Terms, violate law, violate Discord rules, violate Stripe rules, mislead Buyers, create fraud risk, create chargeback risk, create security risk, create reputational risk, or otherwise harm DiscPay, Buyers, Server Owners, or third parties.

DiscPay may act with or without prior notice where immediate action is necessary.

12.23 No obligation to monitor all Rewards

DiscPay may review Rewards or Server activity, but is not required to monitor every Server, Reward, Reward Catalogue, ticket, fulfilment action, Staff action, Buyer request, or external fulfilment process.

The absence of review or enforcement by DiscPay does not mean that a Reward is approved, lawful, compliant, safe, or guaranteed.

DiscPay may take enforcement action later if an issue is discovered.

12.24 Buyer reports

Buyers may report suspected failed fulfilment, misleading Reward descriptions, prohibited Rewards, fraud, abuse, or other issues through available support routes.

DiscPay may review such reports, but does not guarantee that it will resolve every dispute, provide refunds, force fulfilment, reverse external delivery, or take action requested by the Buyer.

DiscPay may use reports to investigate Servers, restrict Stores, suspend Rewards, preserve evidence, enforce these Terms, or identify platform risk.

12.25 Server Owner support responsibility

Server Owners are responsible for providing reasonable support to Buyers regarding Rewards, fulfilment, Server-specific questions, Token redemption, access issues, and Reward-related disputes.

DiscPay may provide infrastructure, records, logs, or support tools, but DiscPay does not replace the Server Owner’s responsibility to support their own Buyers.

Failure by a Server Owner to provide reasonable support may result in Store restriction, Server suspension, enforcement action, or termination of access.

13. Refunds, Disputes, And Chargebacks

13.1 Scope of this section

This section explains how DiscPay treats refunds, disputes, chargebacks, reversals, failed payments, and related Token or Reward issues.

This section should be read together with any separate Refund and Chargeback Policy published by DiscPay.

If DiscPay publishes a separate Refund and Chargeback Policy, that policy may provide additional detail, but these Terms will continue to apply.

13.2 Payments handled by Stripe

Payments are processed by Stripe or another supported payment processor.

DiscPay does not hold Buyer funds and does not control all aspects of refunds, chargebacks, disputes, payment reversals, fraud reviews, bank decisions, card-network rules, payment-method rules, or Stripe decisions.

A refund, chargeback, dispute, reversal, or payment issue may need to be handled through Stripe, the relevant Server Owner, the Buyer’s payment method, a bank, a card network, or another payment provider.

13.3 Server Owner responsibility for refunds

Unless DiscPay expressly states otherwise in writing, the Server Owner is responsible for refund-related decisions connected to the Rewards, products, services, access, roles, benefits, or other items they offer through or in connection with their Server.

The Server Owner is responsible for handling Buyer complaints, failed fulfilment claims, Reward disputes, incorrect Reward descriptions, and other Server-specific issues.

DiscPay may provide records, logs, transaction references, Token data, import tools, or other infrastructure to support refund-related workflows, but DiscPay does not become responsible for refunds merely because it provides such tools.

13.4 General no-refund position

Unless required by applicable law, Stripe rules, payment-method rules, or a specific refund decision by the relevant Server Owner, Token purchases are generally not refundable after Tokens have been credited or used.

This position reflects that Tokens are server-specific digital records, may be used quickly, may trigger manual or automated fulfilment, may result in access-based or digital Rewards, and may involve Server Owner obligations outside DiscPay’s direct control.

Nothing in these Terms limits any mandatory consumer rights that cannot legally be excluded.

13.5 No direct refund guarantee from DiscPay

DiscPay does not guarantee that a Buyer will receive a refund.

DiscPay does not hold Buyer funds and may be unable to issue a refund directly.

Refund availability may depend on the Server Owner, Stripe, card networks, payment-method rules, applicable law, the timing of the request, whether Tokens were used, whether Rewards were fulfilled, whether the payment is disputed, and other relevant circumstances.

13.6 Refund requests

A Buyer seeking a refund should follow the relevant refund or support process made available by the Server Owner, Stripe, the payment method, or DiscPay where applicable.

Depending on the issue, the Buyer may need to provide transaction references, Discord identifiers, Store details, payment records, screenshots, Reward request information, ticket records, or other evidence.

DiscPay may review refund-related information, but is not required to decide every refund request unless DiscPay expressly provides a supported refund-review process.

13.7 Failed or delayed Token delivery

If a payment succeeds but Tokens are not credited, are delayed, or are credited incorrectly, the issue may require automated retry, manual import, manual review, support assistance, or correction.

DiscPay may use Stripe records, transaction identifiers, queue records, import records, logs, and other available evidence to determine whether Tokens should be credited.

A delayed Token credit does not automatically entitle a Buyer to a refund from DiscPay.

However, DiscPay may take reasonable steps to support correction where its records show that a valid payment occurred and Tokens were not properly credited.

13.8 Duplicate payments

If a Buyer believes they were charged more than once, they should report the issue through the available support route and may also need to contact Stripe, the relevant payment provider, or the Server Owner.

DiscPay may review transaction records and may support correction where duplicate payments or duplicate credits are identified.

If duplicate Tokens are credited, DiscPay may remove or reverse the duplicate Tokens.

If duplicate payments occurred without duplicate Token crediting, the refund route may depend on Stripe, the Server Owner, payment-method rules, and applicable law.

13.9 Refunds after Tokens are used

If a Buyer receives a refund, chargeback, reversal, or payment cancellation after Tokens have been used, DiscPay may remove, reverse, freeze, or adjust the related Tokens.

If the Tokens have already been redeemed for Rewards, DiscPay may record a negative balance, restrict future Token use, support Server Owner enforcement, suspend the Buyer’s access to DiscPay features for that Server, or take other appropriate action.

A Buyer is not entitled to keep Tokens or receive Rewards connected to a payment that has been refunded, reversed, disputed, charged back, or found fraudulent.

13.10 Refunds after Rewards are fulfilled

If a Reward has already been fulfilled, it may not be technically or practically possible to return, revoke, reverse, or undo the Reward.

This is especially likely for digital, custom, creative, access-based, consumed, external, or manually fulfilled Rewards.

The Server Owner is responsible for deciding how to handle fulfilled Rewards after a refund, chargeback, dispute, or reversal, subject to applicable law, Stripe rules, Discord rules, and these Terms.

DiscPay may remove related Tokens or restrict related Token workflows even if the Reward cannot be reversed.

13.11 Chargebacks and disputes

A Chargeback or Dispute may occur when a Buyer, payment card holder, bank, payment method, or payment network challenges a payment.

Chargebacks and Disputes may be handled through Stripe, banks, payment-method providers, card networks, or other external systems.

DiscPay does not control the outcome of Chargebacks or Disputes.

A Chargeback or Dispute may affect the Buyer’s Token Balance, the Server Owner’s Stripe Connected Account, the Server’s payment status, future access to DiscPay features, and related records.

13.12 Legitimate disputes and abusive disputes

DiscPay recognises that some disputes may be legitimate.

However, misuse of refunds, disputes, reversals, or chargebacks may be treated as abuse.

Abuse may include, without limitation:

1. purchasing Tokens and then falsely claiming the payment was unauthorised;
2. using Tokens and then initiating a chargeback without valid reason;
3. receiving a Reward and then disputing the payment dishonestly;
4. repeatedly initiating disputes after receiving Tokens or Rewards;
5. using disputes to avoid payment for fulfilled Rewards;
6. coordinating payment abuse with other users;
7. using stolen or unauthorised payment methods;
8. misrepresenting transaction facts; or
9. otherwise abusing payment systems.

DiscPay may investigate suspected refund, dispute, or chargeback abuse.

13.13 Consequences of disputes or chargebacks

If a Buyer initiates a Chargeback, Dispute, reversal, refund claim, or similar payment challenge, DiscPay may, where appropriate:

1. freeze related Tokens;
2. remove related Tokens;
3. record a negative Token Balance;
4. restrict Token redemption;
5. restrict future purchases;
6. restrict the Buyer’s access to DiscPay features for the relevant Server;
7. notify or support the Server Owner;
8. preserve transaction and fulfilment records;
9. support investigation of the relevant Transaction;
10. suspend or terminate access for abusive conduct; and
11. take other action necessary to protect DiscPay, Buyers, Server Owners, payment integrity, or platform integrity.

DiscPay may take such action before the final outcome of a dispute where immediate restriction is necessary to reduce risk.

13.14 Server Owner response to disputes

Server Owners are responsible for responding to payment disputes, chargebacks, or refund issues connected to their Stripe Connected Account and their Rewards.

This may include providing evidence, transaction records, fulfilment records, Buyer communications, Reward descriptions, access logs, ticket records, or other information through Stripe or another relevant process.

DiscPay may provide infrastructure records where available and appropriate, but Server Owners remain responsible for their Stripe Connected Account and dispute handling.

13.15 Buyer restriction after disputed activity

DiscPay may restrict a Buyer’s use of DiscPay in a Server where the Buyer initiates a Chargeback, Dispute, reversal, or payment challenge connected to that Server.

Where DiscPay believes the disputed activity is abusive, fraudulent, repeated, coordinated, or harmful, DiscPay may apply broader restrictions across DiscPay.

DiscPay will not treat every dispute as abuse automatically, but DiscPay may act where the available evidence indicates risk to payment integrity, Server Owners, Buyers, or DiscPay.

13.16 Server restrictions after excessive disputes

DiscPay may restrict, suspend, review, or terminate a Server if the Server has excessive refunds, excessive disputes, excessive chargebacks, misleading Reward descriptions, failed fulfilment patterns, suspicious payment activity, prohibited Rewards, poor support, or other payment-related risk.

DiscPay may disable checkout, suspend Store Pages, freeze Token redemption, require changes to Rewards, require additional owner verification, require support review, or take other action to protect Buyers and platform integrity.

13.17 Reversing Tokens after payment failure

If a payment fails, is cancelled, is reversed, is refunded, is charged back, is disputed, is found fraudulent, is unauthorised, or is otherwise invalidated, DiscPay may reverse or remove any Tokens connected to that payment.

This may occur even if the Tokens were previously shown in the Buyer’s Token Balance.

DiscPay may rely on Stripe data, transaction records, payment status, logs, support records, and other available information when deciding whether a Token reversal is appropriate.

13.18 No double recovery

A Buyer must not receive both a refund or payment reversal and retain the Tokens or Rewards connected to the refunded or reversed payment, unless the relevant Server Owner or DiscPay expressly allows this.

A Buyer must not use refunds, disputes, chargebacks, or payment reversals to obtain Tokens, Rewards, access, services, or digital items without payment.

DiscPay may take corrective action to prevent double recovery.

13.19 External or off-platform items

Some Rewards may be delivered outside DiscPay or outside Discord.

If a Buyer receives an external or off-platform Reward, DiscPay may be unable to reverse, inspect, recover, revoke, or verify that Reward.

External or off-platform fulfilment disputes are primarily the responsibility of the Server Owner and Buyer, subject to Stripe rules, applicable law, and these Terms.

DiscPay may still use its own records to determine Token adjustments, Server restrictions, Buyer restrictions, or enforcement action.

13.20 Refunds required by law

Nothing in these Terms excludes or limits any refund, cancellation, consumer, statutory, or other mandatory rights that cannot lawfully be excluded.

Where applicable law requires a refund, cancellation right, notice, remedy, or other protection, the relevant party must comply with that law.

Server Owners are responsible for understanding and complying with consumer protection, digital content, distance-selling, tax, and refund laws that apply to their own Rewards and Buyers.

13.21 DiscPay discretion in refund-related enforcement

DiscPay may use discretion when handling refund-related, dispute-related, or chargeback-related issues.

DiscPay may consider factors such as:

1. whether the payment succeeded;
2. whether Tokens were credited;
3. whether Tokens were used;
4. whether a Reward was requested;
5. whether a Reward was fulfilled;
6. whether the Reward was reversible;
7. whether the Buyer acted in good faith;
8. whether the Server Owner acted in good faith;
9. whether Staff misused permissions;
10. whether records show fraud or abuse;
11. whether Stripe or another payment processor restricted the account;
12. whether applicable law requires a particular outcome; and
13. whether action is necessary to protect platform integrity.

13.22 Records for refund and dispute handling

DiscPay may retain and use transaction records, Token records, fulfilment records, Store records, Stripe references, Discord identifiers, Buyer identifiers, Server identifiers, logs, tickets, support records, error records, and other metadata to support refund, dispute, and chargeback handling.

These records may be shared with Server Owners, Stripe, payment processors, legal advisers, authorities, or other relevant parties where appropriate and lawful, as described in DiscPay’s Privacy Policy and applicable law.

13.23 No guarantee of recovery

DiscPay does not guarantee that a Server Owner will recover disputed funds, win a chargeback, avoid payment processor penalties, avoid refunds, avoid account restrictions, or avoid losses connected to Buyer disputes.

DiscPay also does not guarantee that a Buyer will recover funds, receive a refund, receive a replacement Reward, or obtain compensation from a Server Owner.

DiscPay’s role is limited to providing infrastructure, records, support tools, and enforcement action where appropriate.

13.24 Relationship with separate Refund and Chargeback Policy

DiscPay may publish a separate Refund and Chargeback Policy to explain refund, dispute, reversal, and chargeback handling in more practical detail.

The separate policy may include instructions for Buyers, Server Owners, Operators, and Staff.

If a separate Refund and Chargeback Policy is published, users must comply with it where applicable.

DiscPay may update that policy from time to time, subject to the change provisions in these Terms.

14. Prohibited Use

14.1 Purpose of Prohibited Use rules

DiscPay is intended to support lawful, payment-linked, server-specific Token and Reward workflows for Discord communities.

DiscPay must not be used for illegal, unsafe, misleading, abusive, fraudulent, regulated, high-risk, or prohibited activity.

The rules in this section are intended to protect Buyers, Server Owners, payment integrity, Stripe compliance, Discord compliance, platform safety, legal compliance, and DiscPay’s operational integrity.

DiscPay may interpret and enforce Prohibited Use rules at its discretion where necessary to reduce legal, payment, fraud, chargeback, security, platform, or reputational risk.

14.2 General Prohibited Use

You must not use DiscPay to create, offer, sell, advertise, facilitate, fulfil, redeem, promote, support, fund, process, or manage any product, service, Reward, Token workflow, Store, Server activity, or transaction that is illegal, fraudulent, deceptive, unsafe, harmful, abusive, exploitative, or prohibited by these Terms.

Prohibited Use includes, without limitation:

1. activity that violates applicable law;
2. activity that violates Stripe’s terms, policies, restricted-business rules, or prohibited-business rules;
3. activity that violates Discord’s terms, policies, developer rules, monetisation rules, or community standards;
4. activity that violates another platform’s terms or rules;
5. activity that creates unacceptable fraud, chargeback, security, legal, regulatory, or reputational risk;
6. activity that misleads Buyers;
7. activity that abuses Tokens, Token Balances, Rewards, refunds, disputes, or chargebacks;
8. activity that attempts to use DiscPay as a financial, stored-value, cash-out, money-transfer, gambling, or investment system; and
9. activity that DiscPay determines is unsuitable for the platform.

14.3 Illegal goods and services

DiscPay must not be used for any illegal goods, illegal services, illegal content, illegal transactions, or illegal activity.

This includes, without limitation:

1. stolen goods;
2. stolen accounts;
3. stolen payment methods;
4. counterfeit goods;
5. unauthorised access credentials;
6. illegal drugs or controlled substances;
7. unlawful weapons;
8. fraud services;
9. identity theft;
10. document forgery;
11. money laundering;
12. sanctions evasion;
13. terrorist financing;
14. illegal sexual content;
15. child sexual abuse material or exploitation;
16. blackmail or extortion;
17. illegal surveillance;
18. illegal hacking;
19. malware distribution;
20. doxxing services;
21. harassment-for-hire; and
22. any other goods, services, or activity that are unlawful in any relevant jurisdiction.

DiscPay may immediately suspend, restrict, terminate, report, or preserve records relating to suspected illegal activity.

14.4 Physical products prohibited

Unless DiscPay expressly approves otherwise in writing, DiscPay must not be used to sell, arrange, redeem, distribute, ship, deliver, or fulfil physical products.

This includes, without limitation:

1. merchandise;
2. shipped items;
3. tangible goods;
4. physical collectibles;
5. physical documents;
6. food or drink;
7. clothing;
8. electronics;
9. hardware;
10. physical access cards;
11. physical tickets; and
12. any other physical goods.

DiscPay is designed for digital, access-based, service-based, and server-related workflows. Physical products create shipping, returns, consumer-law, tax, fraud, fulfilment, safety, and payment risks that DiscPay does not currently support.

14.5 Gift cards and cash-equivalent items prohibited

DiscPay must not be used to sell, redeem, exchange, fulfil, transfer, or provide gift cards, prepaid cards, vouchers, cash-equivalent balances, store credit, redeemable credit, payment cards, payment codes, or similar items.

A Server Owner must not offer Rewards that allow a Buyer to convert Tokens into gift cards, vouchers, cash equivalents, payment instruments, or transferable monetary value.

DiscPay may suspend or terminate any Server that uses Tokens or Rewards to create a cash-equivalent or stored-value system.

14.6 Cash-out prohibited

Tokens must not be used for cash-out.

A Server Owner, Operator, Staff member, Buyer, or other user must not use DiscPay to exchange Tokens for money, cryptocurrency, gift cards, financial assets, payment balances, bank transfers, payment-app balances, or other cash-equivalent value.

A Server Owner must not advertise, promise, imply, support, or facilitate Token cash-out inside or outside DiscPay.

Any external Token cash-out arrangement is unsupported by DiscPay and may result in suspension, Token reversal, Store disabling, termination, or other enforcement action.

14.7 Cryptocurrency, tokens, NFTs, and financial assets

Unless DiscPay expressly approves otherwise in writing, DiscPay must not be used to sell, redeem, exchange, distribute, mint, allocate, transfer, promote, or provide cryptocurrency, crypto tokens, NFTs, token allocations, token presales, digital asset investments, DeFi products, yield products, staking products, trading products, financial assets, investment contracts, or similar assets.

Crypto, NFT, trading, or investment-related communities may use DiscPay only for ordinary community access or non-financial digital perks, provided their use complies with these Terms, Stripe’s rules, Discord’s rules, and applicable law.

Such communities must not use DiscPay to sell:

1. investment products;
2. trading signals promising returns;
3. financial advice requiring authorisation;
4. token allocations;
5. NFT mints;
6. crypto assets;
7. cash-equivalent digital assets;
8. profit-sharing rights;
9. investment memberships marketed as financial opportunities; or
10. any product or service that creates unacceptable financial, regulatory, payment, or reputational risk.

14.8 No investment or profit promises

Server Owners must not market Tokens, Rewards, server access, memberships, communities, or digital perks as investments.

Server Owners must not promise, imply, advertise, or suggest that Buyers will earn profit, receive financial returns, obtain yield, receive dividends, benefit from appreciation, obtain resale value, receive passive income, or gain monetary advantage by purchasing Tokens or Rewards.

DiscPay may suspend or remove any Server, Store, Reward, or content that appears to create securities, investment, financial-promotion, crypto-asset, e-money, stored-value, gambling, or regulatory risk.

14.9 Gambling, betting, raffles, and chance-based rewards

DiscPay must not be used for gambling, betting, wagering, paid raffles, lotteries, casino-style games, loot boxes, mystery boxes, chance-based paid Rewards, paid randomised outcomes, prize draws requiring payment, or any similar activity.

A Server Owner must not allow Buyers to use Tokens to:

1. place bets;
2. enter paid raffles;
3. buy randomised Rewards;
4. buy loot boxes;
5. buy mystery Rewards;
6. spin wheels;
7. enter paid games of chance;
8. increase odds of winning prizes;
9. gamble on events;
10. win cash-equivalent rewards; or
11. participate in any activity that is regulated as gambling, lottery, betting, or chance-based paid promotion.

Giveaways may be allowed only where they are lawful, compliant, not misleading, not gambling, not a paid lottery, not based on unlawful chance mechanics, and not structured to bypass these Terms.

14.10 Giveaways

Server Owners may run giveaways only if the giveaway is lawful, compliant with Discord’s rules, compliant with Stripe’s rules, and compliant with these Terms.

A giveaway must not require a Token purchase, payment, cash-equivalent contribution, or other purchase as a condition of entry unless DiscPay has expressly approved the structure in writing and the Server Owner has confirmed compliance with applicable law.

Server Owners are responsible for the rules, eligibility, fairness, winner selection, fulfilment, and legal compliance of any giveaway they run.

DiscPay may restrict, suspend, or remove giveaways that appear to be gambling, paid raffles, misleading promotions, fraud, scams, or otherwise unsuitable.

14.11 Adult content and adult services

Adult-oriented Discord communities may be allowed only where lawful, compliant with Discord’s rules, compliant with Stripe’s rules, and compliant with these Terms.

However, unless DiscPay expressly approves otherwise in writing, DiscPay must not be used to sell, redeem, provide, advertise, or facilitate adult sexual goods, adult sexual services, explicit sexual content, sexual performances, escort services, pornography, paid sexual access, sexualised custom content, or other age-restricted sexual material.

Server Owners must not use DiscPay to monetise sexual content or sexual services.

DiscPay may suspend, restrict, or terminate any Server where adult activity creates legal, payment, Stripe, Discord, safety, age-verification, exploitation, reputational, or platform risk.

14.12 Regulated goods and services

Unless DiscPay expressly approves otherwise in writing, DiscPay must not be used for regulated goods or regulated services.

Regulated goods and services may include, without limitation:

1. alcohol;
2. tobacco;
3. nicotine products;
4. vapes;
5. drugs;
6. CBD or THC products;
7. weapons;
8. explosives;
9. medical products;
10. medical services;
11. legal services;
12. insurance;
13. loans;
14. credit;
15. debt services;
16. financial products;
17. investment products;
18. gambling products;
19. charity fundraising where regulated;
20. government documents;
21. identity documents;
22. age-restricted goods;
23. adult sexual goods or services; and
24. any other goods or services requiring licensing, authorisation, registration, age verification, professional qualification, or regulatory compliance.

A Server Owner is responsible for knowing whether their Rewards or activities are regulated. DiscPay may refuse or suspend any regulated activity even if the Server Owner believes it is lawful.

14.13 Third-party platform rule violations

DiscPay must not be used to sell, advertise, provide, support, or facilitate goods or services that violate another platform’s terms, rules, policies, or technical restrictions.

This includes, without limitation:

1. game cheats;
2. hacked clients;
3. exploit tools;
4. ban evasion;
5. account selling;
6. account sharing where prohibited;
7. stolen accounts;
8. unauthorised boosting;
9. botting or macro services where prohibited;
10. automation intended to violate platform rules;
11. rank manipulation;
12. marketplace manipulation;
13. unauthorised resale;
14. service abuse;
15. bypassing paywalls or access controls;
16. credential sharing; and
17. any service intended to help users break the rules of Discord, games, software platforms, marketplaces, SaaS platforms, or other services.

DiscPay may suspend any Server that exposes DiscPay to third-party platform enforcement risk.

14.14 Fraud, scams, and misleading activity

DiscPay must not be used for fraud, scams, deception, misrepresentation, or misleading commercial activity.

Prohibited activity includes, without limitation:

1. fake Rewards;
2. misleading Reward descriptions;
3. false scarcity;
4. false affiliation;
5. fake endorsements;
6. impersonation;
7. phishing;
8. fake giveaways;
9. false delivery claims;
10. fake transaction records;
11. false fulfilment records;
12. misleading refund statements;
13. hiding material restrictions;
14. bait-and-switch Rewards;
15. fake investment opportunities;
16. pyramid schemes;
17. Ponzi schemes;
18. advance-fee scams;
19. unauthorised use of another brand; and
20. any activity that deceives or is likely to deceive Buyers.

DiscPay may take immediate enforcement action where fraud or misleading activity is suspected.

14.15 Malware, hacking, and security abuse

DiscPay must not be used to sell, distribute, advertise, support, or facilitate malware, hacking tools, credential theft, unauthorised access, exploit kits, phishing kits, botnets, denial-of-service tools, spyware, ransomware, account compromise, or other security abuse.

DiscPay must not be used to purchase, request, reward, fund, or coordinate hacking, doxxing, harassment, extortion, credential theft, data theft, or unauthorised access.

DiscPay may preserve logs, suspend access, restrict Tokens, terminate Servers, and report suspected security abuse where appropriate.

14.16 Harassment, hate, extremism, and violence

DiscPay must not be used to fund, facilitate, reward, organise, promote, or support harassment, hate, extremism, terrorism, violence, intimidation, threats, abuse, targeted harassment, or illegal discrimination.

Prohibited activity includes, without limitation:

1. terrorist financing;
2. violent extremist activity;
3. hate group fundraising;
4. threats of violence;
5. harassment-for-hire;
6. doxxing;
7. stalking;
8. targeted abuse;
9. intimidation campaigns;
10. incitement to violence;
11. illegal discriminatory services; and
12. fundraising for illegal or violent activity.

Political, ideological, or controversial communities may be allowed only where lawful and compliant, but DiscPay may suspend any Server that creates safety, legal, payment, platform, or reputational risk.

14.17 Sanctions and restricted parties

DiscPay must not be used by or for the benefit of any person, entity, country, region, organisation, or activity subject to applicable sanctions, export restrictions, payment restrictions, or legal prohibitions.

Users must not attempt to bypass sanctions, payment restrictions, country restrictions, identity checks, or compliance controls.

DiscPay may restrict or terminate access where sanctions, restricted-party, country, payment, or compliance risk is suspected.

14.18 Intellectual property infringement

DiscPay must not be used to sell, distribute, advertise, or provide infringing content or services.

Server Owners must not use Store Pages, Rewards, Server icons, branding, descriptions, or other content that infringes copyright, trade marks, trade names, design rights, database rights, publicity rights, privacy rights, or other rights of third parties.

Prohibited activity includes, without limitation:

1. pirated software;
2. unauthorised game files;
3. stolen artwork;
4. unauthorised music;
5. unauthorised videos;
6. copyrighted content access;
7. counterfeit digital goods;
8. unauthorised brand use;
9. impersonation of companies or creators; and
10. resale of digital items where resale is prohibited.

DiscPay may remove or restrict content that appears infringing or risky.

14.19 High-risk or unsupported business models

DiscPay may prohibit, restrict, or require approval for high-risk or unsupported business models even where they are not expressly listed in these Terms.

High-risk or unsupported models may include, without limitation:

1. financial services;
2. investment communities selling paid financial benefits;
3. adult monetisation;
4. regulated services;
5. legal or medical advice;
6. high-chargeback digital services;
7. reputation-sensitive communities;
8. refund-heavy services;
9. disputed ownership structures;
10. resale marketplaces;
11. token exchange systems;
12. peer-to-peer trading;
13. cash-out systems;
14. paid randomised reward systems; and
15. other models that create unacceptable risk for DiscPay.

DiscPay may require written approval before allowing such activity.

14.20 Circumvention

Users must not attempt to bypass these Prohibited Use rules.

Circumvention includes, without limitation:

1. using vague Reward descriptions to hide prohibited activity;
2. moving prohibited fulfilment off-platform;
3. using coded language;
4. directing Buyers to external prohibited transactions;
5. selling Tokens for an allowed purpose while actually fulfilling a prohibited purpose;
6. splitting activity across multiple Servers;
7. using another account or Server after suspension;
8. using external links to bypass Store restrictions;
9. instructing Buyers to avoid mentioning prohibited activity; or
10. otherwise attempting to avoid DiscPay’s detection or enforcement.

DiscPay may treat attempted circumvention as a serious breach of these Terms.

14.21 Server Owner duty to monitor Prohibited Use

Server Owners must take reasonable steps to ensure that their Servers, Operators, Staff, Reward Catalogues, Store Pages, tickets, fulfilment workflows, and related activity do not involve Prohibited Use.

Server Owners must remove prohibited Rewards, stop prohibited fulfilment, revoke abusive permissions, respond to Buyer reports, and cooperate with DiscPay investigations where required.

A Server Owner cannot avoid responsibility by claiming that prohibited activity was carried out by Operators, Staff, moderators, community members, Buyers, or third parties if the activity occurred through or in connection with the Server’s use of DiscPay.

14.22 Buyer Prohibited Use

Buyers must not use DiscPay to purchase, request, fund, redeem, support, or facilitate Prohibited Use.

A Buyer must not knowingly purchase Tokens for prohibited activity, request prohibited Rewards, abuse refunds or chargebacks, use stolen payment methods, exploit bugs, misrepresent transactions, harass Staff, or participate in fraud.

DiscPay may restrict, suspend, or terminate Buyers involved in Prohibited Use.

14.23 Reporting Prohibited Use

Users may report suspected Prohibited Use through the available support contact or reporting process.

Reports should include relevant information where available, such as Server details, Reward descriptions, screenshots, transaction references, Discord identifiers, messages, Store links, or other evidence.

DiscPay may review reports, but does not guarantee that it will take the specific action requested by the reporter.

DiscPay may use reports to investigate, preserve records, restrict activity, suspend Stores, remove Rewards, terminate access, or improve platform safety.

14.24 DiscPay review and discretion

DiscPay may review Servers, Stores, Rewards, Token activity, transaction records, logs, reports, tickets, Staff actions, Buyer behaviour, or external evidence where necessary to enforce these Terms.

DiscPay has discretion to determine whether activity is prohibited, high-risk, misleading, unsafe, abusive, or unsuitable for DiscPay.

DiscPay is not required to prove a legal violation before restricting or terminating activity. DiscPay may act where it reasonably believes risk exists.

14.25 No approval by silence

If DiscPay does not immediately detect, restrict, remove, or enforce against a Server, Reward, Store, transaction, or activity, that does not mean the activity is approved, lawful, safe, compliant, or permitted.

DiscPay may take enforcement action later if it discovers an issue or if risk changes.

15. Enforcement, Suspension, And Termination

15.1 Enforcement powers

DiscPay may take enforcement action where it believes that a User, Server, Store, Reward, Token workflow, transaction, permission, payment activity, or related conduct violates these Terms, violates applicable law, violates third-party rules, creates risk, or is otherwise harmful to DiscPay, Buyers, Server Owners, Stripe, Discord, or third parties.

Enforcement action may include, without limitation:

1. warnings;
2. support review;
3. requiring changes;
4. removing Rewards;
5. disabling Reward Catalogues;
6. disabling Store Pages;
7. disabling checkout;
8. freezing Token purchases;
9. freezing Token redemption;
10. freezing Token adjustments;
11. reversing Token credits;
12. restricting Buyers;
13. restricting Operators or Staff;
14. restricting Server Owner access;
15. suspending a Server;
16. terminating a Server’s access;
17. refusing onboarding;
18. requiring re-onboarding;
19. preserving records;
20. reporting suspected illegal activity; and
21. taking other action DiscPay considers appropriate.

15.2 Immediate action

DiscPay may take immediate enforcement action without prior notice where it believes immediate action is necessary to protect Buyers, Server Owners, payment integrity, legal compliance, fraud prevention, security, Discord compliance, Stripe compliance, platform integrity, or DiscPay’s reputation.

Immediate action may be taken before DiscPay completes a full investigation.

15.3 Suspension of checkout

DiscPay may suspend or disable checkout for a Server at any time.

Checkout suspension may occur where:

1. onboarding is incomplete;
2. Stripe status is incomplete, restricted, rejected, or unsafe;
3. fees are unpaid;
4. ownership has changed or is disputed;
5. Prohibited Use is suspected;
6. excessive chargebacks occur;
7. excessive refunds occur;
8. fraudulent activity is suspected;
9. Store content is misleading;
10. Reward fulfilment is failing;
11. legal risk exists;
12. Stripe or Discord compliance is at risk;
13. technical issues affect payment integrity; or
14. DiscPay determines that checkout should be restricted.

Suspension of checkout does not necessarily delete Token Balances, records, logs, or Server configuration.

15.4 Freezing Token redemption

DiscPay may freeze or restrict Token redemption for a Buyer, Server, Reward, Store, or Transaction where necessary.

Reasons may include, without limitation:

1. fraud investigation;
2. chargeback investigation;
3. refund review;
4. duplicate credit review;
5. ownership change;
6. Staff misuse;
7. prohibited Reward investigation;
8. payment-processor restriction;
9. legal requirement;
10. Server suspension;
11. technical failure;
12. security issue; or
13. other platform risk.

Freezing Token redemption does not necessarily mean Tokens have been removed.

15.5 Removal of Rewards and Store content

DiscPay may remove, hide, disable, restrict, or require changes to Rewards, Reward descriptions, Store content, Server metadata, images, icons, links, notices, or other content.

DiscPay may do so where content appears prohibited, unlawful, misleading, infringing, unsafe, abusive, high-risk, inaccurate, or inconsistent with these Terms.

DiscPay is not required to restore removed content.

15.6 Suspension of Servers

DiscPay may suspend a Server’s access to some or all DiscPay features.

Suspension may affect:

1. onboarding status;
2. Store Pages;
3. checkout;
4. Token purchases;
5. Token redemption;
6. Token adjustments;
7. Reward Catalogues;
8. tickets;
9. Staff permissions;
10. Operator access;
11. logs;
12. imports;
13. recovery tools;
14. support tools; and
15. other features.

Suspension may be temporary, indefinite, or pending investigation.

15.7 Termination of Servers

DiscPay may terminate a Server’s access to DiscPay where DiscPay determines that continued access is inappropriate.

Termination may occur for reasons including, without limitation:

1. serious breach of these Terms;
2. repeated breach of these Terms;
3. Prohibited Use;
4. illegal activity;
5. fraud;
6. excessive chargebacks;
7. non-payment of DiscPay fees;
8. abuse of Buyers;
9. misleading Rewards;
10. failed fulfilment patterns;
11. Stripe restrictions;
12. Discord restrictions;
13. ownership disputes;
14. security issues;
15. reputational risk; or
16. any other reason that DiscPay considers sufficient to protect the platform.

15.8 Buyer restrictions

DiscPay may restrict, suspend, or terminate a Buyer’s access to DiscPay features.

Reasons may include, without limitation:

1. payment fraud;
2. stolen payment methods;
3. abusive chargebacks;
4. repeated disputes;
5. Token misuse;
6. prohibited Reward requests;
7. harassment of Staff;
8. exploiting bugs;
9. false claims;
10. attempting cash-out;
11. attempting unsupported Token transfers;
12. attempting to bypass checkout controls; or
13. other harmful conduct.

Buyer restrictions may apply to one Server or across DiscPay, depending on the risk.

15.9 Operator and Staff restrictions

DiscPay may restrict, suspend, or remove Operator or Staff access where it believes such access creates risk.

Reasons may include, without limitation:

1. misuse of permissions;
2. unauthorised Token adjustments;
3. false fulfilment records;
4. improper access to Buyer data;
5. failure to handle fulfilment properly;
6. suspected account compromise;
7. harassment;
8. fraud;
9. breach of these Terms;
10. Prohibited Use; or
11. failure to act under Server Owner authority.

DiscPay may act independently of the Server Owner where necessary to protect the platform.

15.10 Refusal of onboarding

DiscPay may refuse onboarding for any Server or Server Owner.

DiscPay is not required to accept every Server.

Reasons for refusal may include, without limitation:

1. unsupported country;
2. Stripe incompatibility;
3. suspected fraud;
4. Prohibited Use risk;
5. high chargeback risk;
6. legal risk;
7. Discord compliance risk;
8. incomplete information;
9. misleading information;
10. previous suspension;
11. sanctions risk;
12. reputation risk;
13. ownership uncertainty; or
14. other platform risk.

15.11 Non-payment enforcement

DiscPay may suspend, restrict, or terminate access if a Server Owner fails to pay DiscPay fees, invoices, platform charges, or other amounts owed.

DiscPay may disable checkout, Store Pages, Token purchases, Token redemption, Reward tools, or other features until outstanding amounts are resolved.

Non-payment suspension does not automatically delete records, Token Balances, transaction history, or logs.

15.12 Investigation

DiscPay may investigate suspected breaches, disputes, chargebacks, fraud, Prohibited Use, permission misuse, security issues, ownership changes, payment issues, or other risks.

During an investigation, DiscPay may preserve records, restrict features, suspend checkout, freeze Tokens, restrict users, disable Rewards, request information, or take other temporary measures.

Users must cooperate with reasonable investigation requests.

Failure to cooperate may result in suspension or termination.

15.13 Preservation of records

DiscPay may preserve records where necessary for investigation, payment integrity, legal compliance, fraud prevention, security, dispute handling, chargeback handling, tax or accounting purposes, enforcement, or protection of DiscPay’s rights.

Preserved records may include, without limitation:

1. transaction records;
2. Token records;
3. balance adjustment records;
4. fulfilment records;
5. Store records;
6. Stripe references;
7. Discord identifiers;
8. email records;
9. support records;
10. logs;
11. error metadata;
12. security records; and
13. enforcement records.

Record preservation may continue after suspension, termination, Server disconnection, Buyer restriction, or ownership change.

15.14 Effect of suspension

During suspension, affected users may be unable to access some or all DiscPay features.

This may include inability to purchase Tokens, redeem Tokens, adjust balances, access Store Pages, use Reward workflows, manage permissions, import Transactions, or use support tools.

Suspension does not necessarily remove existing Token Balances, records, Store configuration, Stripe references, or logs.

DiscPay may decide whether and when suspended features are restored.

15.15 Effect of termination

Termination may permanently prevent a Server, Server Owner, Buyer, Operator, Staff member, or other user from accessing some or all DiscPay features.

Following termination, DiscPay may disable checkout, remove Store Pages, restrict Token workflows, remove Rewards, revoke permissions, preserve records, and prevent re-onboarding.

Termination does not require DiscPay to delete records where retention is necessary for payment integrity, legal compliance, fraud prevention, accounting, security, dispute handling, or enforcement.

15.16 Reinstatement

DiscPay may allow reinstatement after suspension or termination, but is not required to do so.

DiscPay may require conditions for reinstatement, including:

1. payment of outstanding fees;
2. removal of prohibited Rewards;
3. correction of misleading information;
4. completion of re-onboarding;
5. new Stripe verification;
6. ownership verification;
7. improved support processes;
8. reduced chargeback risk;
9. removal of abusive Staff;
10. additional documentation;
11. agreement to additional restrictions; or
12. other corrective action.

15.17 Appeals and support review

DiscPay may provide a support route for users to request review of enforcement decisions.

A review request does not automatically suspend enforcement action.

DiscPay is not required to provide a formal appeal process unless required by applicable law.

DiscPay may maintain, modify, reverse, reduce, or expand enforcement action after review.

15.18 Repeated or related abuse

DiscPay may consider related activity across multiple Servers, accounts, Buyers, Operators, Staff members, email addresses, payment methods, Stripe accounts, Discord accounts, IP-derived security signals, transaction patterns, or other technical indicators.

Users must not evade enforcement by creating new accounts, moving to another Server, using another Stripe account, using another Discord account, changing names, hiding ownership, using proxies, or otherwise attempting to bypass restrictions.

DiscPay may restrict related accounts or Servers where it believes they are connected to abuse or enforcement evasion.

15.19 No liability for enforcement action

To the fullest extent permitted by applicable law, DiscPay is not liable for losses, lost revenue, lost profits, lost opportunity, reputational harm, loss of Buyers, loss of access, failed fulfilment, delayed payments, Token restrictions, Store suspension, or other harm resulting from enforcement action taken in good faith under these Terms.

This does not limit liability that cannot legally be excluded.

15.20 Cooperation with third parties and authorities

DiscPay may cooperate with Stripe, Discord, payment processors, banks, card networks, hosting providers, legal advisers, law enforcement, regulators, courts, or other relevant parties where appropriate and lawful.

This may include sharing records, preserving evidence, responding to lawful requests, reporting suspected illegal activity, or taking action required by third parties.

15.21 Platform protection priority

DiscPay may prioritise platform protection over continued access for any particular Server, Buyer, Operator, Staff member, or other user.

Where DiscPay believes that continued access creates unacceptable risk, DiscPay may restrict or terminate access even if doing so affects Token purchases, Token redemption, Store availability, Reward fulfilment, Server revenue, Buyer expectations, or operational continuity.

15.22 Survival after enforcement

Rights and obligations relating to payment records, Token records, refunds, disputes, chargebacks, taxes, data retention, confidentiality, intellectual property, disclaimers, limitation of liability, indemnity, governing law, enforcement, and other provisions intended to survive may continue after suspension, termination, Server disconnection, or account restriction.

16. Service Availability, Technical Failures, And Recovery

16.1 Service availability

DiscPay aims to provide a reliable service, but DiscPay does not guarantee that the service will always be available, uninterrupted, secure, error-free, or compatible with every Server, device, browser, country, payment method, Discord configuration, Stripe account, or third-party system.

DiscPay may be affected by downtime, maintenance, software errors, hosting issues, domain issues, SSL or certificate issues, database issues, queue-processing issues, payment-processor issues, Discord API issues, Discord permission issues, Stripe issues, network failures, security controls, abuse-prevention measures, legal restrictions, or other technical or operational factors.

Use of DiscPay is subject to these limitations.

16.2 No uptime guarantee

Unless DiscPay expressly provides a separate written service-level agreement, DiscPay does not provide any uptime guarantee, availability guarantee, response-time guarantee, processing-time guarantee, or delivery-time guarantee.

DiscPay may suspend, restrict, delay, modify, interrupt, or discontinue any part of the service for maintenance, security, fraud prevention, legal compliance, payment-processor compliance, Discord compliance, operational reasons, or platform protection.

16.3 Maintenance and updates

DiscPay may perform maintenance, updates, migrations, security patches, infrastructure changes, database changes, queue changes, Store changes, bot changes, API changes, logging changes, or other technical work at any time.

Where reasonably practical, DiscPay may provide notice of planned maintenance that materially affects the service.

However, DiscPay may perform emergency maintenance without notice where necessary to protect security, payment integrity, data integrity, platform integrity, or legal compliance.

16.4 Discord-related failures

DiscPay depends on Discord for bot functionality, commands, messages, roles, server access, OAuth, API access, permissions, webhooks, member data, and other Discord-dependent features.

DiscPay is not responsible for failures, delays, restrictions, outages, permission issues, API changes, policy changes, account restrictions, server removals, server bans, message failures, command failures, role assignment failures, OAuth failures, or other issues caused by Discord or Discord-related systems.

If Discord is unavailable, restricted, changed, or otherwise affected, DiscPay features that depend on Discord may fail, be delayed, become unavailable, or require manual recovery.

16.5 Stripe-related failures

DiscPay depends on Stripe for payment processing, checkout, account onboarding, payment status, transaction events, disputes, refunds, chargebacks, payout handling, tax tools, and related payment infrastructure.

DiscPay is not responsible for failures, delays, restrictions, reversals, declines, holds, account reviews, account suspensions, payout delays, webhook delays, checkout failures, refund failures, dispute outcomes, or other issues caused by Stripe, payment-method providers, banks, card networks, or other payment infrastructure.

If Stripe is unavailable, delayed, restricted, or otherwise affected, DiscPay payment-related features may fail, be delayed, become unavailable, or require manual recovery.

16.6 Payment succeeded but processing delayed

A payment may succeed through Stripe while DiscPay’s related Token crediting, Store update, queue processing, Discord notification, ticket creation, fulfilment notification, import record, or transaction log is delayed or fails.

This may occur because of webhook delays, queue-processing errors, network issues, database issues, Discord issues, Stripe event delays, configuration issues, duplicate-detection checks, security controls, or other technical factors.

A delayed processing event does not necessarily mean that a payment failed or that Tokens are not owed. The issue may require automated retry, manual import, manual review, support assistance, or correction.

16.7 Queue processing and recovery

DiscPay may use queues, logs, transaction records, import tools, duplicate-detection systems, processed records, failed records, and other recovery systems to handle payment-linked workflows.

Queue processing may be delayed, fail, retry, or require manual review.

DiscPay may move records between pending, processed, failed, reviewed, imported, or other internal states.

DiscPay may rely on transaction identifiers, Stripe references, Server identifiers, Buyer identifiers, timestamps, logs, and other metadata to determine whether a Transaction has already been processed or should be processed again.

16.8 Manual imports and recovery tools

DiscPay may provide manual import, recovery, reconciliation, or support tools to help Server Owners or DiscPay Admins correct missing, delayed, failed, or inconsistent payment-linked records.

Manual import or recovery tools may be used to:

1. locate successful payments;
2. credit missing Tokens;
3. prevent duplicate credits;
4. reconcile Stripe records with DiscPay records;
5. review failed queue items;
6. correct transaction status;
7. generate missing fulfilment records;
8. update logs;
9. investigate disputes; or
10. support other recovery work.

DiscPay does not guarantee that manual import or recovery will resolve every issue.

16.9 Duplicate prevention

DiscPay may use deduplication controls to prevent the same Transaction from being credited, imported, announced, or fulfilled more than once.

Deduplication may rely on Stripe transaction identifiers, checkout session identifiers, payment intent identifiers, internal transaction identifiers, Server records, Buyer records, queue records, or other metadata.

Users must not attempt to bypass duplicate-prevention controls.

If duplicate Tokens, duplicate fulfilment records, duplicate announcements, or duplicate credits occur, DiscPay may correct, reverse, remove, freeze, or restrict related records or Token Balances.

16.10 Server Owner review responsibility

Server Owners are responsible for reviewing transaction records, Token records, fulfilment records, logs, import results, and support information for their Server.

If a Server Owner believes that a payment was missed, Tokens were incorrectly credited, a duplicate occurred, a fulfilment record failed, or a technical issue affected a Buyer, the Server Owner should use available recovery tools or contact DiscPay support.

DiscPay may provide tools and logs to assist, but DiscPay does not guarantee that every issue will be automatically detected.

16.11 Buyer support for technical failures

A Buyer who believes that a payment succeeded but Tokens were not credited, or that a Reward request failed because of a technical issue, should contact the relevant Server support route, ticket system, or DiscPay support route where available.

The Buyer may need to provide relevant information, such as transaction references, payment confirmation, Discord user ID, Server details, screenshots, timestamps, Store information, or other evidence.

DiscPay may review available records but does not guarantee instant resolution.

16.12 Data loss and backup limitations

DiscPay may use backups, logs, recovery records, or other technical measures to protect the service, but DiscPay does not guarantee that all data can always be restored.

Data loss, corruption, delay, partial recovery, or inconsistency may occur because of technical failures, third-party failures, operational errors, security incidents, hosting issues, database issues, queue issues, software bugs, or other causes.

DiscPay may attempt to restore records where reasonably possible, but does not guarantee full restoration of every Store, Token Balance, Transaction, Reward, ticket, log, configuration, or other record.

16.13 Security controls and service restrictions

DiscPay may restrict, delay, block, review, or reject actions for security, fraud prevention, abuse prevention, payment integrity, legal compliance, or platform protection.

Security controls may affect onboarding, checkout, Token crediting, Token redemption, balance adjustments, Store access, Discord commands, OAuth, imports, logs, permissions, or other features.

A legitimate user may experience delays or restrictions because of security controls.

DiscPay may modify security controls at any time and is not required to disclose detailed security logic.

16.14 No guarantee of compatibility

DiscPay does not guarantee compatibility with every Discord Server configuration, role structure, bot permission setup, channel setup, browser, device, payment method, Stripe account type, country, firewall, network, operating system, or third-party service.

Server Owners are responsible for ensuring that their Server configuration, bot permissions, Discord settings, Stripe account, Store settings, and operational workflows are suitable for their intended use.

17. Data, Logs, And Privacy

17.1 Privacy Policy

DiscPay’s collection, use, storage, sharing, and retention of personal data is described in DiscPay’s Privacy Policy.

By using DiscPay, you acknowledge that DiscPay may process personal data and technical data as described in the Privacy Policy and any applicable Data Collection Notice.

These Terms should be read together with the Privacy Policy.

17.2 Data collected to operate DiscPay

DiscPay may collect and process data necessary to operate, secure, support, monitor, improve, and enforce the service.

This may include, without limitation:

1. Discord user identifiers;
2. Discord usernames, display names, avatar references, or icon references where made available through Discord APIs, OAuth, bot interactions, dashboards, tickets, support flows, logs, or operational tooling;
3. Discord Server identifiers;
4. Server names;
5. Server icons;
6. email addresses;
7. country information;
8. Stripe account references;
9. Stripe transaction references;
10. checkout references;
11. Token Balances;
12. Token adjustment records;
13. Transaction records;
14. Reward request records;
15. fulfilment records;
16. Store records;
17. Operator and Staff permission records;
18. command logs;
19. support records;
20. security records;
21. OAuth/session records;
22. cookie or session data;
23. error metadata; and
24. technical logs.

17.3 Logs and audit records

DiscPay may create and retain logs and audit records relating to Server Owner actions, Operator actions, Staff actions, Buyer actions, system actions, payments, Tokens, Rewards, permissions, fulfilment, support, imports, errors, security events, and enforcement.

Logs may be used to:

1. operate the service;
2. maintain transaction integrity;
3. maintain Token integrity;
4. prevent duplicate credits;
5. investigate missing payments;
6. investigate refunds or chargebacks;
7. investigate fraud or abuse;
8. investigate permission misuse;
9. support Server Owners;
10. support Buyers;
11. enforce these Terms;
12. comply with legal obligations;
13. protect DiscPay; and
14. improve service reliability.

17.4 Access to logs

Logs, records, or summaries may be made available to Server Owners, Operators, Staff, Buyers, DiscPay Admins, Stripe, support personnel, legal advisers, authorities, or other relevant parties where appropriate, lawful, and necessary.

Access may depend on permissions, role, context, legal requirements, security considerations, privacy requirements, and DiscPay’s internal controls.

DiscPay is not required to provide unrestricted access to raw logs, internal security records, fraud signals, internal notes, or proprietary monitoring systems.

17.5 Data accuracy

Users must provide accurate information where required.

Server Owners are responsible for keeping onboarding information, email addresses, country information, Stripe information, Store configuration, Reward information, and permissions accurate.

Buyers are responsible for providing accurate information needed for payment, Token crediting, account linking, Reward requests, or support.

DiscPay may restrict, suspend, correct, or review records where information appears inaccurate, incomplete, outdated, fraudulent, misleading, or inconsistent.

17.6 Data retention

DiscPay may retain data for as long as reasonably necessary for service operation, payment integrity, Token Balance integrity, fraud prevention, security, legal compliance, accounting, tax records, dispute handling, chargeback handling, Server reconnection, enforcement, and protection of DiscPay’s rights.

Some records may need to be retained after a Server disconnects, a Buyer leaves a Server, a Server is suspended, a Store is disabled, a payment is refunded, an account is restricted, or a user requests deletion.

Retention is described in more detail in DiscPay’s Privacy Policy.

17.7 Data deletion and restrictions

Users may have rights to request access, correction, deletion, restriction, objection, portability, or other privacy rights under applicable law.

However, DiscPay may retain certain records where necessary for payment records, fraud prevention, chargebacks, refunds, tax or accounting, legal claims, security, enforcement, Token Balance integrity, Server reconnection, or compliance.

Where deletion is not possible or not appropriate, DiscPay may restrict, minimise, anonymise, preserve, or retain records as described in its Privacy Policy and applicable law.

17.8 Security

DiscPay may use technical and organisational measures intended to protect the service, data, logs, records, payment-linked workflows, and user accounts.

However, no system is completely secure.

Users are responsible for protecting their Discord accounts, email accounts, Stripe accounts, devices, passwords, sessions, access tokens, and other credentials.

Users must promptly notify DiscPay if they suspect unauthorised access, compromised accounts, security issues, or misuse affecting DiscPay.

18. Intellectual Property

18.1 DiscPay intellectual property

DiscPay and its software, systems, designs, interfaces, code, workflows, documentation, databases, templates, Store layouts, logos, names, branding, text, graphics, infrastructure, processes, and related materials are owned by DiscPay or its licensors.

Except as expressly allowed by these Terms, users must not copy, modify, reproduce, distribute, sell, lease, sublicense, reverse engineer, decompile, scrape, exploit, or create derivative works from DiscPay or its materials.

18.2 Limited right to use DiscPay

Subject to these Terms, DiscPay grants users a limited, revocable, non-exclusive, non-transferable, non-sublicensable right to access and use DiscPay for its intended purposes.

This right is provided only while the user remains compliant with these Terms and while DiscPay makes the relevant features available.

DiscPay may revoke or restrict this right at any time in accordance with these Terms.

18.3 Server Owner content

Server Owners may provide or configure content through DiscPay, including Server names, Server icons, Reward descriptions, Store information, support text, branding, links, images, or other materials.

The Server Owner represents that they have all rights necessary to provide and use such content.

The Server Owner grants DiscPay a worldwide, non-exclusive, royalty-free licence to host, store, copy, display, process, transmit, modify for formatting, and use such content as necessary to operate, secure, support, display, and improve DiscPay.

18.4 Buyer and user content

Buyers, Operators, Staff, or other users may provide content through support tickets, Reward requests, messages, forms, reports, feedback, or other workflows.

The user grants DiscPay a licence to use such content as necessary to operate the service, provide support, investigate issues, enforce these Terms, comply with law, and protect platform integrity.

18.5 Feedback

If a user provides ideas, suggestions, improvements, feature requests, bug reports, concepts, designs, workflows, or other feedback to DiscPay, DiscPay may use that feedback without restriction or compensation.

Feedback does not create ownership rights for the user in DiscPay’s service, features, systems, or future development.

18.6 Infringing content

Users must not upload, display, configure, advertise, or use content through DiscPay that infringes another person’s intellectual property rights.

DiscPay may remove, disable, restrict, or refuse content that appears infringing, misleading, unauthorised, or risky.

19. Disclaimers

19.1 Service provided as available

DiscPay is provided on an “as is” and “as available” basis.

To the fullest extent permitted by applicable law, DiscPay makes no warranties, representations, or guarantees that the service will be uninterrupted, error-free, secure, accurate, complete, reliable, compatible, profitable, suitable for any particular purpose, or available at all times.

19.2 No guarantee of monetisation

DiscPay does not guarantee that a Server Owner will earn revenue, attract Buyers, avoid refunds, avoid chargebacks, avoid disputes, avoid fraud, maintain Stripe access, maintain Discord access, retain users, or successfully monetise a Server.

Any examples, analytics, suggestions, projections, pricing information, or performance information provided by DiscPay are informational only and do not guarantee results.

19.3 No guarantee of Rewards

DiscPay does not guarantee that Server Owners, Operators, or Staff will provide, maintain, fulfil, or support any Reward.

DiscPay does not guarantee Reward quality, legality, availability, timing, suitability, usefulness, accuracy, compatibility, or value.

Rewards are the responsibility of the relevant Server Owner unless DiscPay expressly states otherwise.

19.4 No guarantee of third-party services

DiscPay does not guarantee the availability, behaviour, decisions, rules, security, accuracy, reliability, or continued operation of third-party services, including Discord, Stripe, banks, card networks, payment-method providers, hosting providers, domain providers, email providers, OAuth providers, APIs, or external fulfilment systems.

19.5 No professional advice

DiscPay does not provide legal, tax, accounting, financial, regulatory, security, business, or professional advice.

Users are responsible for seeking independent advice where necessary.

20. Limitation Of Liability

20.1 General limitation

To the fullest extent permitted by applicable law, DiscPay will not be liable for indirect, incidental, special, consequential, exemplary, punitive, or economic losses, including loss of profits, loss of revenue, loss of business, loss of goodwill, loss of reputation, loss of opportunity, loss of data, loss of customers, loss of anticipated savings, or business interruption.

20.2 Payment and Token-related limitations

To the fullest extent permitted by applicable law, DiscPay will not be liable for losses arising from:

1. Stripe account restrictions;
2. payment declines;
3. payout delays;
4. chargebacks;
5. disputes;
6. refunds;
7. payment reversals;
8. fraudulent payments;
9. unauthorised payment methods;
10. delayed Token crediting;
11. incorrect Token Balances caused by third-party data or user misuse;
12. duplicate credits corrected by DiscPay;
13. Token freezes or restrictions;
14. failed or delayed reward fulfilment by Server Owners;
15. Server Owner tax obligations; or
16. Server Owner misuse of DiscPay.

20.3 Discord and third-party limitations

To the fullest extent permitted by applicable law, DiscPay will not be liable for losses caused by Discord, Stripe, banks, payment networks, hosting providers, domain providers, email providers, external fulfilment systems, third-party APIs, or other third-party services.

20.4 Enforcement-related limitations

To the fullest extent permitted by applicable law, DiscPay will not be liable for losses resulting from good-faith enforcement action, including suspension, termination, Store disabling, checkout restriction, Token freezing, Token reversal, Reward removal, permission restriction, onboarding refusal, or investigation.

20.5 Liability cap

To the fullest extent permitted by applicable law, DiscPay’s total aggregate liability arising out of or relating to these Terms or the service will be limited to the greater of:

1. the total DiscPay platform fees actually received by DiscPay from the relevant Server Owner in the three months before the event giving rise to the claim; or
2. £100.

For Buyer claims, DiscPay’s total aggregate liability will be limited to the amount of DiscPay platform fees, if any, actually received by DiscPay in connection with the Buyer’s relevant Transaction, or £100, whichever is greater.

20.6 Liability that cannot be excluded

Nothing in these Terms excludes or limits liability where it would be unlawful to do so.

This may include liability for death or personal injury caused by negligence, fraud, fraudulent misrepresentation, or other liability that cannot be excluded under applicable law.

21. Indemnity

21.1 Server Owner indemnity

To the fullest extent permitted by applicable law, each Server Owner agrees to indemnify, defend, and hold harmless DiscPay, its directors, officers, employees, contractors, agents, service providers, and affiliates from and against any claims, losses, liabilities, damages, costs, expenses, penalties, fees, or demands arising out of or relating to:

1. the Server Owner’s use of DiscPay;
2. Rewards offered by the Server Owner;
3. Reward descriptions;
4. failed fulfilment;
5. Buyer complaints;
6. refunds, disputes, or chargebacks;
7. tax obligations;
8. Prohibited Use;
9. Staff or Operator conduct;
10. permission misuse;
11. Stripe account issues;
12. Discord rule violations;
13. third-party platform rule violations;
14. intellectual property infringement;
15. misleading Store content;
16. illegal activity;
17. breach of these Terms; or
18. breach of applicable law.

21.2 Operator, Staff, Buyer, and user indemnity

To the fullest extent permitted by applicable law, each user agrees to indemnify, defend, and hold harmless DiscPay from and against claims, losses, liabilities, damages, costs, expenses, penalties, fees, or demands arising out of or relating to that user’s breach of these Terms, misuse of DiscPay, Prohibited Use, fraud, payment abuse, chargeback abuse, unauthorised access, infringement, security abuse, or violation of law.

21.3 Indemnity procedure

DiscPay may control the defence and settlement of any claim subject to indemnity.

A user must cooperate with DiscPay in defending or resolving any such claim.

A user must not settle any claim in a way that imposes obligations, admissions, or liability on DiscPay without DiscPay’s prior written consent.

22. Changes To These Terms

22.1 Right to change Terms

DiscPay may update, modify, replace, or supplement these Terms from time to time.

Changes may be made for legal, operational, technical, security, fraud-prevention, payment-processing, Stripe, Discord, product, commercial, or platform reasons.

22.2 Notice of changes

Where reasonably practical, DiscPay will provide at least 14 days’ notice before material changes to these Terms that significantly affect existing Server Owners or users.

Notice may be provided by email, website notice, dashboard notice, Discord bot message, admin console notice, Store notice, or another reasonable method.

DiscPay may make immediate or shorter-notice changes where necessary for legal compliance, security, fraud prevention, payment processor requirements, Discord requirements, emergency operational reasons, or platform protection.

22.3 Acceptance of updated Terms

Continued use of DiscPay after updated Terms take effect means that you accept the updated Terms.

If you do not agree to updated Terms, you must stop using DiscPay before the updated Terms take effect.

A Server Owner who does not accept updated Terms may need to disable Store Pages, stop using checkout, stop accepting Token purchases, remove DiscPay from their Server, or contact DiscPay support regarding account closure or suspension.

23. Notices And Contact

23.1 Contact email

DiscPay may be contacted at:

support@discpay.net

DiscPay may later provide additional contact routes, support portals, dashboards, Discord support servers, ticket systems, or legal notice addresses.

23.2 Notices to Server Owners

DiscPay may send notices to Server Owners using the email address provided during onboarding, dashboard notices, website notices, Discord bot messages, Discord direct messages where available, admin console notices, Store notices, or other reasonable methods.

Server Owners are responsible for keeping their contact email accurate and accessible.

A notice sent to the email address provided by the Server Owner may be treated as delivered even if the Server Owner fails to read it, loses access to the email account, or does not keep contact information updated.

23.3 Notices to Buyers and other users

DiscPay may provide notices to Buyers or other users through Store Pages, checkout notices, Discord messages, bot messages, support replies, website notices, email where available, or other reasonable methods.

23.4 Legal notices

If a user needs to send a legal notice to DiscPay, the notice should be sent to support@discpay.net unless DiscPay provides a separate legal notice address.

DiscPay may require legal notices to include sufficient information to identify the sender, Server, Transaction, issue, and legal basis of the notice.

23.5 Complaints

If you have a complaint about DiscPay, you should contact support@discpay.net with enough information to identify your account, Server, Transaction, and issue. If your complaint concerns a Reward, fulfilment, moderation decision, refund decision, or Server-specific issue, you may also need to contact the relevant Server Owner. DiscPay may review complaints but does not guarantee a particular outcome.

24. Governing Law

24.1 Governing law

These Terms, and any dispute or claim arising out of or relating to them, DiscPay, Tokens, Stores, Rewards, or related services, are governed by the laws of England and Wales.

24.2 Courts

Subject to any mandatory consumer rights or other legal rules that cannot be excluded, the courts of England and Wales will have exclusive jurisdiction over disputes arising out of or relating to these Terms or DiscPay.

24.3 Mandatory rights

Nothing in these Terms limits any mandatory legal rights that cannot lawfully be excluded or restricted.

If a user is a consumer in a jurisdiction where mandatory consumer protection rules apply, those rules may apply to the extent required by law.

25. Assignment, Severability, And Survival

25.1 Assignment by DiscPay

DiscPay may assign, transfer, novate, subcontract, delegate, or otherwise deal with its rights and obligations under these Terms.

This may include transfer to a successor entity, group company, purchaser, acquirer, reorganised business, or other entity that operates DiscPay.

DiscPay may transfer operation of the service, contracts, records, systems, data processing arrangements, and related rights and obligations to a successor entity, group company, purchaser, acquirer, reorganised business, or other entity where necessary or appropriate.

25.2 Assignment by users

Users may not assign, transfer, delegate, sell, or otherwise deal with their rights or obligations under these Terms without DiscPay’s prior written consent.

A Server Owner may not transfer their onboarding, Stripe connection, Server approval, Store configuration, or DiscPay account control to another person without following DiscPay’s supported ownership-change or re-onboarding process.

25.3 Severability

If any provision of these Terms is found to be invalid, unlawful, or unenforceable, that provision will be limited, modified, or removed to the minimum extent necessary.

The remaining provisions will continue in full force and effect.

25.4 No waiver

If DiscPay does not enforce a provision of these Terms immediately, that does not mean DiscPay has waived the right to enforce it later.

Any waiver must be in writing to be effective.

25.5 Entire agreement

These Terms, together with any policies incorporated by reference, form the entire agreement between you and DiscPay regarding use of the service, except where a separate written agreement expressly applies.

25.6 Survival

Any provisions that by their nature should continue after suspension, termination, Server disconnection, account restriction, Store removal, or cessation of use will survive.

This includes, without limitation, provisions relating to:

1. payment records;
2. Token records;
3. refunds;
4. chargebacks;
5. disputes;
6. taxes;
7. data retention;
8. logs;
9. intellectual property;
10. disclaimers;
11. limitation of liability;
12. indemnity;
13. governing law;
14. enforcement;
15. ownership changes;
16. Prohibited Use;
17. fraud prevention; and
18. legal compliance.

25.7 Headings

Headings are used for convenience only and do not affect interpretation of these Terms.

25.8 Interpretation

Words such as “including”, “includes”, and “without limitation” are illustrative and do not limit the scope of the relevant clause.

References to a feature, tool, workflow, policy, Store, Token, Reward, or system include any updated, replaced, renamed, modified, or successor version where the context allows.

25.9 Language

These Terms are written in English.

If DiscPay provides a translation, the translation is for convenience only unless DiscPay expressly states otherwise. In the event of conflict between the English version and any translation, the English version will apply to the fullest extent permitted by applicable law.

End of Terms of Service