Aeion Billing + Stripe
Stripe is the dominant payment infrastructure of 2026 — credit cards, ACH, SEPA, bank transfers, Apple Pay, Google Pay, and 35+ payment methods across 47 countries. Aeion Billing wraps Stripe's payment surface with the missing layers — subscription lifecycle, license enforcement, dunning, multi-tenant routing, per-tenant Stripe accounts, webhook reconciliation, 3D Secure / SCA compliance. Stripe handles the payment rails. Aeion handles the billing logic.
What the Integration Provides
Per-tenant Stripe configuration. Each tenant gets its own restricted Stripe API key, its own webhook endpoint, its own currency configuration, and control over which payment methods are enabled.
Setup Walkthrough
- Create a Stripe account at stripe.com/register, if you don't already have one.
Webhook Reconciliation
Every Stripe webhook is verified against its signature before Aeion processes it. Once verified, the event is routed to the handler for its specific type — Aeion recognizes and acts on more than 20 Stripe event types, including:
3D Secure / SCA Compliance
EU (PSD2). Payments over roughly €30 typically require Strong Customer Authentication, meaning the customer completes a 3DS challenge. Exemptions apply for low-value payments (under €30), recurring charges after the first authenticated payment, whitelisted merchants, and corporate cards.
Multi-Currency Settlement
Each tenant configures a default currency and a list of supported currencies, and chooses how a customer's currency is detected — by IP geolocation, billing address, or manual selection.
FAQ
We recommend a separate Stripe account per tenant, so card data and settlement stay fully isolated between tenants.
Not today — there's no connected-account, application-fee split, or 1099-K generation logic in Aeion's Stripe integration. Each tenant's own Stripe account is used for direct payments only.
Stripe's standard rates apply — 2.9% + $0.30 per US transaction, 3.4% + $0.30 for international cards, with some variation by payment method. Aeion doesn't add any markup on top.
Stripe routes each transaction through the appropriate regional acquirer — for example, a PSD2-compliant EU acquirer for European transactions.
Every Aeion webhook handler is idempotent, so Stripe's automatic retries (up to 72 hours) are always safe to replay.
With Stripe's tokenization, Aeion never touches raw card data, which keeps most tenants in the simplest PCI scope (SAQ-A). A custom card-entry form would move you to SAQ-D-Merchant instead.
No — card data lives with Stripe as a tokenized payment method; Aeion only stores the token reference.
Yes — each tenant can toggle test mode, use Stripe's test API keys, and run through the flow with Stripe's published test cards (like `4242 4242 4242 4242`).
Yes — each tenant can configure their own Stripe Radar rules and fraud scoring per payment.
Aeion runs a dispute workflow with evidence collection, then submits through the Stripe Dashboard.
Refunds — full or partial — are issued through the Aeion API and hand off to accounting automatically.
Klarna and Afterpay (buy-now-pay-later), iDEAL, Bancontact, WeChat Pay, and Alipay — all handled through Stripe and wired into Aeion.