'%20fill='%23fbce49'/%3e%3c/svg%3e)
Two
Resolve companies, assess order intent, create and verify orders, fulfil sales, refund buyers, and reconcile invoices and settlements.
18Nodes
11Events
9Provider objects
0Workflows
Definition
Nature and scope
| Integration type | Service extension |
|---|---|
| Business capabilities | |
| Integration mechanisms | rest_apiwebhook |
Use cases
What this extension lets you build
- Offer invoice payment during an online B2B checkout.
- Request buyer verification for orders created outside checkout.
- Track invoices, refunds, payouts, and settlement statements.
Journey examples
Integrate Two into checkout and the settlement lifecycle
Two verifies the company and order, finances the sale, then exposes invoicing and reconciliation events.
1. Offer invoice payment at checkout
The process resolves the company, pre-assesses the order, then creates the corresponding Two order.
The Ormuz order remains the business reference; Two objects are correlated through plugin mappings.
2. Invoice and then reconcile settlement
After issuance, the invoice is executed with Two; reconciliation events then indicate payment allocation.
Payment of the Ormuz invoice must be derived from normalized allocation, not provider status alone.
Documentation
Browse the documentation
Review the configuration, nodes, events, objects, and access declared by this extension.
ConfigurationReview installation mode and Ormuz connector settings.NodesExplore actions, routers, and interactions available in processes.EventsReview Ormuz events, their originating provider event, and inputs exposed to processes.Objects and mappingsIdentify exposed provider objects and their reference schemas.Access and dataUnderstand the channels used and platform-object access requested by nodes.Resources and extensionsAccess associated documentation, support, plugins, and external marketplaces.