Developers & Integrations
Start an Integration with Xiibit
Xiibit connects business systems, devices and payment services through a common orchestration layer. Here is how an integration begins.
How We Work with Integrators
Scoped engagements
Integrations are planned with our team. Availability depends on the payment service, device or software you want to connect.
Validation first
We confirm feasibility for your specific bank, device or platform before implementation begins.
Documentation on request
Official documentation is shared as part of an engagement — there is no public self-service onboarding today.
A Typical Integration Path
Every integration differs, but the path generally follows these steps.
- Scope the use case Tell us what you want to connect and the outcome you need.
- Feasibility & architecture review We review the systems involved, confirm feasibility and outline the integration scope.
- Configuration & build The integration is configured and built against the agreed scope, with our team supporting your engineers.
- Certification & pilot Where required, the integration goes through certification and a pilot deployment.
- Rollout & support The connection moves into production with an agreed support path.
Systems and Endpoints
Xiibit connects across these categories — subject to validation for each specific system.
Integration-dependent
Payment services
Banks, payment service providers and DuitNow QR payment flows.
Integration-dependent
Business software
POS systems, SaaS products and merchant-facing software.
Integration-dependent
Devices
Payment terminals, soundboxes and IoT devices — including Edxapay hardware.
Integration-dependent
Unattended environments
Vending machines, self-service kiosks and laundromats.
Each specific connection follows its own path — configuration, certification, a commercial agreement or further development.
Request Integration Documentation
Tell us what you are building and we will share the right documentation and next steps for your integration.