Payments infrastructure · United States

Cards-as-a-service
vs. standard credit card

Two card products. One gives a bank total control, the other hands it to the builder. A summary of the US market, August 2026.

01 · What each model is

Traditional

Standard credit card

A bank's product, issued to a consumer. The bank owns every layer, the credit, the card, the data, and the economics.

Chase Amex Citi Capital One

vs

Infrastructure

Cards-as-a-service

Infrastructure a builder embeds. The CaaS provider supplies licensed rails. The builder controls the product, brand, and data layer.

Marqeta Lithic Stripe Issuing Unit

02 · How a transaction flows

Standard card, bank controls every step

Consumer applies

Hard credit pull. Bank underwrites risk.

7 - 14 days

Bank issues card

Bank's BIN. Bank's network relationship. Bank's brand.

Bank owns

Authorization routes to the bank's processor

TSYS, FIS, or Fiserv. No builder visibility into the decision.

Opaque

Interchange flows to the bank

Roughly 1.5 - 2.5% of the sale stays with the issuing bank.^[1]

Bank keeps it

Bank earns interest on carried balances

Average APR runs 20 - 25% across accounts that accrue interest.^[2]

Bank earns

CaaS, builder controls every step

Builder integrates via API

No bank charter needed. BIN sponsorship handled by the CaaS partner bank.

Hours to connect

Card issued programmatically

Virtual or physical. Builder's brand on the card.

Seconds via API

Authorization webhook hits builder logic

Builder approves or declines in real time. Spend policy, fraud, and budget enforced here.

Builder controls

Interchange splits to the builder

Program managers typically keep 70 - 80% of net interchange after network and processor fees, roughly 40 - 60% of gross interchange.^[3]

Builder earns

Full transaction data flows to the builder

No data moat for the bank. Builder uses it for loyalty, underwriting, upsell.

Builder owns

7 - 14 days

Standard card
issuance time

Seconds

CaaS virtual card
issuance via API

~2%

Interchange the bank
keeps on every swipe

40 - 60%

Gross interchange a CaaS
builder can negotiate back

Card issuance timing per NerdWallet. Interchange share per WalletHub. Builder revenue share per Synctera, expressed here as a share of gross interchange for comparability. Directional ranges; actual terms vary by program, volume, and negotiated agreement.

03 · Eight dimensions that decide the right model

Dimension

Standard card

Cards-as-a-service

Issuance speed

7 - 14 days (mail plus underwriting)

Seconds (virtual), 1 - 3 days (physical)

Spend controls

None, the consumer spends freely

Programmable MCC locks, velocity limits, per-card rules

Interchange revenue

100% stays with the bank

40 - 60% revenue share to the builder

Transaction data

Bank owns granular data

Full data stream to builder via webhook

Card brand

Bank brand dominant

Builder's brand on the card

Rewards design

Bank decides structure and value

Builder designs fully custom rewards

Regulatory burden

Bank holds all compliance risk

Shared, bank holds the charter, builder owns KYC and AML

Credit and funding model

Bank underwrites, APR runs 20 - 25%^[2]

Builder configures: charge, debit, prepaid, or BNPL

Treat this as a snapshot of conditions as of August 2026, not a settled map. Interchange caps, revenue share terms, and issuer economics shift with regulation and negotiation.

04 · Who owns each layer of the stack

Standard card, bank owns everything

Bank owns

Consumer has no control

Bank charter and BIN sponsorship

Issuing bank

Credit underwriting

Bank (hard pull, APR)

Core processor (TSYS, FIS, or Fiserv)

Bank-contracted

Card issuance and network relationship

Bank

Transaction data

Bank, full ownership

Interchange revenue

Bank, 100%

Rewards design

Bank decides, consumer has no say

Spend controls

None, zero programmatic control

CaaS, builder controls the product layer

Sponsor bank / CaaS provider

Builder owns

BIN sponsorship and charter

Sponsor bank, e.g. Bancorp or Sutton^[4]

Core processor and ledger

CaaS provider (Marqeta, Lithic, or Stripe)

Card UX, brand, and design

Builder, full control

Spend controls and authorization logic

Builder, fully programmable

Transaction data stream

Builder, no bank data moat

Interchange revenue share

Builder, negotiated split

Rewards program design

Builder, custom structure and value

Credit and funding model

Builder configures: debit, charge, or BNPL

05 · Who builds each

Standard card, who issues it

Mass-market banks

Chase, Citi, Bank of America

Co-brand programs

Delta Amex, Hilton Honors, Amazon Chase

Credit unions

Member-facing card programs

Revolving credit users

Consumers who carry a balance month to month

CaaS, who builds on it

Expense platforms

Brex, Ramp, Divvy, real-time policy enforcement

Vertical SaaS

Trucking, construction, healthcare spend embedded in software

Gig and marketplace platforms

Instant worker payout to a branded card instead of an ACH delay

Hotels and travel

Virtual cards for OTA reconciliation, supplier payments, guest wallets

I write about this from the payments side of the card relationship, 15+ years across American Express, Fidelity, Starwood, and Wyndham. Let's talk. I'm always open to consulting projects, contract work, or Senior Management/Director level roles in travel and payments, and to advisory discussions on programs navigating topics like this.

Get in touch More thinkpieces