top of page
Financial Services
FinTech
Payment Processing
Marqeta
Won by giving internet-native companies API control over card issuing, authorization, and funding, replacing fragmented bank-network-processor relationships despite Visa, Mastercard, legacy processors, and issuing banks.
1
MODEL
BUSINESS MODEL
Embedded Software
- Founded by Jason Gardner in 2009–10, Marqeta ultimately built an open-API issuer-processor platform rather than selling cards directly. [32][34][33] - The platform bundles issuing banks, card networks, card fulfillment, compliance, authorization, tokenization, fraud tools, and program management into one integration layer. [35][36][37] - Customers configure card rules, spending controls, funding, and credentials in real time; JIT Funding moves customer funds only when a transaction is authorized. [38][35][36] - Revenue comes primarily from interchange on processed transactions, shared with customers through revenue-share payments, plus processing and value-added services. [39][40] - Marqeta expanded from debit and prepaid into credit in 2021 and formalized credit-program tools in 2023. [41][42]
1. Identify a regulated or infrastructure-heavy process where customers want product control but cannot economically manage every intermediary. 2. Build an abstraction layer that packages compliance, counterparties, and execution into APIs while exposing the decisions customers care about. 3. Make the first wedge a use case where real-time control creates obvious value, not merely lower cost. 4. Charge on the underlying transaction or value flow so revenue scales with customer success. 5. Add managed services, new asset classes, and geographies only after the core platform proves reliability and regulatory depth. Avoid selling APIs without owning or deeply controlling the regulated execution chain; integration convenience alone is not a durable business. [35][36][37]
DISTRIBUTION MODEL
Marqeta initially pursued prepaid loyalty cards, then pivoted through multiple models before launching open APIs and Just-in-Time Funding in 2014. It prioritized configurable card issuing and real-time authorization over becoming a consumer card issuer; this let DoorDash constrain Dasher purchases to eligible restaurants and amounts, while Square launched Cash App Card rapidly. [32][33]
HOW THEY BUILT IT
HOW TO ARCHITECT IT
Enterprise Sales, Developer/API-Led, Partnerships, Product Integrations
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- Marqeta targeted fintechs and technology-enabled service providers—DoorDash, Instacart, Square, Affirm, Klarna, Brex, and Uber—rather than selling first to banks. [32][43][33] - Open REST APIs, developer documentation, and sandbox-style program configuration made engineers the entry point. [35][36] - Issuing-bank, card-network, and fulfillment partnerships removed the customer’s need to build those relationships independently. [35][37] - Enterprise sales and solution teams supported high-value, regulated launches; DoorDash cited launch-to-first-transaction in under 70 days. [44]
What worked: selling programmable infrastructure to builders created a technical buying motion and made the platform part of the customer’s product architecture. Trap if copied blindly: developer-led distribution fails when the buyer is a regulated institution with procurement, compliance, and risk requirements; pair API access with enterprise implementation and regulatory credibility. [35][44][37]
| PATTERNS OF THIS MODEL
PATTERNS IN EMBEDDED FINANCIAL INFRASTRUCTURE: 1. ABSTRACTION OF REGULATED COUNTERPARTIES CREATES LEVERAGE. The vendor aggregates banks, networks, compliance, and fulfillment, converting a multi-party project into one integration. [35][37] 2. TRANSACTION-LINKED REVENUE ALIGNS WITH CUSTOMER SCALE. Marqeta’s 2025 TPV rose 31% to $382.5 billion while net revenue rose 23% to $624.9 million. [39][40] 3. CONFIGURABILITY BECOMES THE PRODUCT. Real-time rules, funding models, and authorization decisions let customers differentiate their end-user experience. [38][36] THE WEAKNESS: interchange and network economics are externally controlled; Marqeta’s costs of revenue rose 21% in 2025, largely from higher card-network and issuing-bank fees. [40]
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — PROGRAMMABLE TREASURY AND WORKING-CAPITAL RAILS. The next layer is not only issuing cards but controlling when funds move across cards, accounts, stablecoins, and credit lines. Marqeta’s 2026 stablecoin-backed card work signals this direction. [45] GOLDMINE 2 — VERTICAL EMBEDDED FINANCE WITH UNDERWRITING CONTEXT. Platforms in logistics, healthcare, construction, and marketplaces can use operational data to issue purpose-constrained credentials and financing. GOLDMINE 3 — AI-DRIVEN AUTHORIZATION AND FRAUD ORCHESTRATION. Real-time transaction data can support dynamic limits, fraud scoring, and spend policy without rebuilding the card stack. THE PIT — INTERCHANGE-DEPENDENT GROWTH. Revenue tied to interchange is vulnerable to regulation, network fee changes, and customer renegotiation. THE SECOND PIT — API-ONLY POSITIONING. A thin API layer can be displaced by banks, networks, or large processors that bundle issuing, processing, and risk. MOVE WITH CAUTION — do not enter card infrastructure without committed bank sponsors, network certification, fraud controls, and capital-risk management; regulatory complexity is the product, not an afterthought. [45][35][37][40]
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
Marqeta faced legacy issuer-processors such as Fiserv, TSYS, and FIS, plus card networks and banks. Rather than competing for bank core processing, it targeted technology companies that wanted API control and speed; Square built Cash App Card with Marqeta in about six weeks, while DoorDash used configurable cards for Dasher spending. [43][33]
MARKET TYPE
Consolidated Market
ENTRY STRATEGY
Greenfield Entry
WHY THEY WON
Card issuing and processing is consolidated around banks, Visa/Mastercard, and legacy processors. Marqeta exploited a blind spot: incumbents optimized for banks and stable enterprise programs, while emerging internet companies needed developer control, rapid iteration, and real-time spend rules. Its open API and bundled infrastructure changed the buying criterion from processor reliability alone to speed, configurability, and product control. The transferable lesson is that a consolidated market can be attacked by serving a new buyer whose requirements the incumbent’s architecture was not designed to meet. [35][32][33]
EXECUTION
Marqeta did not attack the bank-processor core directly; it flanked legacy players by serving fintechs, marketplaces, and consumer apps that wanted to embed card programs. After earlier loyalty-card models failed to scale, it launched open APIs and JIT Funding in 2014, packaging bank, network, processor, and fulfillment relationships into one platform. [32][34][33] The critical bet was that developers and product teams would value authorization control enough to adopt a new infrastructure provider. This required bank sponsorship, network certification, and reliable processing; it would fail where the target customer already had deep processor relationships or where regulatory sponsorship could not be secured. [35][37][33]
FOOTHOLD STRATEGY
Lighthouse Customer Strategy
Marqeta’s foothold came from marquee technology customers: DoorDash used constrained Dasher cards, Instacart powered shopper purchasing, and Square used Marqeta for Cash App Card and business debit. These customers proved that the platform could support high-volume, real-world payment programs and became references for later fintechs and enterprises. [32][43][33]
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: Marqeta’s growth campaigns turned difficult customer implementations into reusable proof of regulated infrastructure capability. KEY LEARNING: in infrastructure markets, a demanding lighthouse customer is more persuasive than a broad feature announcement because it validates reliability, compliance, and scale. HOW TO USE: pursue one technically demanding customer whose requirements force you to build durable platform capability, then convert the implementation into a reference architecture for the next segment. [44][32][33]
KEY LEARNING
THE STANDARD: In a consolidated market, entrants win by serving an underserved buyer with a different operating model, not by replicating the incumbent’s full feature set. RULE 1 — IDENTIFY THE NEW BUYER: fintechs and product-led companies valued speed and configurability more than legacy bank relationships. [32][33] RULE 2 — EXPECT PRICE AND INTERCHANGE PRESSURE: transaction-linked revenue is exposed to network fees, regulation, and customer revenue-share demands. [39][40] RULE 3 — SUCCESSFUL ENTRANTS BUNDLE TRUST: bank sponsorship, network access, compliance, and fulfillment must be packaged into the offer. [35][37] RULE 4 — COMMON FAILURE: entering with developer appeal but without enterprise-grade reliability, compliance, or support. MARKET TYPE: Consolidated Market (category). [35][33]
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN DEVELOPER-LED ENTERPRISE FINANCIAL INFRASTRUCTURE: 1. API ACCESS CREATES TECHNICAL PULL. Developers evaluate integration speed and control before commercial stakeholders finalize procurement. [35][36] 2. MARQUEE IMPLEMENTATIONS CREATE CATEGORY CREDIBILITY. DoorDash, Square, and Instacart signaled that the platform could operate at consumer-scale volume. [32][43][33] 3. PARTNER BUNDLING REDUCES TIME TO MARKET. Pre-aggregated bank, network, and fulfillment relationships compress launch timelines. [35][37] 4. THE WEAKNESS: enterprise sales complexity can overwhelm self-serve developer motion when compliance, credit, and multi-country programs enter the deal. [44][37]
| MARKET ENTRY PLAYBOOK
THE STANDARD: A flanking attack is appropriate when the incumbent’s strength serves one buyer archetype while a new buyer archetype has materially different needs. RULE 1 — Choose a buyer whose buying process, product velocity, and risk tolerance differ from the incumbent’s core customer. RULE 2 — Build only the capabilities needed to win that buyer, while securing the regulatory or operational prerequisites they cannot self-supply. RULE 3 — Use the first segment to create referenceable proof before moving toward the incumbent’s traditional customers. RULE 4 — Reject the flank if the new buyer cannot generate enough transaction volume to cover compliance, support, and infrastructure costs; Marqeta’s high-volume marketplace and fintech customers provided that volume. [32][43][33]
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A lighthouse strategy works when one demanding customer validates the hardest parts of the product and creates credibility for expansion. RULE 1 — Select a customer whose use case stresses reliability, compliance, and scale—not merely one willing to pay. RULE 2 — Convert the implementation into reusable architecture, documentation, and operational playbooks. RULE 3 — Failure occurs when the lighthouse requires bespoke work that cannot be productized or when its brand substitutes for repeatable demand. RULE 4 — In regulated infrastructure, use the lighthouse to earn certifications, bank relationships, and audit evidence before broadening. [44][32][37]
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
Marqeta prices primarily against processed transaction value: it earns interchange fees based on a percentage of transaction amount plus a fixed per-transaction amount, along with processing and value-added-service fees. In 2025, net revenue was $624.9 million on $382.5 billion TPV. [39][40]
REVENUE MODEL
Revenue Sharing, Transaction Fee, Service Fee
PRICING MODEL
Revenue Sharing, Usage-Based Pricing, Custom Enterprise Pricing
WHY THEY WON
Marqeta receives interchange from customer card transactions, pays network and issuing-bank fees, and shares a portion of interchange with customers. It also earns processing fees—often percentage-of-volume or per-transaction—and fees for tokenization, fraud, decisioning, digital banking, and other services. Revenue expands with card issuance, transaction frequency, cross-border activity, and value-added adoption; margins depend on network and bank costs. [39][40]
Marqeta uses custom enterprise agreements rather than public self-serve tiers: interchange is transaction-based, processing fees are volume- or transaction-based, and value-added services are separately priced. The meter is customer transaction activity, aligning vendor revenue with the customer’s card-program success. [39][40]
TARGET AUDIENCE
Fintechs and neobanks (enterprise/custom; want card issuing and wallet experiences); marketplaces and on-demand platforms (enterprise/custom; want controlled worker or consumer spend); BNPL and lending companies (enterprise/custom; want virtual cards and installment funding); banks and large enterprises (enterprise/custom; want modern virtual-card and embedded-finance programs). [44][41][43][33]
CUSTOMER BUYING BEHAVIOUR
A product or payments leader identifies a need to issue cards or control spend; engineering evaluates APIs, controls, and reliability; risk, compliance, legal, and finance assess bank sponsorship, network rules, fraud, and economics; procurement negotiates a custom enterprise agreement and implementation plan. [35][44][37]
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Customers pay for the ability to launch and control a financial product without becoming a bank. RULE 1 — PRICE THE VALUE FLOW: transaction-linked fees align vendor revenue with customer card usage and scale automatically. RULE 2 — MONETIZE CONTROL, NOT ACCESS: authorization rules, JIT Funding, fraud tools, and tokenization justify premium economics beyond basic processing. RULE 3 — SHARE INTERCHANGE STRATEGICALLY: revenue sharing makes the customer’s economics better but reduces vendor capture and creates renegotiation risk. RULE 4 — WATCH THE COST TRAP: card-network and issuing-bank fees can rise with volume, so gross TPV growth does not guarantee proportional profit growth. The buyer is buying faster time-to-market and control over card behavior—measured in TPV, active programs, and incremental card products. [38][39][40]
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
Customer concentration: large TPV contributors can dominate volume and negotiate revenue share. Interchange and network-fee exposure: regulation, network pricing, and issuing-bank fees directly affect net revenue and margin. [39][40] Program churn or wind-down: a fintech customer’s failure, pivot, or loss of sponsorship removes future TPV. Compliance and fraud liability: card programs carry KYC, dispute, sanctions, and fraud obligations. [35][37] Platform concentration: dependence on Visa/Mastercard rails and issuing-bank partners constrains independence. [36][37] Macro and consumer-volume sensitivity: TPV can slow with consumer spending and marketplace activity. Marqeta’s 2025 net revenue was $624.9 million, up 23%, with TPV of $382.5 billion; it is publicly traded on Nasdaq as MQ. [39][34][40]
Where the model can break
4
MOTION
motion ge cs
Marqeta sells high-value, regulated, multi-stakeholder card programs through enterprise sales, solution engineering, bank/network partnerships, and implementation support. Its customers require compliance, KYC, fraud, fulfillment, and program-management capabilities; Marqeta also offers Managed by Marqeta for full-service program operation. [35][44][37]
GROWTH EXPANSION MODEL
Platform Expansion, Geographic Expansion
HOW THEY EXPAND
Marqeta expanded from debit and prepaid into credit, added tokenization, fraud, decisioning, and digital-banking services, and extended into more than 40 certified markets. It grew within customers as they added card types, geographies, and use cases; 75% of top customers expanded beyond their first program. [45][44][41][42]
COMPETITIVE STRATEGY
Technology Advantage
HOW THEY COMPETE
Against legacy processors, Marqeta competed on modern APIs, real-time controls, JIT Funding, and faster launch cycles. Against banks and networks, it did not replace them; it aggregated and orchestrated their capabilities into a developer-consumable platform. [35][36][33]
GROWTH ENGINE
GTM
Content Flywheel
Enterprise sales identifies a company that wants to embed financial services; solution engineering maps the card program; Marqeta activates bank, network, and fulfillment partners; successful launch produces transaction volume, data, and expansion into additional programs or geographies. The engine compounds when customer programs scale and cross-sell into credit, tokenization, and international markets; it weakens if implementation is slow, compliance fails, or TPV concentrates in a few customers. [35][44][37]
Marqeta runs a sales-led, developer-assisted enterprise GTM: technical evaluation begins with APIs and documentation, while enterprise sales, compliance, risk, and partnership teams close and implement the program. The primary motion is enterprise sales; developer-led evaluation and partner infrastructure are supporting mechanisms. [35][44][36][37]
SUSTAINING MOATS
High Customer Lock-In
moat
The moat is Marqeta’s certified, multi-party card infrastructure: bank relationships, network access, compliance operations, fraud controls, and production-scale processing are packaged into one platform. Once a customer’s card program, funding logic, and risk rules run on Marqeta, migration requires re-certification and operational disruption. [35][36][37]
| MOAT INTELLIGENCE
THE STANDARD: Infrastructure moats last when regulatory access, operational reliability, and customer configuration compound. RULE 1 — REGULATORY ACCESS: certifications in more than 40 markets and bank/network relationships are costly and slow to recreate. [45][35][34] RULE 2 — PRODUCTION SCALE: nearly $400 billion processed over the last four quarters demonstrates operational credibility at peak volume. [45][46] RULE 3 — CONFIGURATION LOCK-IN: card rules, funding models, tokenization, and fraud logic become embedded in the customer’s product. [38][36] THE SIGNAL: 75% of top customers expanded beyond their first program; the moat does not protect against interchange compression, customer concentration, or a bank/network deciding to offer a competing integrated stack. [44][39][40]
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — FIND THE REAL MODEL: Marqeta tested prepaid loyalty concepts before abandoning them for an infrastructure platform; the early lesson was to stop selling a consumer card product and start selling control. WATCH: avoid building regulated infrastructure before a repeatable customer need exists. [32][33] $1–5M ARR — BUILD THE API WEDGE: The 2014 open-API and JIT Funding launch created a programmable issuing platform. [32][34] $5–10M ARR — WIN TECH-ENABLED WEDGES: DoorDash and Instacart used constrained cards for marketplace workforces, proving real-time authorization value. [32][33] $10–50M ARR — CREATE LIGHTHOUSE PROOF: Square built Cash App Card with Marqeta in roughly six weeks, demonstrating speed against legacy processors. [33] $50–100M ARR — SCALE FINTECH DISTRIBUTION: By 2017, Marqeta had an estimated $70 million revenue and customers including Alipay, Brex, Klarna, and Capital on Tap. [32][33] $100M+ ARR — EXPAND PRODUCT AND GEOGRAPHY: 2020 revenue more than doubled to $290.3 million; Marqeta IPO’d in 2021, added credit in 2021–23, reached $676.2 million net revenue in 2023, dipped to $507.0 million in 2024, then recovered to $624.9 million in 2025 with $382.5 billion TPV. [39][41][42][43][40] Rule: prove a control-rich use case with a demanding customer, then expand only when the platform can productize compliance, scale, and new financial products.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Build infrastructure that gives customers control over a regulated value flow, then monetize the flow rather than the login. SEQUENCE: 1. Choose a regulated workflow where customers need speed and configurability but cannot manage all counterparties. 2. Build the minimum trusted abstraction—compliance, counterparties, execution, and APIs—before pursuing broad distribution. 3. Win one demanding customer whose requirements force production-grade capability, then productize that implementation for adjacent segments. WORKED: Marqeta’s open APIs, JIT Funding, and DoorDash/Square implementations proved that control and speed could displace legacy processor relationships. [35][32][33] CAUTION: Do not copy the interchange-revenue model without modeling network fees, issuing-bank costs, revenue share, and customer concentration. Also avoid API-first positioning if your target buyer requires managed compliance, credit risk, or multi-country operations you cannot yet deliver. [39][37][40]
bottom of page