This week’s news points to a more disciplined model of product growth: stronger control layers, clearer ownership, and infrastructure that supports scale without multiplying operational complexity.
U.S. open banking enters a more uncertain operating model
The CFPB’s Section 1033 rule, designed to govern consumer-authorized access to financial data in the U.S., reached a key deadline on April 1, 2026. But the rule is now under review, enforcement remains uncertain, and the market is still debating who should bear the cost of the infrastructure behind permissioned data sharing. At the same time, major banks continue shifting from screen scraping to API-based access, so the operating environment is changing even without a clear regulatory path.
Source: americanbanker.com
Why it matters
Regulatory uncertainty has not slowed the infrastructure shift underneath it. As banks push toward API-based access and challenge the economics of secure data sharing, account connectivity becomes more than a supporting integration. It starts to affect provider strategy, consent performance, fraud controls, and the cost of bank-data-heavy product flows.
For fintech teams, account connectivity becomes a core platform capability. It requires an architecture that can handle changes in access models, providers, pricing, and bank coverage over time.
What teams should watch
Focus on whether your product is ready to operate in a world where account connectivity is core infrastructure. This layer now shapes provider strategy, consent performance, fraud controls, and the economics of bank-data-heavy product flows.
What teams should do:
- Treat account connectivity as a platform capability.
Build a dedicated layer for provider abstraction, consent flows, token lifecycle management, retries, fallbacks, and observability.
- Reduce dependency on a single aggregator.
Make it possible to switch providers by bank, use case, and economics rather than locking critical flows to one partner model.
- Recalculate the unit economics of bank-data-heavy features.
Identify which use cases can still hold up if access costs rise or provider terms change.
- Bring consent and reconnection flows up to an operational standard.
Measure completion, latency, recovery, and drop-off across banks and providers instead of treating consent UX as a one-time integration detail.
- Move critical flows off screen scraping where possible.
Products that still depend on scraping for important journeys carry more operational and partner risk as banks continue shifting toward APIs.
- Design for change in regulation, pricing, and partner models.
This layer needs clear ownership across product, platform, risk, and partnerships, with enough flexibility to absorb shifts in access rules and commercial terms.
Experian turns credit reporting into a self-service platform for smaller lenders
Experian introduced a new self-service platform for community banks, credit unions, and other smaller lenders that lets them complete credentialing and onboarding online and start accessing consumer credit reports with fewer manual steps. The service includes guided application flows, real-time credentialing, subscription-based plans, and built-in tools such as VantageScore 4.0, Fraud Shield, and PreciseID to support common underwriting and fraud prevention workflows.
Source: experianplc.com
Why it matters
Access to credit infrastructure is becoming easier for smaller lenders to activate. Community banks, credit unions, and other lenders can now reach bureau data, scoring, and fraud tools faster, with less manual onboarding and implementation friction. For fintech teams, that shifts competitive advantage away from access itself and toward decision quality, antifraud logic, workflow design, and the speed at which new lending scenarios can be launched and controlled.
This also reflects a broader change in how credit infrastructure is being packaged and delivered. Bureaus and data providers are turning access into a more standardized, subscription-based product with digital onboarding and embedded tooling. That can shorten launch timelines and expand access, but it also raises the bar for risk governance. Faster activation does not replace strong credit policy, explainable decisions, or disciplined control over decision quality.
What teams should watch
Watch where lending products will now separate operationally: in decisioning quality, antifraud logic, workflow design, launch speed for new scenarios, and the strength of risk controls behind them.
What teams should assess now:
- Build a dedicated decisioning layer. Bureau data, scoring, fraud checks, policy rules, adverse action logic, and audit trail should not be scattered across the product.
- Increase change velocity. New credit rules, segments, and workflows should be launched in days, not quarters.
- Strengthen antifraud and explainability. Embedded fraud tools are becoming a market standard, but your team still needs clear decision reasoning, not just a score.
- Measure economics at the scenario level. As infrastructure access becomes easier, the winners will be the teams that better manage CAC, approval quality, fraud loss, manual review rate, and time to funding.
- Standardize onboarding and compliance as product workflows. If competitors can complete credentialing and activation digitally and quickly, manual processes on your side will start to look like a product defect.
In practical terms, the goal is no longer just to connect to a bureau. It is to build a lending platform inside the product, with fast rule orchestration, an embedded fraud and risk layer, measurable economics, and minimal manual operations.
U.S. digital wallets keep gaining share as wallet-led checkout expands
In the U.S., digital wallets are expected to keep taking share from cards through 2030. According to Worldpay, wallet payments will rise to 44% of e-commerce transactions and 26% of in-store payments. Wallets already lead U.S. online payments with a 40% share, compared with 32% for credit cards. In physical retail, cards still hold the top spot for now, but their share is projected to decline.
Source: paymentsdive.com
Why it matters
For fintech teams, this signals a shift in more than consumer preference. It changes where the payment experience is actually controlled. Wallets already lead U.S. e-commerce payments, and Worldpay expects that lead to grow through 2030. At the same time, cards are not disappearing. More often, they sit behind the wallet as the funding layer inside the customer-facing flow.
That changes what product teams need to optimize. The challenge moves from card acceptance alone to wallet execution: how checkout is structured, how tokenized credentials are managed, how routing and fallback logic work, how fraud controls are applied, how approval performance is improved, and how wallet behavior is measured across the journey. As more of the experience is shaped inside the wallet layer, the payment stack becomes a question of control, conversion, and resilience inside the product.
What teams should watch
Teams should review whether the payment stack is built for wallet-led flows or still optimized around a card-first journey. As wallets take more share in e-commerce and expand further in-store, teams need to review where performance, risk, and recovery actually sit across the payment flow.
What to pay attention to first:
- Wallet UX – whether the journey is truly wallet-native, fast, and easier to complete than the card flow. Placement, speed, fallback behavior, and repeat usability all affect conversion.
- Orchestration – whether token lifecycle, routing, retries, fallback logic, and wallet-specific approval performance are managed through one coordinated control layer.
- Fraud model – whether risk checks account for wallet, device, token, and session context, rather than relying only on card-level signals.
- Metrics – whether teams measure wallet adoption, conversion, fallback, token failures, repeat usage, and approval performance instead of looking at approval rate alone.
- Control points – whether the product still controls the critical parts of the payment experience or whether too much of that experience now sits inside an external wallet layer.
- Resilience and compliance – whether tokenization, auditability, exception handling, disputes, outage fallback, and provider dependency are visible, owned, and built into the operating model.
Cross river raises $50M to scale embedded finance
Cross River has raised $50 million in new capital to expand its platform across AI, crypto, and embedded finance. The company is framing this as the next stage of embedded finance: a single platform where lending, payments, cards, and crypto are managed through a shared AI layer for compliance and risk. The funding will also support new products, deeper partnerships, and international expansion.
Source: businesswire.com
Why it matters
Cross River’s positioning points to a broader shift in embedded finance: growth is moving beyond adding standalone financial capabilities and toward running lending, payments, cards, crypto, and control logic through a more unified platform model. As providers expand across multiple financial functions, competitive value shifts toward how well those functions are coordinated, governed, and scaled together inside the product.
For fintech teams, that raises the bar on platform design. The harder challenge is building a system that can preserve money-state clarity, routing consistency, controls, and exception recovery across multiple flows without adding operational drag. That shifts development priority toward orchestration, embedded risk and compliance logic, and operating layers that support expansion without fragmenting the product.
What teams should watch
Focus on how money is governed inside the product. The market is moving toward platforms where payments, lending, cards, crypto, and control logic run through a shared operating layer, with AI applied across compliance, risk, monitoring, and user-facing workflows.
What to assess right now:
- Do you have a unified orchestration layer for money movement, or is business logic still fragmented across providers and rails?
- Can the system explain money state across ownership, balances, routing, retries, reversals, exceptions, and audit history?
- Are risk, compliance, and monitoring embedded directly into the flow, or do they still rely on manual reviews and operational workarounds?
- Can you add new rails, partners, or products without rewriting core logic?
What teams should do to keep up:
- Shift roadmap priority toward the platform layers that govern money state, routing, controls, and exception recovery.
- Strengthen ledgering, reconciliation, and exception handling. These are core scaling infrastructure.
- Move rules and evidence into explicit system layers: policy logic, decision logs, traceability, and reporting.
- Apply AI where it improves decisioning, anomaly detection, and operational monitoring.
- Reduce stitching costs by using a shared model for events, statuses, and money states across integrations.
Closing insight
Across U.S. fintech, the harder problem now sits deeper in the product stack. Open banking, wallets, credit infrastructure, and embedded finance all show the same shift: core capabilities are becoming easier to connect, while product advantage moves deeper into the systems that govern flow state, decisions, risk, and recovery.
For CTOs and product leaders, that changes where competitive strength is built. It sits less in the integration itself and more in the layers that make the product controllable under real operating pressure: consent, routing, token lifecycle, ledgering, reconciliation, fraud controls, exception handling, and observability. Teams that build those layers as product infrastructure will scale faster, absorb change better, and carry less operational drag.