Aeion Finance + Stripe
Stripe webhooks land on Aeion's shared payment-provider layer — signature-verified, idempotent, no polling. Today that pipeline automatically posts refund reversals as double-entry GL journal entries; revenue-recognition posting on payment receipt, subscription deferred-revenue waterfalls, and payout-to-bank matching are being built out on top of the same event stream. No Zapier glue layer in between.
What Connects
`
Setup
Three steps:
Payment Flow — End-to-End
`
Subscription Revenue Recognition (ASC 606)
Aeion Finance ships a deferred_revenue ledger structure built for exactly this waterfall. Automatically opening the schedule the moment a Stripe subscription is created is the target flow described below — wiring that trigger end-to-end is in progress, so treat this as the intended shape rather than shipped default behavior today.
Refund + Dispute Handling
```typescript
FAQ
Stripe Tax handles sales/use tax computation at checkout — useful if you sell digital goods to 45+ US states. Aeion's native tax engine integrates Stripe Tax as a source. Stripe Sigma is for ad-hoc Stripe-data SQL — Aeion's BI module reads finance data directly so Sigma is mostly redundant.
Not integrated today. If you need either, talk to your account team about roadmap timing before assuming the flow above covers it.
Aeion's ledger stores temporal FX rates and posts journals in your base currency with the foreign amount preserved; the webhook payload's presentment amount is available for that mapping.
Stripe retries failed deliveries for up to 3 days. Aeion's webhook handler is idempotent (Stripe event-id deduplication), so a retried delivery is safely ignored rather than double-processed.