Clarity Platform Architecture

Unlike bolt-on payment solutions that redirect users to external interfaces, Clarity embeds payment functionality directly within ERP workflows. Users in D365 or NetSuite process payments, manage wallets, and handle refunds without ever leaving their familiar environment. The platform's plugin architecture means payment capabilities are deeply integrated with invoicing, order management, and customer data — not just connected via API. See Embedded vs. Integrated Payments.

Every feature in Clarity is a modular plugin registered through the IPlugin interface. Client-specific customizations are isolated in the Client layer, which hooks into core pipelines without modifying them. This means core and plugin updates can be applied independently of client customizations, and new capabilities can be added or removed without affecting the rest of the system. See Plugin System and Pipeline Hooks.

Yes. Each client deployment uses a dedicated database instance, providing complete data isolation. Configuration, credentials, and connector settings are managed per-tenant. The platform supports deploying multiple isolated instances from the same codebase, with client-specific customizations applied through the plugin and pipeline hook system. See Deployment Model.

Clarity supports multiple embedded payment models: direct iframe embedding within ERP interfaces (D365, NetSuite), self-service Quick Pay links delivered via email/SMS for invoice payments, full eCommerce checkout flows, and back-office CSR payment processing. All models use client-side direct-to-provider tokenization, ensuring PCI compliance (SAQ-A eligible) regardless of the embedding context. See Embedded Payments and Quick Pay.