Integrations

What is connected, and what still needs credentials

Every integration carries a status. We would rather tell you it is not ready than show you a logo that does nothing.

Payments — Restoora Pay Connect

Integration required

A provider-neutral layer. Your organization connects its own eligible merchant account; each branch picks providers by country and sales channel. Card numbers are never stored in Restoora.

  • Stripe — first implementation candidate in supported markets
  • Regional providers — configuration placeholders, not connected
  • In-person terminals — separate integration per provider
  • Cash and external terminal — recorded payment methods, available today

Delivery platforms

Integration required

A connector framework with per-provider credentials and visible connection status. Nothing appears as connected until it is.

  • Provider adapters
  • Menu push
  • Order pull
  • Status callbacks

Fiscal devices and e-invoicing

Integration required

Country-specific fiscal requirements are validated per market before a branch goes live.

  • Italy — fiscal printer interface
  • Germany — TSE requirement
  • Saudi Arabia — ZATCA review pending

Accounting

Integration required

Exports work today; country-specific accounting connectors are built per market. We do not claim legal completeness in any country without validation.

  • CSV and journal exports
  • Supplier bills and expenses
  • Connector framework

Platform API and webhooks

Demo

Authenticated API keys, scopes, idempotent writes, retry handling and observable delivery status for every webhook.

  • API keys with scopes
  • Signed webhooks
  • Retry and backoff
  • Delivery log
Ask about a specific provider