Stripe

Use Stripe from Ormuz to manage customers, collect SEPA mandates, initiate debits and bank transfers, and reconcile payment activity from provider events.

17Nodes
57Events
10Provider objects
0Workflows
Definition

Nature and scope

Integration typeService extension
Business capabilities
Integration mechanismsrest_apiwebhook
Use cases

What this extension lets you build

  • Collect interactive card payments with Stripe Payment Element while keeping the Ormuz PSP payment as the financial source of truth.
  • Create or reuse the Stripe customer associated with an Ormuz company or contact.
  • Collect a mandate in Journey and trigger off-session SEPA debit payments.
  • Generate bank transfer instructions and create customer-balance PaymentIntents.
  • Receive Stripe events and synchronize payments, balances, and transaction status.
Journey examples

Collect and reconcile Stripe payments

Stripe can handle cards, mandates, direct debits, or bank transfers while Ormuz preserves business objects and reconciliation logic.

1. Collect a card payment

Ormuz creates the PSP payment and then displays Stripe Payment Element to collect and authenticate the card.

Ormuz object
Create the PSP payment
Source objectpsp_payment
Action
Collect the card payment
Event
Confirm the PaymentIntent
Business outcome
Continue reconciliation
Node Ormuzreconcile_payment

Amount and currency come from the PSP payment; the Stripe result is verified server-side before synchronizing the Ormuz object.

2. Collect a SEPA mandate

The buyer is associated with a Stripe Customer and then redirected to a mandate-collection experience.

Ormuz object
Identify the buyer and contact
Source objectscompany + contact
Action
Create or find the Customer
Action
Collect the mandate in the hosted experience
Business outcome
Retain the reusable mandate
Provider objectstripe.mandate

The Customer ↔ company mapping allows later processes to resolve the correct Stripe account.

3. Debit and synchronize the payment

An issued invoice triggers the off-session debit, then a Stripe event updates the Ormuz PSP payment.

Event
Invoice ready for debit
Ormuz eventinvoice.issued
Action
Create the payment intent
Node Corecreate_psp_payment
Action
Trigger the SEPA debit
Event
PaymentIntent succeeded
Action
Synchronize the PSP payment
Business outcome
Make the payment allocatable
Ormuz objectpsp_payment

The invoice is marked paid only after payment allocation, not merely on receipt of the provider event.

4. Receive a customer-balance bank transfer

Ormuz generates bank-transfer instructions, waits for funds, then synchronizes the associated PaymentIntent.

Action
Create bank-transfer instructions
Action
Create the payment intent
Node Corecreate_psp_payment
Action
Create the transfer PaymentIntent
Event
Receive available funds
Action
Synchronize the PSP payment

Cash-balance movements remain provider objects; the normalized `psp_payment` is used for business reconciliation.

Documentation

Browse the documentation

Review the configuration, nodes, events, objects, and access declared by this extension.