Choose a supported provider

Movira supports Stripe, Nuvei, and Razorpay for hosted online payments. Stripe and Nuvei can also support card-present flows when the required terminal integration and POS module are configured.

  • Stripe: online checkout, payment links, recurring payments, and supported Stripe Terminal setups.
  • Nuvei: hosted online checkout and payment links, recurring payments, and supported Nuvei terminal setups.
  • Razorpay: online checkout and payment links; no Movira card-terminal integration.

Choose credential scope

An organization-wide credential is available to every location in the organization. A location-specific credential overrides the organization credential only for that location when the route uses the same provider and mode.

Separate from Movira subscription billing

These credentials collect payments from your guests. Movira uses a separate platform-owned credential to collect SaaS subscription invoices.

Add and test credentials

  1. 1

    Open Payments → Gateways.

  2. 2

    Choose Add gateway and select the provider.

  3. 3

    Choose organization-wide or a specific location.

  4. 4

    Select Sandbox for a demo location or Live for a production location.

  5. 5

    Enter the provider fields and run Test connection.

  6. 6

    Save only after the test succeeds.

Route each payment channel

  1. 1

    Open the location or the Routing view.

  2. 2

    Choose Online booking, Payment link, Recurring, Kiosk, or POS / card terminal.

  3. 3

    Select a provider and the mode required by the location.

  4. 4

    Save the route and confirm it resolves to an active credential.

  5. 5

    For POS, register a terminal and reader after the POS route is ready.

Understand the safeguards

  • Demo locations accept sandbox credentials and routes only.
  • Production locations accept live credentials and routes only.
  • A saved credential does nothing until a channel route points to its provider and mode.
  • Movira resolves a matching location credential first, then an organization-wide credential. A disabled location override blocks unsafe fallback; if no active match exists, the route is unavailable.
  • Provider secrets are encrypted and are not displayed again after saving.

When a route is not ready

  • Confirm the credential scope, provider, and mode match the route.
  • Run Test connection again after rotating provider keys.
  • For Nuvei online payments, confirm the deployed webhook/DMN URL is public HTTPS.
  • For terminals, confirm the POS module, terminal registration, reader assignment, and provider mode.
  • Do not test real cards against a sandbox route.