Pay
Pay unifies offline acceptance, terminal fleet behavior, and settlement controls across open and closed loop flows.
Unified acceptance across kiosk, POS, and mobile
Capabilities
- Offline mode and safe replay for event network volatility.
- Terminal fleet orchestration and observability.
- Closed-loop and open-loop support under one domain model.
- Settlement rules with deterministic audit trails.
How It Works
- 1Set payment acceptance and settlement policies.
- 2Run transactions through one orchestration path.
- 3Publish reconciled outcomes to finance and ops views.
Module Features
Everything you need for a better event.
1
Offline Mode
Capture and replay with strict idempotency controls.
2
Terminal Fleet
Provisioning, health checks, and replacement operations.
3
Closed vs Open Loop
Run both models without splitting operator workflows.
4
Settlement Rules
Policy-based splits and payout references per transaction.
1
Offline Mode
Capture and replay with strict idempotency controls.
3
Closed vs Open Loop
Run both models without splitting operator workflows.
2
Terminal Fleet
Provisioning, health checks, and replacement operations.
4
Settlement Rules
Policy-based splits and payout references per transaction.
Proof
Finance and operations reviewed the same payment truth in real time.
"The payment stack stopped being a patchwork and became a system."
What This Means For
- Campaigns, notifications, and family-wallet offers run from the same platform.
- Each module maps directly to measurable visitor journey steps.