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
  1. Reference Guide

Support & Contacts

PreviousWebhook Event ReferenceNextIntegration Support

Last updated 10 days ago

Support & Contacts

Purpose

This section explains how to get help—whether you are integrating for the first time or running live traffic in production. It points you to the right channel, sets expectations for response times, and defines severity levels.

Quick-contact table

Need
Email
Coverage (America/New York)

Technical / production issues

24 × 7

General inquiries (billing, partnership, docs)

Mon – Fri, 09:00 – 18:00

Severity matrix

Severity
Examples
First response target

P1 – Critical

API unavailable, payments failing globally

30 min

P2 – High

Single merchant blocked, webhook backlog, major latency

2 h

P3 – Normal

Non-blocking bug, documentation clarification

1 business day

P4 – Low

Cosmetic issue, enhancement request

2 business days

Where to go next

  • – step-by-step ticket workflow, what details to include, and how we triage issues.

  • – severity definitions re-stated with target status-update cadence and (future) phone or pager details.

Use the email addresses above and the severity guidelines to ensure your request reaches the right team with the right urgency.

Integration Support
Escalation Contacts
support@bead.xyz
info@bead.xyz