Adyen Issuing

Name: Adyen Issuing
Brand: Adyen
Rating: 3.1 (464 reviews)

Leader

Meet the financial technology platform helping the world’s leading businesses achieve their ambitions faster.

Est 2006|Valuation $33.8B|Raised $267.1M|41 Ref Customers

LinkedIn 408K|Website|Web traffic 56.8M|FTEs 5,020|HQ Amsterdam, North Holland, NL

MarketsProcure-to-Pay

Platform CoversB2B Payments Corporate Card Management

Published Oct 23, 2026

01Common complaints

- Organizations requiring issuing coverage beyond the US, UK, and Europe today should consider alternative vendors with broader geographic availability. - Organizations that require a published rate card for early-stage modeling and rapid procurement may prefer vendors that publish unit pricing. - Small businesses with low transaction volumes and simple card issuing needs may find the vendor’s sales-led, enterprise-oriented onboarding disproportionate to their needs. - Organizations preferring a specialist issuing-only provider and willing to operate a multi-vendor stack may select specialist platforms instead. - Organizations that require consolidated instance management across many brands and legal entities should validate account structure options and operational overhead before selecting this product. - Availability constraint - Issuing is available for businesses in the US, UK, and Europe; organizations outside these regions should confirm availability timelines. - Sales-led onboarding and environment differences - Onboarding is sales-led and configurations in test do not automatically replicate to live, which introduces additional go-live work and configuration management considerations. - Pricing clarity limitations - While the vendor describes component-level pricing concepts, concrete issuer fees and revenue splits typically require sales engagement and program modeling. - Review data limitations - Most third-party reviews discuss the vendor as a payments processor rather than the Issuing product specifically. Buyers should request direct issuing customer references. - Roadmap items - No specific Issuing roadmap dates were identified in this research run; request roadmap and feature timelines during procurement.

Deal disqualifiers (poor fit)

Need for issuing coverage outside the US, UK, and Europe in the near term.
Requirement for instant, self-serve activation with fully public unit pricing.
Limited internal compliance or operations capacity for disputes, fraud operations, and program monitoring.

02Why they buy

- Integrated acquiring and issuing funds flow - The vendor positions issuing as integrated with acquiring and account/balance capabilities to enable funds movement between incoming payments and issued cards within the same platform. The practical value depends on whether acquiring is also adopted with the vendor. - Program controls and authorization strategy - Documentation describes configurable transaction rules and authorization workflows that support spend controls and custom verifications layered on top of internal checks. - Interchange-- pricing model - The vendor describes a pricing model that separates interchange revenue, scheme fees, and issuer fees to clarify component-level economics; program-specific negotiation and modeling are still required to estimate net economics. - Areas where competitors have advantages (balanced) - Competitors may provide clearer public unit pricing, specialist issuing features (e.g., JIT funding), or alternative integration models depending on customer priorities.

03Field reports

Customer Testimonials

