Contact Support

Get help from the Zentra team

Contact Support

Reach the right Zentra team quickly. The goal is fewer loops, clearer routing, and better context on the first message.

Support Channels

Technical Review

[e-mail]

Best for:

• integration errors
• API behavior questions
• webhook handling and retry issues
• rollout blockers in sandbox or live

Commercial Review

[e-mail]

Best for:

• pricing and launch scope
• regions and rollout model
• enterprise review
• commercial onboarding

Trust Review

[e-mail]

Best for:

• compliance posture
• security and control review
• data-handling questions
• audit evidence requests

Status Page

status.usezentra.com

Best for:

• checking active incidents
• confirming platform availability
• verifying whether an issue is already known

Before You Contact Us

1. Check the docs

   Search the API Reference, FAQ, and reviewed surface policy first.

2. Confirm environment and scope

   Note whether the issue is in sandbox or live, and whether it affects money movement, identity, webhooks, or operator access.

3. Gather the right evidence

   Include:

   • request or event ids
   • endpoint or namespace used
   • stable reference or idempotency key
   • expected behavior vs actual behavior
   • the smallest code sample that reproduces the issue
4. Check service status

   Review status.usezentra.com before escalating a suspected outage.

Email Template

When emailing the team, include:

Subject: [Issue Type] Brief Description

Environment: Sandbox / Live
API Key (last 4 chars): sk_****abcd

Issue Description:
[Describe the issue clearly]

Expected Behavior:
[What you expected]

Actual Behavior:
[What happened instead]

Steps to Reproduce:
1. [First step]
2. [Second step]
3. [etc...]

Request or Event IDs:
[If available]

Relevant Reference:
[Business reference or idempotency key]

Response Expectations

Priority	Typical Scope	Response Time
Critical	live outage, blocked money movement, security issue	under 4 hours
High	major degraded workflow, repeated webhook or auth failures	within 1 business day
Standard	integration guidance, rollout questions, non-blocking bugs	within 2 business days

Security and Trust

For security disclosures or trust review requests, contact [e-mail] and include:

• issue summary
• impact assessment
• reproduction steps
• affected environment
• any evidence or logs with sensitive values masked

Do not post potential vulnerabilities publicly.

Helpful Links

Developer Console

Manage API keys, webhook endpoints, and account settings.

API Reference

Review current public and reference surfaces.

Postman Collection

Use a ready-to-run collection for local testing.

Going Live

Work through the launch-readiness checklist.

FAQ

Check common questions before opening a thread.

Website

Route broader commercial or partnership conversations through the main site.