Least-necessary access
Use delegated authorization and the minimum provider permissions required for supported workflows wherever the provider allows it.
Commerce → UmiPort → Accounting
Automation built around control and traceability.
UmiPort handles financial integration data, so the platform is being designed with tenant isolation, encrypted secrets, scoped authorization, idempotent processing, auditability and recoverable sync workflows.
One-time connections Automated accounting flow Continuous reconciliation
Authorization boundaries ✓
Encrypted secrets ✓
Tenant isolation ✓
Idempotent posting ✓
Immutable source evidence ✓
Audit trail ✓
Security principles
Designed before scale.
These are architectural principles for the UmiPort product. Formal certifications will only be claimed after they are actually achieved.
Tenant boundaries
Keep each customer’s connection credentials, source events, rules and accounting destinations logically isolated.
Recoverable processing
Use durable queues, retries and transaction states so a temporary provider or local ERP outage does not silently lose financial events.
Financial control model
Every posting has a provenance.
UmiPort records where a transaction came from, how it was interpreted, which rule was applied and what the destination system confirmed.
Encrypted tokens and sensitive configuration
No plain-text marketplace passwords
Role-based permissions
Signed or verified callbacks where supported
Duplicate prevention / idempotency
Raw source event retention
Posting confirmation
Exception queue
Mapping change history
Operational logs and retries
Backups and recovery procedures
No public inbound Tally port requirement
UmiPort will publish a production security and data-processing policy before general availability. This page describes the intended V1 architecture and controls, not third-party certification claims.