AerisPayments™

Mission Control for billing and collections — gateway events, subscriptions, and reconciliations backed by enterprise.payment_transactions and related tables.

AerisPayments™

Payment gateway selector

Same processor, different validation logic per vertical.

Mode: Network (Claim Submission)

Validation blocked

  • metadata.units: units must be provided for unit-based billing.
  • metadata.rate_per_unit: rate_per_unit must be provided for unit-based billing.
  • metadata.auth_reference: TriWest auth_reference is required.

Daily volume — last 7 days (demo)

Recent Payment Transactions

Selected columns from enterprise.payment_transactions

enterprise.payment_transactions

Org demo-pay-org-001
GatewayAmountCurrencyProcessed atStatusGateway txn id
stripe149.00USD2026-03-08 10:14succeededpi_3PcZ1zLxxa1c
stripe399.00USD2026-03-08 09:02succeededpi_3PcYt9Lx0n95
paynow75,000.00ZWL2026-03-07 16:44succeededPN-20260307-8842
stripe29.00USD2026-03-07 11:23failedpi_3PcXoRLx8b02
stripe999.00USD2026-03-06 19:31succeededpi_3PcWl3Lx7k11

Getting started · Setup guide

AerisPayments™

Follow these steps to configure your first records. Once completed, this wizard will be replaced by live data from Supabase.

  1. Configure gateway credentials (Stripe, Paynow) in core.api_clients or environment.
  2. Set up subscription_plans in core.subscription_plans and link them to products.
  3. Verify webhook endpoints and start capturing payment_transactions.

Get started

This button will eventually launch a guided form or deep-link into the first creation screen for this module (e.g. new Site, Patient, or Asset).