Centro de ayuda

What integrations can BetterSuite support?

Integrations on BetterSuite fall into two categories: built-in adapters for the systems most marketplaces need on day one, and an open extension layer for everything else. You should expect to connect the platform to your real stack — accounting, BI, CRM, support — without building bespoke middleware.

Tiempo de lectura
4 min
Última actualización
12 de abril de 2026
Secciones
3 en esta página
01

Built-in adapters

Out of the box, BetterSuite integrates with regional payment providers, the major messaging channels, SSO providers, mapping and geocoding stacks, and the most-used identity verification services. Each adapter is configured per operator — you do not write code to enable them.

  • Payments: Stripe, Adyen, regional PSPs with per-country routing
  • Messaging: SMS, WhatsApp Business, email, and push
  • Identity: passkeys, SSO, email codes, mobile OTP
  • Maps: Google Maps and Mapbox, configurable per region
  • KYC and document verification for drivers and providers
02

Extending the platform

Beyond the built-ins, you have two extension paths. Use the GraphQL API to read and write platform data from your own services. Subscribe to webhooks for state changes — orders, trips, payouts, disputes — and react in your own workflow tools.

Both paths are first-class: the same APIs we use to build the admin console and apps are available to your team.

03

Common workflow patterns

Most operators set up three integration patterns within their first quarter: sync customer activity to a CRM, stream financial events to accounting, and route operational alerts into a shared Slack or Teams channel. None of these requires new infrastructure on your side.

¿Le ha resultado útil este artículo?

¿Necesita algo más concreto?

Si su situación va más allá de lo que cubren los artículos, cuéntenosla y el equipo le responderá con un primer plan.

Contactar con el equipo