> For the complete documentation index, see [llms.txt](https://remittix-organization.gitbook.io/remittix-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://remittix-organization.gitbook.io/remittix-whitepaper/1.0-executive-summary.md). # 1.0 Executive Summary Digital assets have become a major component of the global financial system, yet moving value between crypto networks and traditional banking infrastructure remains unnecessarily fragmented. Cryptocurrency can be transferred globally within minutes, but converting that value into usable fiat money often still requires multiple platforms, exchanges, wallets and banking processes. For businesses, consumers and crypto-native organisations, this creates a gap between holding digital assets and using them efficiently within the traditional financial system. Remittix is being developed to bridge that gap. At the centre of the Remittix ecosystem is a PayFi platform designed to allow users to initiate payments using digital assets while enabling recipients to receive conventional fiat currency through supported banking and local payment infrastructure. Rather than requiring the recipient to own cryptocurrency, manage a wallet or understand blockchain technology, Remittix is designed to abstract that complexity from the payment experience. A typical Remittix payment can be represented simply: **Digital Asset → Remittix PayFi → Conversion & Payment Routing → Fiat → Recipient Bank Account** This model allows blockchain-based value to interact with conventional financial infrastructure while preserving a familiar payment experience for the recipient. Remittix has progressed substantially beyond its original concept. During its development cycle, the project has moved through smart-contract deployment, independent contract auditing, wallet development, PayFi infrastructure development, product testing and successful testing of crypto-to-fiat payment functionality. This progression has allowed the Remittix vision to expand beyond a single payments product into a wider digital financial ecosystem. The ecosystem is being developed around four principal components: ## Remittix PayFi The core payments layer designed to connect digital assets with fiat settlement infrastructure and enable crypto-funded payments to supported bank accounts and payment destinations. ## Remittix Wallet A non-custodial wallet designed to provide users with control over their digital assets while acting as an access point to the broader Remittix ecosystem. ## Remittix Markets A perpetual futures trading platform built on established decentralised trading infrastructure, expanding the Remittix ecosystem into on-chain derivatives markets. ## Remittix Earn A digital-asset yield platform designed to allow users to earn returns on supported assets including stablecoins and other cryptocurrencies. These products are designed to operate as interconnected components of a broader ecosystem centred around RTX, the native Remittix token. RTX has a fixed maximum supply of 1.5 billion tokens and acts as the native digital asset of the Remittix ecosystem. Its utility is being introduced across PayFi, Markets, Earn and other ecosystem products as those mechanisms are formally announced. Remittix does not seek to recreate every component of global financial infrastructure itself. Instead, its architecture is designed to integrate specialised third-party infrastructure for functions such as payment processing, fiat settlement, regulatory compliance and decentralised market execution. This allows Remittix to concentrate on building a unified product experience while connecting users to established financial and blockchain infrastructure beneath the interface. For regulated payment activity, relevant compliance procedures, including applicable identity verification, enhanced due diligence, anti-money-laundering controls and sanctions screening, are performed by authorised third-party infrastructure providers according to their respective regulatory obligations and geographic permissions. This modular architecture is intended to support expansion across multiple assets, blockchain networks, fiat currencies and payment corridors without requiring Remittix to operate every underlying financial rail directly. The long-term objective is broader than simplifying cryptocurrency withdrawals. Remittix is building toward an environment in which the asset held by the sender and the currency required by the recipient no longer need to match. A user may hold value in cryptocurrency. A recipient may require euros, dollars or another local currency. The role of Remittix is to provide the infrastructure connecting those two environments. In this model, blockchain becomes the value layer, traditional payment systems remain the settlement layer, and Remittix acts as the bridge between them. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://remittix-organization.gitbook.io/remittix-whitepaper/1.0-executive-summary.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 `build a script that syncs our docs to a CMS` 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.