Payments and banking overview
Independent concepts
Section titled “Independent concepts”| Capability | What it represents | Boundary |
|---|---|---|
| Platform commercial billing | Emissary charges integrators for platform use. | Separate from a tenant’s provider configuration. |
| Tenant payment connectivity | An integrator configures providers to collect from its own customers. | Provider-specific external credentials and validation are required. |
| Payment ledger | Records payment operations and invoice payment projections. | A ledger record is not proof of external settlement. |
| Bank transfer instructions | References/instructions to pay outside Emissary. | Do not confirm money received without verified settlement evidence. |
| Bank reconciliation | Imports statement subsets and proposes explainable matches. | Bank-specific format/dialect validation is still needed. |
Do not conflate the two Stripe integrations
Platform commercial billing uses an integrator BillingAccount. Tenant Payment Connectivity is an environment-scoped provider configuration. One does not configure or authorize the other.
Maturity
Section titled “Maturity”| Connector | Jurisdiction | Status | Implemented capabilities | Validation notes |
|---|---|---|---|---|
| Stripe — Emissary commercial billing | global | In Development | platform subscription payment workflow, billing payment-method setup | In Development |
| Stripe — tenant payment connectivity | global | Under Evaluation | provider configuration boundary, payment operation model, callback verification foundation | Under Evaluation |
| Bank transfer instructions | generic | Ready | bank-transfer instructions, payment references | Ready |