> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/reference-guide/enumerations-and-schemas.md). # Enumerations & Schemas ### Purpose Enumerations & Schemas is the canonical reference for every reusable value set and shared object used across Bead APIs. Use this section to validate request bodies, parse responses, and keep client libraries in sync with the platform. ### What you’ll find here * **Common Field Types** – Reusable objects such as addresses and contacts that appear in multiple APIs. * **Merchant Onboarding Schema** – Complete schema for `POST /merchant-onboarding/application`, including business identity, contacts, owners, banking, and fee configuration. * **Settlement Currencies** – Supported currencies for settlement. * **Tender Types** – Enumerations for supported payment methods. Subpages cover: * **Crypto** – Supported digital assets for crypto payments. * **Alternative Payments** – Supported peer-to-peer and wallet-based payment methods. ### How to use these pages * **Validate input**: Reject values not present in the corresponding enum list. * **Display names and symbols**: Map the code or tender string to the human-readable name provided here. * **Plan for change**: New rows will appear when Bead adds a rail or asset; unknown values should raise a clear error in your integration. ### Versioning Enumerations can grow but never break existing values. Schemas may add optional fields; required fields change only in a new API version. Always check the changelog before each release cycle. --- # 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://developers.bead.xyz/reference-guide/enumerations-and-schemas.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.