20 Payment Provider Adapters, One API, Zero Markup
Every payment provider adapter Aeion ships today. Configure per-tenant in the admin UI; switch providers per-order without code changes. The 20 adapters cover ~95% of the global commerce stack — major card processors, BNPL, regional alternatives, crypto, and manual (for cash / check / wire).
Coverage by Category
The full adapter inventory, by category.
Major Card Processors — Detail
| Provider | Slug | Real-world fit | Region |
BNPL (Buy Now Pay Later) — Detail
BNPL adoption hit ~10% of US online transactions in 2025; growing in EU + AU. Aeion ships all 4 major Western BNPL providers.
Regional Alternatives — Detail
Markets outside the US-EU axis often require local payment methods.
POS-Focused + Crypto + Manual
POS-focused (2):
Configuration — Real Env-Vars + DB Storage
Payment provider credentials live in your own database, encrypted at rest. Configure via:
Common Per-Provider Gotchas
- Stripe — Radar's machine-learning model improves over time; new merchants see more false positives in the first 90 days. Aeion's own fraud detection runs pre-Stripe to reduce that noise.
FAQ
Yes — Aeion supports adding a custom payment provider through the same integration pattern the 20 built-in adapters use. Most missing providers (regional players) are quick to add; talk to your account team about enterprise custom-provider onboarding.
The customer picks at checkout (the storefront shows enabled providers as buttons). Per-store config gates which providers are even shown. Per-product config can override (e.g., subscriptions always use Stripe regardless of store default).
Not currently — one order = one payment provider. For split-tender (gift card + credit card), gift card balance is deducted first; remaining balance goes to the chosen card provider.
Coinbase Commerce handles fiat conversion at payment confirmation. You're paid in your configured fiat (USD, EUR, etc.); customer pays in crypto. Aeion doesn't expose merchants to crypto-volatility risk.
No — all providers use client-side tokenization (Stripe.js, PayPal SDK, etc.). Aeion never touches card numbers regardless of how many providers you enable. SAQ-A scope holds.
Each gateway charges its own processing fee (typically 2.5%-3.5% for cards; 4-6% for BNPL on the merchant side). Aeion takes 0% — fees go to the gateway, never to Aeion.
Stripe and PayPal are the most mature for recurring billing. Gateway-specific subscription objects map cleanly to Aeion's subscription records regardless of which you choose.