Skip to content

SYSTEM Cited by 1 source

Stripe Issuing

Stripe Issuing is Stripe's card-issuance product: a set of APIs for creating and managing virtual and physical payment cards backed by the major card networks (Visa / Mastercard), with programmable authorization controls, fund storage, and transaction monitoring.

Docs: docs.stripe.com/issuing.

Issuing is the substrate on which Stripe Issuing for agents (launched 2026-04-29) is built — the agent-specific product is a capability layer atop the full Issuing API surface, not a replacement or subset.

This wiki page is a stub; Stripe Issuing predates the 2026-04-29 launch by several years and has rich mechanics (authorization webhook, real-time controls, card-network settlement, funding-source primitives, physical + virtual card issuance, Connect platform flows) that are outside the scope of the current ingest. Future Stripe Engineering posts disclosing Issuing internals will expand this page.

Known capabilities (from the 2026-04-29 post's framing)

The launch post references Issuing primitives in the service of describing what Issuing for agents provides. Each is present on the base product:

  • Virtual cards — issued via API, usable anywhere network-accepted card credentials are.
  • Single-use / scoped-use virtual cards — cards that enforce a scope (amount, currency, merchant) at the authorization boundary; the agent-layer primitive this wiki canonicalises at concepts/single-use-virtual-card-for-agents is a specialisation of this Issuing capability.
  • Fund storage — balances the cards draw against; distinct from raw-card-on-file architectures where cards charge an external funding source directly.
  • Spending controls — programmable limits / restrictions per card.
  • Transaction monitoring — historical + real-time API access to card activity.
  • Fraud tools — composition with Radar at authorization time.

Issuing vs PaymentIntents

  • PaymentIntents is the payment-acceptance API: merchant charges a buyer's payment method.
  • Issuing is the credential-issuance API: platform creates a payment method usable by a cardholder or agent acting on their behalf.

Composite products (like Link's wallet for agents) use both: Issuing to create the scoped card the agent uses; PaymentIntents at the other side to settle the resulting charge into the consumer's account.

Known deployments on this wiki

Other third-party Issuing deployments (expense-management, embedded-fintech, marketplace-seller-tooling) are canonical use cases but not individually ingested.

Seen in

Last updated · 446 distilled / 1,275 read