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
  2. Support & Contacts

Escalation Contacts

Escalation contacts

Current state – We handle all external issues via email. Phone hotlines and chat channels will be added later. Use the addresses below and include the information requested in the “What to send” section so we can route your ticket quickly.

Support email addresses

Purpose
Email
Coverage window (America/New York)
First response target

Technical / production issues

24 × 7

See severity table

General inquiries (billing, partnership, docs)

Mon – Fri, 09:00 – 18:00

1 business day

Severity definitions & target response

Severity
Example situations
First response
Status updates

P1 – Critical

API unavailable, payments failing for all merchants

30 minutes

60 minutes

P2 – High

Webhook backlog, single merchant blocked, major performance degradation

2 hours

4 hours

P3 – Normal

Non-blocking bug, doc clarification, feature question

1 business day

1 business day

P4 – Low

Cosmetic issue, enhancement request

2 business days

Weekly

What to send

  • Merchant ID / Terminal ID / Tracking ID involved

  • Timeframe (UTC) and sample request IDs

  • HTTP status codes or error messages received

  • Steps to reproduce, if known

  • A callback email or Slack handle for follow-up

We’ll triage the ticket to the right engineering or operations team and keep you updated according to the targets above.

PreviousIntegration SupportNextChangelog

Last updated 10 days ago

support@bead.xyz
info@bead.xyz