Integrations
Connect usage, tax, hosted payments and accounting with preserved outcome evidence.
- Billing inputs
- Usage producersin and out
- Customer provisioningin and out
- Tax servicein and out
- Collection and accounting
- Hosted payment providerin and out
- Email providerin and out
- Accountingin and out
- Agents
- Your agentWorks within the permissions you assign
Billing inputs
- Usage producers. Verify source identity and retain event keys, timestamps and payload digests. Repeated events do not increase quantities.
- Customer provisioning. Reconcile accepted subscription terms and customer identity; service activation is separate from a payment result.
- Tax service. Freeze the configured tax result and effective treatment with each calculation. Missing evidence keeps the invoice candidate unresolved.
Collection and accounting
- Hosted payment provider. Retain protected tokens, accepted mandates and original instruction identities. Apply only verified outcomes; reconcile pending or unknown requests before retry.
- Email provider. Preserve notification identity and delivery outcome separately from customer viewing or payment.
- Accounting. Send issued invoice, credit and reconciled receipt identities. Ledger posting and revenue recognition remain owned by the configured accounting system.
How connections are governed
service accounts, audit, pausingUse least-privilege provider-account credentials and verified incoming events. Keep connections disabled until configured and reconciled. Unknown outcomes preserve the existing instruction and any reserved amount. Neither a provider request nor a generated document establishes settlement or ledger posting.
The API is one more client of the same interface. Use Proto with Subscription Billing →