Support
XKOVA support helps developers and startups integrate and operate stablecoin rails. Capture the error code, correlation ID and request timestamp when reporting a problem.
Get Help
Visit XKOVA Support to ask the AI assistant, open a ticket, or request a person. The assistant uses public documentation and the XKOVA website and cites its sources. Check XKOVA System Status for current service observations and incident updates.
For staging integration work, use staging support and staging system status. Confirm the installation before sharing diagnostics.
Prepare a Support Request
Include the installation, workspace mode, affected product, request timestamp with timezone,
error code, correlation_id, and steps to reproduce the problem.
Add the chain ID and transaction hash when a public-network transaction is involved.
A transaction hash helps identify an operation; it does not prove account ownership or settlement success.
Use the support portal or the support contact available in your workspace. Check the assistant's cited source and request a person when the answer does not resolve the issue. Support does not require you to give another person your API key or wallet credentials.
Installation and Workspace Mode
Installation identifies where the software runs. Workspace mode identifies the network tier. Every sandbox workspace uses supported testnets. Every production workspace uses supported mainnets, including workspaces on the staging installation. The two modes have separate keys and data.
| Workspace Mode | Use | What to Record |
|---|---|---|
| Sandbox | Integration testing with supported testnet assets and deterministic provider scenarios. | Sandbox endpoint, scenario if used, chain ID, error code and correlation ID. |
| Production | Approved live operations on supported mainnets. | Production endpoint, timestamp, error code, correlation ID and transaction hash if available. |
Production access requires approval. Sandbox availability does not grant production execution authority. Data is protected in both workspace modes. A sandbox or testnet label does not make records disposable.
Share Diagnostics Safely
Never include passwords, API keys, authorization headers, private keys, seed phrases or payment-card details. Remove personal information from screenshots and logs unless it is necessary for the request. Describe the expected and observed behavior, and include the smallest useful reproduction.
Platform and End-User Support
XKOVA support covers the integration and platform behavior. People using an application built on XKOVA contact that application's support team for account questions. Support conversations do not authorize account impersonation, policy changes, transaction signing or movement of funds.
Service Status and Response Commitments
See System Status for how service observations and incident updates should be interpreted. A healthy service observation does not establish that a particular transaction settled.
This guide does not promise a response deadline, 24-hour staffing, refunds, fund recovery or a service-level agreement. Any applicable response commitment must be explicitly included in your published plan or agreement.
Related
See FAQ and Troubleshooting, Errors and Correlation IDs, Networks and Tokens, and Changelog.