> For the complete documentation index, see [llms.txt](https://0fiat.gitbook.io/0fiat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://0fiat.gitbook.io/0fiat/welcome/about.md). # About 0fiat **Trillions.** That’s how much volume in global payments happens on a daily basis. Whether is is shopping, food, entertainment or even paying things like rent, the global payments industry is large and organized with millions of individuals settling a payment in real time. > **0Fiat exists to make spending crypto feel as simple, fast, and borderless as the internet itself - without banks, cards, or gatekeepers standing in the way.** ### Core belief The world already runs online, but money is still trapped in old rails: cards, banks, KYC walls, and hidden fees. 0Fiat rejects the idea that using crypto for everyday life should be harder than using a credit card. 0Fiat is built on the **belief** that anyone, anywhere, should be able to click “checkout” and pay directly from a wallet they control. ### The Problem * Crypto is spendable in theory, but in practice users are forced into exchanges, cards, and compliance mazes just to buy simple things online. * Card programs add KYC friction, geographic restrictions, and opaque fees that break the promise of instant, global digital money. * Merchants want new customers and higher approval rates, but not the complexity of handling crypto, chargebacks, or failed payments. ### What we stand for * **Pure self-custody**: Your wallet, your keys, your checkout. 0Fiat connects wallets to merchants without demanding banks, cards, or identity dossiers. * **Access without permission**: No KYC verification to start spending; your wallet is enough. * **Fair, transparent costs**: Zero added fees from 0Fiat, avoiding the hidden markups and FX surprises common with crypto cards and legacy rails. * **Reliability at scale**: Higher success rates on transactions so users can trust that “Pay with crypto” actually works when it matters. * **Choice of tools**: Multiwallet support so users are never locked into one provider or ecosystem. ### How we reimagine checkout * 0Fiat lives as a browser extension at the exact moment of checkout, where intent to buy is highest. * The user flow is radically simple: select product, click 0Fiat at checkout, pay with crypto in a few clicks. * Under the hood, 0Fiat abstracts away the complexity of payments so merchants see a seamless purchase and users experience a native crypto transaction. ### The future we’re building 0Fiat tracks global rollouts because the mission is truly borderless: any country, any brand, any user with a wallet should be able to participate in the digital economy. As 0Fiat expands, it layers in rewards: joining bonuses, cashback on every transaction, and higher affiliate payouts so the people who use and share the network also own its upside. 0Fiat is not just a payment option; it is a statement that the next era of commerce will be open, non-custodial, and natively crypto, and that everyday spending should move at the speed of a click, not at the pace of legacy finance. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://0fiat.gitbook.io/0fiat/welcome/about.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.