> For the complete documentation index, see [llms.txt](https://doc.d1ce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.d1ce.com/third-party-payment-disclaimer.md). # Third-Party Payment Disclaimer Before proceeding with your top-up, please carefully read the following terms. By using a third-party payment method to complete your transaction, you acknowledge that you have read, understood, and agreed to comply with all terms outlined below. **1. SCOPE OF TERMS** These terms apply to all users who elect to process payments or complete account top-ups via third-party payment platforms through our website. **2. INDEPENDENCE OF THIRD-PARTY PAYMENT PROVIDERS** (a) Independent Operation: All third-party payment platforms operate independently and are not affiliated with, owned, or controlled by this website. (b) Service Interface: Our website solely provides an interface or redirection to third-party services and does not directly process, manage, or interfere with payment transactions. (c) Governing Terms: Third-party services, including payment processors, e-wallets, and banking partners, are subject exclusively to their respective terms and regulatory conditions. **3. DISCLAIMER OF LIABILITY** (a) Limitation of Liability: The website bears no liability for issues arising from third-party payment usage, including failed or delayed transactions, fraud, data breaches, regulatory holds, transaction fees, or foreign exchange losses. (b) Dispute Resolution & Release: Users assume all legal responsibility for third-party transactions. The website is not a party to payment disputes, provides no compensation or arbitration, and users agree to fully release and hold the website harmless from any related claims. **4. RISK ACKNOWLEDGEMENT** (a) Account Ownership: Users must ensure that the payment account or card used for top-ups belongs to them and is legally authorized for use. (b) Anti-Fraud Requirement: Utilizing third-party accounts, fraudulent payment methods, or illicit funds is strictly prohibited. (c) Policy Compliance: Users are solely responsible for understanding and adhering to all operating rules, limits, and policies of their chosen payment provider. **5. REFUND AND TRANSACTION POLICY** (a) Finality of Transactions: All successful top-up transactions processed via third-party platforms are non-refundable and non-reversible, except where mandatory by applicable law. (b) User Processing Errors: Any mistaken transfers or transaction errors resulting from user negligence must be addressed directly with the third-party payment provider. **6. PLATFORM RIGHTS** (a) Service Modification: We reserve the right to modify, suspend, or terminate any third-party payment options at our sole discretion without prior notice. (b) Fraud Prevention Controls: Suspicious, high-risk, or irregular payment transactions may result in immediate account suspension and reporting to regulatory and law enforcement authorities. **7. LEGAL NOTICE** (a) Service Provider Status: The website operates solely as an interactive gaming service platform and does not function as a financial institution; we do not manage, store, or hold user deposits. (b) Regulatory Responsibility: Users agree that all statutory obligations concerning financial regulations, anti-money laundering (AML) compliance, and source-of-funds verification remain with the user and the payment provider. (c) Waiver of Claims: By using third-party payment services, the user expressly waives all rights to initiate legal action, arbitration, or compensation claims against the website for any related payment disputes or failures. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.d1ce.com/third-party-payment-disclaimer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.