platform-fit 2026-04-18 12 min read the orchestration desk

Pay.com, Checkout.com, Adyen: which fits a 20-brand portfolio

3-minute scan
  • Adyen wins on enterprise scale ($5M+/year per portfolio); Checkout.com wins on global card mix; Pay.com wins on speed-to-launch and high-risk vertical breadth.
  • All three require real engineering — none of them are "Stripe-easy." Budget 80–250 hours of integration time even on managed projects.
  • For 20-brand portfolios under $50M total volume, none of these is necessarily the right answer — a parent merchant account with descriptor-level branding usually wins on cost and operational simplicity.
On this page

    The "we're too big for Stripe but too small for Adyen" zone is where most multi-brand operators live. Pay.com, Checkout.com, and Adyen are the three names that come up most often in that conversation. Each one is a different bet on what your portfolio looks like in 24 months. This is the honest comparison — written by people who've integrated all three.

    What each platform actually is

    Adyen

    Dutch enterprise PSP, public, ~$300B annual processing volume, full-stack acquirer in major markets. Direct connections to Visa, Mastercard, ~150 local payment methods. Single API across regions. Sub-merchant model via "MarketPay" (their Stripe Connect equivalent) for marketplaces, or single-account with descriptor-level sub-branding for portfolios.

    Real customer profile: Spotify, Microsoft, McDonald's, eBay. Floor of $5M/year is informally enforced — they'll take smaller accounts but the integration team won't respond fast.

    Checkout.com

    UK-headquartered global PSP, private, processes ~$200B/year. Strong in EMEA, growing in U.S. Best-in-class for global card processing — they have direct issuer connections across 150 countries with intelligent routing for higher auth rates. Sub-merchant via "Sub-entity" structure or full multi-account.

    Real customer profile: Wise, Klarna, GE, Siemens. Floor more flexible than Adyen but engineering integration cost is meaningful.

    Pay.com

    Newer entrant (2021), positioning as the "high-risk friendly enterprise PSP." Acquirer relationships with multiple banks across regulated verticals (CBD, supplements, nootropics, peptides via case-by-case underwriting). Sub-merchant model with portfolio-level reporting.

    Real customer profile: mid-market high-risk operators ($1M–$50M/year), CBD chains, supplement portfolios, regulated verticals. Floor lower than Adyen/Checkout — they'll onboard at $500k/year.

    The 8 dimensions for a 20-brand portfolio

    1. Volume floor and pricing tier

    • Adyen: Effective minimum $5M/year for serious attention. Below that, on Adyen Dynamic Pricing (~2.95% + €0.11). Above $25M, custom interchange-plus with 15–25 bps margin.
    • Checkout.com: Effective minimum $2M/year. Custom pricing kicks in at $5M. Floor margin around 25–35 bps over interchange on standard verticals.
    • Pay.com: $500k/year acceptable. Margin 40–80 bps over interchange depending on vertical. High-risk surcharge can push to 150–300 bps.

    2. Vertical scope

    • Adyen: low-risk only. Will not touch peptides, kratom, SARMs, nootropics. CBD case-by-case (rare yes).
    • Checkout.com: low-risk + some moderate-risk (firearms accessories, tobacco). Same restrictions as Adyen on regulated supplements.
    • Pay.com: broadest scope. Will quote on most regulated supplement verticals, CBD, kratom (case-by-case). Not cannabis flower, not adult, not unregistered firearms.

    3. Sub-account architecture

    • Adyen: single merchant account with up to 1,000 "sub-merchants" each with own descriptor / payout / reconciliation. True portfolio model. Requires API-level setup.
    • Checkout.com: "Sub-entity" model with similar per-brand isolation but more manual setup per brand. Better suited to 5–15 brands than to 50.
    • Pay.com: per-brand merchant accounts grouped under a portfolio dashboard. Closer to "Stripe Standard with consolidated reporting" than to true sub-merchant architecture.

    4. Integration effort

    • Adyen: 120–250 engineer-hours for a non-trivial multi-brand integration. Their docs are excellent; the surface area is large. Expect 8–16 weeks calendar.
    • Checkout.com: 80–180 engineer-hours. Simpler API surface, though enterprise features add complexity. 6–12 weeks calendar.
    • Pay.com: 40–80 engineer-hours for portfolio integration. Their setup team does heavy lifting on white-glove projects.

    5. Authorization rate

    • Adyen: consistently 1–3 percentage points higher than Stripe on global card mix due to direct issuer relationships and intelligent routing. The single biggest argument for Adyen at scale.
    • Checkout.com: similar to Adyen on EMEA, slightly behind on U.S. domestic.
    • Pay.com: similar to Stripe on U.S. domestic, depends on acquirer routing for international.

    6. Freeze risk and portfolio concentration

    • Adyen: low single-account freeze risk (they're an acquirer, not a payfac). Per-sub-merchant risk reviewed independently. Termination is rare and process-driven.
    • Checkout.com: similar profile to Adyen.
    • Pay.com: medium risk — portfolio concentration in high-risk verticals can trigger reserve increases or onboarding pauses for new brands. Less predictable than Adyen.

    7. Reporting and reconciliation

    • Adyen: single reconciliation file per payout, sub-merchant-tagged. Best-in-class.
    • Checkout.com: good reporting, slightly less polished sub-entity tagging.
    • Pay.com: per-brand reports rolled up at portfolio level. Functional, not exceptional.

    8. Cost of leaving

    • Adyen: high. Integration is platform-specific; migration off is 6+ months.
    • Checkout.com: moderate to high.
    • Pay.com: low to moderate. Per-brand merchant accounts are easier to migrate one at a time.

    The decision matrix

    Pick Adyen if: total portfolio volume is $10M+/year, all brands are low-risk verticals, you have engineering capacity for a 16-week integration, and global card mix matters (you're doing >30% non-USD or international cards). Authorization rate gain alone usually justifies the spend at scale.

    Pick Checkout.com if: $5M+/year, primarily EMEA exposure, you want best-in-class international auth rate without Adyen's integration weight. Strong fit for SaaS or subscription operators with global subscribers.

    Pick Pay.com if: $1M–$10M/year, portfolio includes regulated verticals (supplements, CBD, kratom), and you need a single portfolio dashboard without rebuilding around an enterprise API. Best fit for ops teams that want managed onboarding rather than engineer-led integration.

    Pick none of them if: you're running 10–20 brands at $50k–$200k/month each in the same vertical, with descriptor-level differentiation. The right architecture is one parent merchant account with sub-brand descriptors at a peptide-friendly or vertical-specific acquirer. That's the multiflow case — see how 20 brands run on one merchant account and orchestration vs aggregation.

    What the brochures don't say

    Adyen will quote you, then under-deliver service below $10M

    Their integration team triages by account size. Below $10M annual volume, expect 2–4 week response cycles on integration questions. This kills momentum on a portfolio rollout where every brand needs setup attention.

    Checkout.com's sub-entity onboarding requires per-brand KYB

    Each sub-entity goes through full KYB including bank verification. For a 20-brand portfolio that's 20 KYB cycles — same operational pain as opening 20 Stripe accounts, just with a better dashboard at the end.

    Pay.com's "high-risk friendly" depends on the acquirer

    Pay.com routes through multiple acquirer banks. Approval for your peptide brand depends on which acquirer underwriting handles the case. Two brands in the same vertical can get different answers a month apart. Less predictable than working directly with a peptide-focused ISO.

    The honest answer for a 20-brand portfolio

    If your portfolio is $30M+/year and verticals are clean: Adyen. The auth-rate gain pays for the integration in 12 months.

    If your portfolio is $5M+/year and global is a real factor: Checkout.com.

    If your portfolio is mixed-risk regulated verticals at $1M–$10M/year: Pay.com is faster than direct ISO sourcing and gets you a single dashboard.

    Outside those bands, a parent merchant account model usually beats all three on cost, operational simplicity, and time-to-launch. Read multiflow vs Stripe for the architecture comparison, or check our pricing for the spread vs Adyen-class rates.

    Found this useful? Share it X LinkedIn Reddit HN Email

    FAQ

    Can I run Adyen and Pay.com simultaneously?
    Yes — multi-PSP routing at the brand or even transaction level is common. Adyen for U.S. domestic + Pay.com for high-risk supplements is a real architecture. Adds engineering complexity but can be the right answer when one platform won't cover the full vertical mix.
    Does Adyen offer instant settlement?
    No standard instant settlement product. Adyen runs T+2 or T+3 by default with custom faster-payout possible at high volume. If cash-velocity is critical, consider Pay.com (next-day standard) or stay on Stripe/Square for the cash-velocity-sensitive brand.
    How does Checkout.com handle 3DS for global cards?
    Excellent — they auto-route 3DS challenges through the right authentication path per issuer for higher pass rates. This is one of their genuine differentiators vs Stripe for international ecommerce.
    Is Pay.com a payfac or an acquirer?
    Pay.com is a registered payfac with relationships to multiple sponsor acquirer banks. They underwrite per-brand and route to the appropriate acquirer. This explains why high-risk vertical approval is acquirer-dependent.
    What about Stripe Enterprise vs Adyen at the same scale?
    Stripe Enterprise (the negotiated-rate variant) closes most of the rate gap with Adyen at $20M+. Adyen still wins on auth rate for global card mix; Stripe wins on developer experience and ecosystem. The decision becomes "do you want best-in-class auth rate or best-in-class extensibility."

    Running multiple brands?
    multiflow was built for this.

    The Operator Briefing

    Twice-monthly. No fluff.

    Processor shutdowns, reserve-hold playbooks, reconciliation lessons, and the merchant-account decisions that save operators six-figure years. Delivered to your inbox — never spam.

    No spam. Unsubscribe in one click.

    We use essential cookies · Privacy