Stripe Issuing

Drive the product through a documented public API G

Agent access

Connect an agent via an official MCP server G

Agent access

Plug MCP servers into this product so it can use their tools G

Agent access

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

Issue scoped/least-privilege API credentials for an agent G

Agent access

Point an agent at llms.txt or agent-oriented docs G

Agent access

Run the product headlessly / in CI for automation G

Agent access

Set up automations that run autonomously in the background G

Agentic features

Build against official SDKs G

Agent access

Operate the product with natural-language commands G

Agentic features

Use an official CLI G

Agent access

Subscribe to events via webhooks G

Agent access

Explore an interactive API reference with runnable examples G

Api quality

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

Rely on versioned APIs with a documented deprecation policy G

Api quality

Test against a sandbox environment without touching production data G

Api quality

Give an agent its own card — issue a scoped virtual card to an AI agent with merchant locks, amount caps, and expiry so autonomous purchases stay inside policy, a use the vendor documents by name C

Agent cards

Approve or decline each authorization in real time — a webhook or auth-stream endpoint my code answers inside the network's time budget, with a documented timeout fallback I control C

Auth stream

Define rules that trigger actions automatically on events G

Create a virtual card through the API in one call — PAN, CVV, and expiry available programmatically the moment it's issued — and go from sandbox to a live card without a sales cycle C

Virtual cards

Launch a card program without becoming a bank — BIN sponsorship, network membership, and program management are the platform's problem, and the time from signup to first live card is documented C

Program launch

Set spend limits per card and per cardholder — amount caps over daily, monthly, or all-time windows, and transaction-count velocity rules — enforced by the platform, not my code C

Limits

See money move in real time — account and card balances, a transaction ledger that ties every authorization to its clearing, and settlement reporting that reconciles to the penny C

Balances

Export all of my data in open formats and leave G

Prevent my data from being used to train AI models G

Self-host the core product G

Issue single-use and tightly scoped cards — one purchase, one merchant, an exact amount — so a leaked number is worthless the moment it's used C

Scoped cards

Do everything through the API that I can do in the UI G

An agent can operate my card program — read balances and transactions, create and update cards, and adjust spend controls through the API or an MCP surface with scoped credentials C

Agent operations

Order personalized physical cards through the API — custom card art, bulk orders, shipping methods and tracking — without managing a card manufacturer relationship myself C

Physical cards

Restrict where a card works — merchant category (MCC) allowlists and blocklists, and single-merchant locks — applied at authorization time C

Merchant controls

The platform fights fraud on my issued cards — network fraud scores or its own models surfaced at auth time, suspicious-activity alerts, and tooling to block and reissue compromised cards C

Fraud monitoring

Choose how transactions are funded — prefunded balances or just-in-time funding where my system approves and funds each authorization — with the cash-flow tradeoffs documented C

Funding models

The full card lifecycle is API-driven — activate, pause, unpause, report lost or stolen, reissue with a replacement linked to the original, and permanently close C

Lifecycle states

Cards land in Apple Pay and Google Pay — push provisioning from my app with the entitlements process documented, plus in-wallet card art and manual provisioning as a fallback C

Wallet provisioning

File and track disputes on card transactions programmatically — network reason codes, evidence submission, provisional credit handling, and status webhooks through resolution C

Dispute filing

Simulate the whole transaction lifecycle in the sandbox — authorizations, clearings, reversals, refunds, and declines — so my auth logic is tested before a real card ever swipes C

Simulation

Post-auth events are as programmatic as auth — clearings, refunds, reversals, and chargebacks arrive as webhooks with stable transaction identifiers, so my own ledger never drifts C

Settlement events

Cardholder verification is built into issuance — KYC for consumers and KYB for businesses run through the platform with documented data requirements, review states, and re-verification flows C

Kyc

Every authorization event carries decision-grade context — merchant name and MCC, enhanced merchant data, wallet and entry-mode details, partial-approval and incremental-auth signals C

Auth context

Network tokens are first-class — I can see and manage the tokens created for a card, know which wallet or merchant holds them, and revoke them independently of the PAN C

Tokenization

The platform supports the card types my product needs — debit, prepaid, commercial credit, and consumer credit programs — not just one prepaid rail C

Card types

Cardholder credentials are manageable through the API — PIN set and reset flows, 3DS enrollment for online use where the region requires it — without support tickets C

Credentials

Choose where my data is stored (region/residency) G

Control data retention and deletion G

I get machine-readable reconciliation artifacts — daily settlement files or report APIs covering interchange, fees, and network adjustments — that my finance stack can consume automatically C

Recon reports

Opt out of telemetry and usage tracking G

Perform bulk operations across many items at once G

Read the product's source under an open license G

Schedule recurring jobs or workflows G

Show cardholders their own PAN and CVV without inheriting PCI scope — hosted components or ephemeral-key reveal flows the vendor documents as keeping me out of SAQ D C

Pci scope

Version, review, and roll back my automations G