# Overview This guide helps you understand the core concepts used to structure RocketFuel API data. Understanding these core concepts will make it easier for you to work with our resources and build integrations with the RocketFuel APIs. It's helpful to understand these terms within our platform and how they relate to each other. **Core Concepts** 1. Partners 2. Merchants 3. Shoppers 4. Exchanges 5. QR Payments 6. Bank Payments 7. Invoices 8. Settlements Partners introduce merchants to RocketFuel's bank transfer and volatility-proof cryptocurrency payment solution and earn a commission on every transaction they process. Merchants can choose to sign up on RocketFuel's system by visiting the link [https://merchant-sandbox.rocketfuelblockchain.com ](https://merchant-sandbox.rocketfuelblockchain.com). They can offer their goods/services on their website and accept payments in Cryptocurrency or via bank using RocketFuel's solution. Shoppers are the customers who buy goods or services from merchants and pay them in exchange for goods/services they are purchasing. When shoppers pay to merchants, they can connect their exchanges, such as Coinbase, OkCoin, Gemini, etc. and pay using those exchanges. Also, the other payment options available to shoppers are from their crypto wallet by scanning the QR code or bank. For bank payments, shoppers will need to connect their bank account. Invoices help merchants use RocketFuel's solution outside their website, and shoppers can just visit an invoice link to make the payment. All the money earned by the merchants using RocketFuel's solution is settled daily to the merchants by RocketFuel. --- # Agent Instructions: 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: ``` GET https://docs.rocketfuel.inc/core-concepts/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.