Stripe
Each of these is a real decision Stripe is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Stripe is a financial infrastructure platform whose APIs and hosted solutions handle payments, recurring revenue (Stripe Billing, used by hundreds of thousands of businesses), card issuing (Stripe Issuing, to create and manage virtual and physical card programs), platform payments (Connect), and banking-as-a-service for direct merchants and platforms/marketplaces in 46+ countries. More than 10 million businesses, including 88% of the Forbes AI 50, build on Stripe, which processes trillions of dollars yearly, around 1.6% of global GDP. It offers Radar (fraud/abuse), AuthBoost (payment optimizations), Financial Connections (open banking), Disputes, Authentication, merchant analytics, and stablecoin products and financial infrastructure. It owns FX and multi-currency management products (FX Acquiring, Multicurrency Settlement (MCS), Currency Conversion) and Metronome, letting companies launch products faster, offer any pricing model, and streamline finance workflows without writing code. Link, its consumer payments product with over 300 million registered consumers, saves payment details for quick, secure checkout and helps businesses improve conversion and offer more payment options.
Your first one is free. No card.
18 live right now.
The rest
Cut over payment ingress without dropping traffic
The old policy engine loses support soon, and 0.7% of shadow-tested requests still differ on client IP handling. Each segment moves one way only, so you decide how much proof is enough before cutting over.
Decide what ships by the rule-change deadline
Only 71% of sampled dispute cases can produce a verified evidence package, and the card network date will not move. You have to choose between covering every merchant and launching a narrower scope you can defend.
Lock the icon system before the regional launch
An audit found 78 of 186 merchant-facing surfaces using outdated or inaccessible payment marks, and production starts before a fixed launch date. What you lock will be hard to unwind once shared surfaces adopt it.
Save payout history before the records expire
A readiness check found that 19% of cross-border payment histories cannot be rebuilt once source retention runs out. You have to weigh what to capture now, because the cutover date is fixed and lost history stays lost.
Prove fee disclosures are correct before the deadline
A card network deadline is coming, and 39% of in-scope card volume has no validated evidence that fee disclosures are set up correctly. You have to weigh compliance against interrupting merchants who are already fine.
Shut off the legacy path without stopping payouts
27% of payment workers still pull credentials from the legacy path, and the generated dependency maps list consumers with no owner. You have to decide how much of that evidence to trust before the old path is turned off.
Cut over to the new way of setting reserves
28% of in-scope merchant balances still lack verified inputs, and the cutover date is fixed and one-way. You have to weigh audit exposure against the cash you take away from merchants.
Commit to a remediation plan for overdue reviews
1,146 high-risk accounts kept processing with reviews past due, and the regulator wants a plan in 14 days. You decide which merchants keep processing while the records disagree about which reviews were done.
Decide how to classify flows before the deadline
27% of in-scope flows still lack a structured classification, and the new treatment takes effect on a fixed date. You have to commit to a model and an evidence standard that hold up once reporting begins.
Fix stored-credential data before enforcement
In nine weeks, 34% of stored-credential volume will flow through integrations that cannot supply the consent and reference fields the new rule requires. You decide what gets fixed, what gets an exception, and what proves it.
Decide how to tell merchants about new pricing
A contract review found 41% of eligible merchants have terms or usage that the draft single message does not fit. You have to decide how far to segment before the contract date, without inviting pricing disputes.
Set the evidence bar for cross-border payments
The regulator's deadline is fixed, and 38% of cross-border volume in scope lacks evidence good enough to classify. You have to weigh keeping merchants live against being sure every affected payment can be reported.
Decide who moves to the mandated flow
A fixed enforcement date is coming, and 38% of eligible volume sits on custom confirmation flows that will break. You have to pick who migrates, and lean on verified safety evidence rather than rollout counts.
Lock the migration terms before renewal closes
The marketplace will sign only if you move its top merchants off a rival processor in six months, and its incumbent deal ends in 28 days. You have to weigh the incentives it wants against loss exposure you cannot unwind.
Stop tokens from landing on the wrong customer
Account-updater events can arrive after a payment method is detached, and that can restore a credential to the wrong customer. You have to settle the state model before the network deadline, and bad history is costly to unwind.
Move connected accounts onto tax reporting
A readiness review found 29% of eligible connected accounts have no verified reporting data, clustered in a few high-volume platforms. You weigh filing readiness against the churn risk of pushing sellers before the deadline.
Decide how merchants read the new settings
In a readiness review, 37% of merchants misread how the consolidated settings would change behavior on live payments. The date is fixed, so you have to weigh how much to simplify now against what you explain at cutover.