A payment platform for merchants who'd rather sell.
Coming soon.
Eliopi will give your business a polished hosted checkout, KYB-managed onboarding, dispute tooling, and clean payouts — without the months of engineering most teams burn building it themselves. We're finalising the operating entity and our compliance review; the early-access waitlist is open.
What Eliopi will do at launch.
Four jobs, no theatrics. The scope below is what we are building so merchants can sign up and take a payment as soon as Stripe activates our Connect platform capability.
Stripe processing fees vary by country, card type, and payment method. Figures shown are indicative for a standard EU consumer card; see pricing for the full breakdown.
We are explicit about who we can onboard.
Eliopi enforces Stripe's restricted-businesses list at onboarding. The categories below are not exhaustive — see the full Acceptable Use Policy.
Onboarded Merchants we work with
- Direct-to-consumer e-commerce
- Digital products & downloads
- SaaS & subscription businesses
- Online courses & coaching (delivery-backed)
- Marketplaces in unrestricted verticals
- Professional services with deliverables
- Print-on-demand & physical goods (with shipping records)
Prohibited Categories we do not onboard
- Adult content, escort services, dating with sexual exchange
- Gambling, lotteries, skill-based gaming with prizes
- Firearms, ammunition, weapons, military-grade hardware
- Cannabis, CBD above legal THC limits, drug paraphernalia
- MLM, pyramid schemes, get-rich-quick, "passive income" pitches
- Money services: ATMs, check cashing, P2P money transfer
- Debt collection, credit repair, debt consolidation
- Counterfeit goods, IP infringement, unlicensed music/film
- Cryptocurrency exchanges, ICOs, NFT secondary marketplaces
- Pseudo-medicine, unsupported supplement claims, predatory medical
- Telemarketing, door-to-door sales, negative-option marketing
What Eliopi sees. What Eliopi never stores.
Eliopi operates under PCI SAQ-A — the lowest-scope merchant category. The card form is rendered by Stripe Elements directly to Stripe's tokenisation endpoint; PAN data does not transit through Eliopi infrastructure.
Tokenised metadata for routing & reporting.
- payment_method (token)stored on Stripe
- amount & currencyretained
- card brand · last4 · BINretained
- customer email (merchant-supplied)retained
- order metadata (merchant-supplied)retained
- 3DS authentication resultretained
Card data and authentication secrets stay with Stripe.
- full PANnever received
- CVV / CVCnever received
- track 1 / track 2 datanever received
- cardholder authentication secretshandled by Stripe
- merchant payout bank credentialshandled by Stripe
→ Full security & compliance posture: security.html
Honest answers to the questions a reviewer asks.
Are you a payment processor or a financial institution?
No. Stripe is the licensed payment processor; Eliopi is a platform built on Stripe Connect that operates merchant onboarding, hosted checkout, dispute workflows, and platform-fee collection. Eliopi is not a bank, a money transmitter, an acquirer, or an MSB. We are a software platform that earns an application_fee_amount per transaction.
Does Eliopi store cardholder data (PAN, CVV)?
No. The card form is rendered by Stripe Elements directly into Stripe's tokenisation endpoint. Our PCI scope is SAQ-A: no PAN, no CVV, no full card data ever transits or is stored on our infrastructure. We retain Stripe-issued payment-method tokens, brand, last4, and BIN — nothing more.
Who is the merchant of record? Whose name appears on the cardholder's statement?
The connected merchant account is the merchant of record. Charges are created with on_behalf_of set to the connected account, so the merchant's statement descriptor, business address, settlement currency, and regulatory acquirer all reflect the merchant — not Eliopi.
How are disputes and chargebacks handled?
Disputes flow through Stripe and surface in the Eliopi dashboard. Because we use destination charges, the dispute amount and dispute fee debit the platform balance; we recoup from the connected merchant via a transfer reversal, per the Stripe Connect dispute model. Merchants submit evidence directly through the Eliopi dashboard within Stripe's response window. Full detail: refund & dispute policy.
What categories of business do you NOT onboard?
We mirror Stripe's restricted-businesses list and add platform-specific exclusions. Adult content, gambling, firearms, cannabis above legal THC limits, MLM, debt collection, money services, and pseudo-medical products are all outside our scope. Full list and restricted (case-by-case) categories: Acceptable Use Policy.
How fast will a merchant be onboarded once Eliopi launches?
Once Eliopi is approved as a Stripe Connect platform, a merchant who has a US LLC, EIN, beneficial-owner identity documents, and a US bank account ready will be able to complete Stripe Identity verification in a single sitting; charges_enabled typically activates within minutes to hours. Documents that need manual review (e.g. older passports, address mismatches) can take 1–2 business days. We do not promise approval — Stripe Risk and Eliopi's onboarding team will reserve the right to decline merchants outside our acceptable-use scope.
What stage is Eliopi at today?
Pre-launch. The operating entity is currently Eliopi LLC, Utah; we are transitioning to a Delaware entity via Stripe Atlas, after which our Stripe Connect platform application will be submitted to Stripe Risk for review. The site you are reading describes the planned product, the policy framework, and our compliance posture — not a live platform with onboarded merchants. Early-access waitlist signups are stored and contacted in order once Stripe activates our platform capability.
Get a head start.
We're forming Eliopi through Stripe Atlas and applying for Connect platform approval. Join the early-access waitlist and we'll reach out, in order, once the platform is live — typical wait is 4–8 weeks.