Bead Developers
  • Introduction
  • Quick Start
  • Authentication
  • Payments
    • Create Payment
    • Payment Statuses
    • Payment Webhooks
    • Test Transactions - Crypto
    • Changelog
  • Entity Management
    • Onboarding
    • Merchant Management
      • Get Merchant
      • Changelog
    • Location Management
      • Create Location
      • Get Location
      • List Locations
      • Update Location
      • Delete Location
      • Changelog
    • Terminal Management
      • Terminal Lifecycle (Concepts)
      • Create Terminal
      • Get Terminal
      • List Terminals
      • Update Terminal
      • Delete Terminal
      • Webhook Management
      • Changelog
  • Settlement
    • Batches
    • Settlement Details
  • Reporting
    • Payment History Concepts
      • Pagination and Sorting
    • Partner Payments
    • Merchant Payments
    • Terminal Payments
    • Changelog
  • Reference Guide
    • Core Concepts
      • Environments & Base URLs
      • Authentication
      • Error Codes
    • Enumerations & Schemas
      • Tender Types
        • Crypto
        • Alternative Payments
      • Settlement Currencies
      • Common Field Types
    • Endpoint Index
      • Table View (All APIs)
      • Download OpenAPI / Postman
    • Payment Scenarios
      • Under- and Over-Payment Handling
      • Reclaiming Unconverted Crypto
    • Operational Guides
      • Compatible Crypto Wallets
      • Webhook Event Reference
    • Support & Contacts
      • Integration Support
      • Escalation Contacts
    • Changelog
  • FAQs & Troubleshooting
    • Authentication FAQs
    • Payments FAQs
      • Resolving “403 Forbidden” When Creating Payments
    • Environment & Testing
      • How to Test Klarna Payments
      • How to Prepare for USDC Testing
      • How to Test Klarna Payments
    • Webhooks & Error Codes
Powered by GitBook
On this page
  • Purpose
  • What you’ll find here
  • How to use these pages
  • Versioning
  1. Reference Guide

Enumerations & Schemas

PreviousError CodesNextTender Types

Last updated 10 days ago

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

Page
Contents

Lists every crypto and alternative-payment tender string, with network notes and decimals.

Shows each enabled fiat, crypto, or wallet-app currency returned by /currencies, including code, network, and status.

Defines shared patterns such as 24-char IDs, ISO-8601 timestamps, money amounts, and the Address object.

How to use these pages

  1. Validate input: reject values not present in the corresponding enum list.

  2. Display names and symbols: map the code or tender string to the human-readable name provided here.

  3. 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. Check the changelog before each release cycle.

Tender Types
Settlement Currencies
Common Field Types