CROSSFX SUPPORT
Get the right help. Faster.
Technical and operational support for your CrossFX integration, transactions, webhooks and testing.
The more context you include in your first message, the faster our team can identify the request, transaction or delivery attempt involved.
API integrationTransactionsWebhooksSandbox
How we can help#
CrossFX provides technical and operational support throughout your integration and live transaction lifecycle.Integration
Build and troubleshootAPI integration support, credentials, Sandbox testing, API errors and implementation questions.
Transactions
Investigate transaction stateTransfer, deposit and payout enquiries, settlement questions and corridor-specific operational issues.
Webhooks
Debug event deliveryWebhook delivery, event investigation, subscriptions and delivery-attempt troubleshooting.
Support also covers corridor availability and rules, operational questions and testing assistance.
Support channels#
Use the channel that best matches what you need.Onboarding
Credentials, access and onboarding[onboarding@crossfx.com](mailto:onboarding@crossfx.com)
Use this address for onboarding requests, credentials and access questions.
Technical & API help
Integration and operational support[support@crossfx.com](mailto:support@crossfx.com)
Use this address for API errors, integration help, webhook debugging and transaction investigations.
What to include in a support request#
A useful support request gives us enough information to identify the exact transaction, API request or webhook delivery involved.FASTEST WAY TO FIND AN API ERROR
Always include the error_id
Every platform error body carries an error_id. Quoting it is the single fastest way for our team to locate the request in CrossFX logs.
For anything involving a transfer, deposit or payout, include the identifiers that apply.cbtx_tracking_idTransfer identifier
Include for every transaction-related investigation.
deposit_idDeposit identifier
Include when the issue involves the funding leg.
payout_idPayout identifier
Include when the issue involves disbursement.
error_id from the error body, if you received one
Relevant timestamps in UTC
If the issue concerns a payout, also provide:Beneficiary details, masked where needed
Country and payout method
Transfer amount and currency
Webhook delivery issues#
If an expected webhook did not arrive, include the event and subscription details so we can trace delivery.Event ID
Which event?Include the event `id` from [Search Webhook Events](/42801043e0).
Delivery attempt ID
Was delivery attempted?Include the delivery attempt `id` from [Search Webhook Delivery Attempts](/42801046e0), if an attempt was recorded.
Subscription ID
Where should it have gone?Include the `subscription_id` of the endpoint that should have received the event.
Additional context#
The following information is not always required, but can materially reduce investigation time:Sanitised API request body
Remove secrets, credentials and any unnecessary sensitive information before sending logs or request bodies to support.
Business hours & escalation#
Standard support hours
Monday to Friday09:00 to 18:00 EAT
East Africa Time
**Weekend**
Limited cover for urgent issues.
Urgent out-of-hours issue
Email: support@crossfx.comPut `URGENT` in the subject line and include the `cbtx_tracking_id` in the body.
Direct escalation contacts are shared with your team during onboarding.
OUT-OF-HOURS FORMAT
Subject: URGENT — brief description of issue
Body: Include the relevant cbtx_tracking_id and supporting context.
Frequently asked questions#