> 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/core-banking-components/payment-operations-and-workflows.md). # Payments The **Payments Framework** is designed to support secure, and scalable payment operations. Whether you're handling high-volume batch transactions or low-latency real-time payments, the framework provides the flexibility and control needed for modern financial institutions. **Key Highlights:** * Real-time and batch processing for domestic and international payments * Multi-currency support with built-in FX handling * Automated payment approvals based on customizable thresholds * Integrated reconciliation with ledger alignment and reporting * Fraud and compliance monitoring using rule-based and AI-driven checks The framework allows institutions to define payment workflows tailored to internal policies, regulatory requirements, and customer expectations. From payment initiation to final settlement, each step can be configured and monitored for accuracy and efficiency. By implementing the Payments Framework, banks can simplify operations, strengthen compliance, and offer faster, smarter payment experiences to their customers. --- # 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://docs.xyb.co/core-banking-components/payment-operations-and-workflows.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.