> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-platform-1/xyb-payments/welcome-to-xyb-payments.md). # Welcome to XYB Payments! Welcome to the XYB Payments Platform! A modern, API-first payment orchestration layer built for banks, fintechs, and financial institutions who want full control over how money moves. Whether you're sending payroll, processing user transfers, or integrating card payouts, our platform helps you **build it faster, scale it confidently, and stay compliant.** ***
Getting StartedXYB Payments overviewcard-getting-started.png
Payment Setup & ArchitectureUnderstanding the XYB Payment Ecosystemcard-integrate.png
Workflows & Payment LifecyclesPlanning your Payments Infrastructurecard-workflow.png
Payment Operations & SupportBuild a Customer Facing Fund Transfer Flowuser ops.png
--- # 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://docs.xyb.co/xyb-platform-1/xyb-payments/welcome-to-xyb-payments.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.