KEY TAKEAWAYS
- Support tickets are tracked from your dashboard.
- Never share your API key, password or wallet seed.
- Include check references and timestamps for billing questions.
We are a small operations team, so the fastest route is always a support ticket or email with your account email and the relevant check reference.
Support channels
- Support ticket: open one from your dashboard — it is tracked and answered in order.
- Support ticket: open one from your dashboard.
What to include
- Your account email (never send your password or API key).
- For billing questions: the date/time of the check and the amount.
- For API help: the endpoint, a request ID and the error response (mask card data).
- For bulk or subscription pricing: expected monthly volume and target gateways.
Security
We never ask for your API key, seed phrase or private keys. Anyone asking for those is not us. See our terms and privacy policy.
Getting support
The fastest route is the in-dashboard ticket system: it keeps your question, account context and history in one thread. Open a ticket from the Support page after signing in, and replies are delivered back to the dashboard.
For account, billing or integration questions you can also email the in-dashboard support form. Include your account email and, when relevant, the check ID or invoice reference from history — it shortens the round trip considerably. Never send full card numbers or your API key by email.
Response times
Tickets are triaged during business days, with most answered within one business day. Billing questions related to deposits or charges are treated as priority. If you have not heard back within two business days, reply in the same thread to re-open it.
What to include in a request
- Your account email (never the password or API key).
- The check ID, invoice reference or deposit transaction ID when relevant.
- The gateway and input format used, for check-related issues.
- A description of the expected and observed behaviour.
Before you write in
Several questions resolve themselves in the documentation. Billing follows a single rule — classified results are charged, errors are not — so a charge with a live or dead result is expected, and a run full of errors should cost nothing. Deposit crediting is automatic once a transaction confirms on-chain; if the network is congested, the dashboard shows the invoice as pending until it does. Check history holds a row per request with cost and outcome, which usually answers "what happened to my balance" faster than a ticket can.
Escalation
If a ticket goes unanswered for more than two business days, reply in the same thread; threads are re-queued rather than re-created, so all context stays attached. Security reports — a suspected key leak, an unexpected login, a billing anomaly — should be marked clearly in the subject line and are prioritised. There is no phone support; everything runs through tickets and email so that every exchange is written down and attached to the account.