Important limitation: Most third-party review platforms cover the vendor overall (payments/acquiring) rather than the Issuing product specifically. Where possible, this section highlights comments that reference issuing or embedded finance. - Review platforms (vendor overall) - TrustRadius shows a high aggregate score with multiple reviews; reviewers cite integration breadth and UI as strengths and note occasional concerns about response times. - G2 profile includes mixed reviews with a range of ratings; some reviewers reference the vendor’s broader set of financial products, including issuing, though most reviews focus on payments. - A vendor review profile exists on Gartner Peer Insights, but issuing-specific quotes were not extracted in this research run. - Community / social sentiment (anecdotal) - Pricing opacity for issuing: community discussions ask for detailed issuer fee amounts and interchange revenue split details, indicating a lack of publicly available detailed figures. - Operational complexity / multi-entity management: community posts describe challenges with multiple vendor instances, integrations, and dashboards when launching multiple brands. - Example direct quotes (representative excerpts) - Positive (platform breadth): A review excerpt referenced the vendor’s suite of financial products and noted that including issuing can simplify internal support and merchant experience. - Concerns (pricing transparency): Community posts have asked for concrete details about issuer fees and interchange splits for the issuing program. - Concerns (operational overhead): Community posts describe repeated administrative work when launching new brands or instances with separate vendor contracts and dashboards. - Why customers chose this product over alternatives (inferred) - Organizations already using the vendor for acquiring may prefer Issuing to consolidate funds flow, reporting, and vendor relationships. - Enterprise buyers cite broad payments coverage and analytics on review platforms, which can support confidence in expanding into issuing. - Why some customers left for competitors (churn reasons) - Issuing-specific churn reasons were not clearly available in accessible sources. General switching reasons in payments communities commonly include support responsiveness, contract complexity, and risk appetite/KYB decisions. - Deal-breakers and reasons organizations did not purchase - Geographic availability: Issuing availability is limited to certain regions (e.g., North America and parts of Europe), which constrains global launches. - Need for a self-serve model and published unit pricing: some organizations prefer vendors that publish per-card/unit pricing for faster procurement and modeling.

Vendor-announced customer examples

Vendor press releases and announcements describe use cases such as marketplaces using virtual cards for supplier payments and online travel agencies issuing virtual cards to suppliers. These vendor communications provide examples of deployment scenarios but do not include independently verified ROI metrics.

Metrics and methodology gaps

No independently verified ROI or cost-savings numbers for Adyen Issuing were found in this research run.
Buyers should request program economics models, fraud and dispute rate benchmarks, and authorization/approval rate data during procurement.

Mixed results / failed projects

Public examples of failed issuing rollouts specific to this vendor were not identified. Common causes for issuing program failures in the industry include compliance readiness, insufficient volume economics, and underestimating disputes and operational needs.

04Best fit

Company sizes (practical guidance)

Most suitable for mid-market to enterprise organizations, and platforms/marketplaces with meaningful transaction volume and a need for branded physical or virtual cards.
Heuristic ranges (buyer-side guidance, not vendor stated):
- Hundreds to many thousands of employees
- Tens of millions to multiple billions in revenue, or platforms with substantial gross payment volume and many sub-merchants

Industries and verticals where adoption is strongest

Platforms and marketplaces offering embedded finance to SMB users.
Travel and supplier payments (virtual cards for supplier settlement).
Expense management and corporate spend programs.

Roles and personas

Decision makers: VP/Head of Payments, CFO/Treasurer, Head of Product (embedded finance), Head of Risk/Compliance.
End users: finance operations (reconciliation, reporting), developers/platform engineering (issuing + balances APIs), customer support/disputes teams.

Pain points the product addresses

Issuing physical and virtual cards with programmatic controls and consolidated reporting.
Reducing payout delays and enabling funds flow within a single vendor ecosystem when acquiring and issuing are both used.

Qualification criteria (good fit)

Organizations that already use or plan to use the vendor for acquiring and want a unified stack for funds flow and reporting.
Ability to engage in a sales-led implementation and compliance program setup.
Geographic footprint aligned with Issuing availability (US, UK, Europe).

05The pitch

What the product does (core value proposition in objective terms)

Adyen Issuing is an API-first card issuing product for creating and managing physical and virtual payment cards, including mobile wallet provisioning, and for controlling card usage through configurable spend controls and authorization logic.
The product is integrated with Adyen’s broader acquiring and account/balance capabilities to enable funds flow between incoming payments and outgoing disbursements with fewer intermediary steps.

Target market and market positioning

- The vendor emphasizes enterprise use cases and platform business models such as embedded finance, supplier payments/online travel agencies (OTAs), and expense management. - Adyen documentation describes two common integration models: - Enterprise issuing with acquiring (the organization acquires via Adyen and uses those funds to fund issued cards). - Embedded issuing (a platform/marketplace provides issuing to its users, who then issue cards to employees or departments).

Get a comprehensive analysis of Adyen Issuing including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →