> For the complete documentation index, see [llms.txt](https://docs.bill-z.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bill-z.com/payment-rails.md). # payment rails Billz Pro executes payments through regulated fiat rails and documents them for treasury workflows. ## SEPA (EUR) SEPA is the standard EUR bank transfer rail used across supported jurisdictions. ### Typical characteristics * recipient identified via **IBAN** * bank cutoffs and holidays apply * reference/memo handling may vary by downstream institutions ### Common Billz Pro uses (EUR) * vendor invoices * rent * utilities * recurring operational expenses *** ## ACH (USD) ACH is the standard US domestic bank transfer rail for USD payments. ### Typical characteristics * recipient identified via routing + account details * bank processing windows apply * settlement often 1–3 business days (not guaranteed) ### Common Billz Pro uses (USD) * US vendors * operating expenses * supported business payments *** ## Why this matters for positioning Billz Pro is not only converting crypto.\ It is an **execution layer** that bridges treasury operations into these rails with: * structured payment intent, * compliance checks, * proof-oriented documentation. --- # 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.bill-z.com/payment-rails.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.