Support & answers

Submit a request through the form on the site or write to a channel from the Contact page. We confirm your business model, regions, and volumes, then align on documentation and grant access to the test environment.

Typical path: short call → KYC / agreement (depending on entity) → sandbox keys → pre-production checklist → switch to live.

Successful crediting of an incoming payment usually takes from seconds to a few minutes, depending on method and participating bank. For payouts, timing depends on clearing windows and the recipient account type.

In the dashboard and via API you see intermediate statuses (created, processing, success, declined). For declines we surface a code or text reason from the provider where possible, which helps your own user support.

Pricing combines the Averon fee and partner fees for the specific method and country. Final rates are fixed in a commercial proposal for your risk profile and volume.

Supported currencies and FX policy (where applicable) are agreed at onboarding: you can hold separate balances or convert under agreed rules.

Integration uses a REST API with keys for sandbox and production. Webhooks are signed with a secret; we recommend verifying the signature before updating order status in your database.

The sandbox includes success and typical decline scenarios so you can debug retries and idempotency without real money movement.

We minimise personal data to what is needed to process payments and meet legal obligations. Retention and subprocessors are described in the agreement and data appendices.

For higher-bar sectors (fintech, marketplaces) we can add IP restrictions, separate dashboard roles, and log exports for audit.

Contracted customers get a dedicated channel (email / Telegram as agreed) with response targets in business hours. Critical incidents involving funds use a separate escalation path.

The Contact page lists public channels for first contact and registered address — use those if you are not yet in onboarding.