Meta Eyes Stripe Stablecoins for 2026 Rollout

TheNewsCrypto2026-02-25 tarihinde yayınlandı2026-02-25 tarihinde güncellendi

Özet

Meta Platforms plans to integrate stablecoin payments into Facebook, Instagram, and WhatsApp in the second half of 2026, with Stripe likely as the infrastructure partner. This marks a strategic shift from its failed Libra project, as Meta will not issue its own token but instead rely on third-party stablecoins, positioning itself as a distribution layer. The focus is on reducing costs and speeding up cross-border payments for creators, particularly for small amounts. Regulatory clarity from the 2025 GENIUS Act and Stripe’s regulated infrastructure may enable a compliance-first approach. Meta has not disclosed which stablecoins will be supported or specific implementation details.

Meta Platforms is preparing to integrate stablecoin payments across Facebook, Instagram, and WhatsApp in the second half of 2026. The company has reportedly issued requests for proposals to external infrastructure providers, with Stripe emerging as the likely partner.

The move signals Meta’s renewed interest in digital payments, but under a very different structure than its failed Libra project. This time, Meta will not mint its own token. Instead, it plans to rely on third-party stablecoin infrastructure and position itself as a distribution layer.

Stripe’s Bridge platform appears central to the plan. Stripe acquired Bridge for approximately $1.1 billion in October 2024. In February 2026, Bridge secured conditional approval from the Office of the Comptroller of the Currency (OCC) to operate as a national trust bank.

A Strategic Shift From Libra to Infrastructure Integration

Meta’s 2019 Libra project received a strong pushback from regulators. They were not in favor of a global currency that would be secured by a portfolio of assets controlled by corporations. The project was later renamed Diem but failed.

The current plan does not have sovereign-like goals. Meta plans to include existing stablecoins rather than issuing a new one. Sources say Meta wants to start the new project at arm’s length to minimize regulatory resistance.

Stripe CEO Patrick Collison was added to Meta’s board in April 2025. This happened before Bridge’s conditional OCC approval and Meta’s outreach to infrastructure companies.

Focus on Cross-Border Creator Payouts

Meta hopes to minimize the cost of small cross-border payments to international creators, especially when the amount is about $100. The usual wire transfer and foreign exchange costs tend to reduce the value of cross-border payments.

Stablecoin-based payment systems might help speed up payment times and minimize costs. Meta’s platforms currently support about 3 billion people around the globe, giving Meta the scale to adopt new technologies.

Stripe, in its 2025 annual letter, observed that the number of transactions on Bridge quadrupled with the increased use of stablecoins, even going beyond the crypto cycles. You can check the OCC charter news updates on the Office of the Comptroller of the Currency website.

Regulatory Clarity Changes the Landscape

The GENIUS Act, passed in July 2025, provided a federal framework for fully reserved payment stablecoins. This act provided more defined guidelines for companies operating in the U.S. market.

Bridge’s conditional trust bank approval is consistent with this framework. Unlike the Libra era, companies now operate within defined federal guidelines rather than regulatory ambiguity.

Several implementation details remain unresolved. Meta has not disclosed which stablecoins it will support. The company also has not clarified whether it will abstract blockchain functionality from users or enable direct on-chain interactions.

Meta declined to comment on the reported plans, and Stripe has not publicly confirmed the partnership.

If the integration proceeds, Meta could reenter the digital payments space in a compliance-first manner. By leveraging Stripe’s regulated infrastructure, the company may transform its social platforms into stablecoin-enabled payout hubs.

The 2026 rollout could mark one of the largest mainstream stablecoin integrations to date.

Highlighted Crypto News:

Oobit, Backed by Tether, Expands to Crypto-to-Bank Transfer

TagsCrypto PaymentsGenius ACTMetaStablecoinStripe

İlgili Sorular

QWhat is Meta's reported plan for integrating stablecoin payments, and when is it expected to be rolled out?

AMeta is preparing to integrate stablecoin payments across Facebook, Instagram, and WhatsApp in the second half of 2026.

QHow does Meta's new stablecoin strategy differ from its failed Libra (Diem) project?

AUnlike the Libra project, which aimed to create a new global currency, Meta's new plan will not mint its own token. Instead, it will rely on integrating existing third-party stablecoins and act as a distribution layer.

QWhich company is reportedly the key infrastructure partner for this initiative, and what recent regulatory approval did they secure?

AStripe is the likely partner, specifically through its Bridge platform. Bridge secured conditional approval from the Office of the Comptroller of the Currency (OCC) to operate as a national trust bank in February 2026.

QWhat is one of the primary use cases Meta is targeting with stablecoin integration on its platforms?

AA primary use case is to minimize the cost and speed up the time of small cross-border payments, particularly for international creator payouts, where traditional wire transfer and foreign exchange fees are high.

QWhat recent U.S. legislation provided a clearer regulatory framework that benefits stablecoin projects like Meta's?

AThe GENIUS Act, passed in July 2025, provided a federal framework for fully reserved payment stablecoins, offering more defined guidelines for companies operating in this space.

İlgili Okumalar

After Tokenizing Assets, How to Exit?

After tokenization, a key unresolved issue is providing holders with a reliable exit mechanism, as underlying asset settlement (taking days to months) lags far behind on-chain token settlement. Three primary models for instant liquidity have emerged, differing in their capital structure and efficiency: 1. **Balance Sheet Model (e.g., Grove Basin):** A single, well-capitalized entity (like Sky) provides immediate liquidity from its own reserves. This offers simplicity and deep initial liquidity but is constrained by that single balance sheet's capacity and risk appetite, limiting scalability. 2. **Dedicated Vault Model (e.g., Upshift Clear):** Independent liquidity providers (LPs) fund separate vaults for each supported asset. This decentralizes capital sources but isolates liquidity and capital, which becomes inefficient as the number of tokenized assets grows. 3. **Shared Liquidity Layer Model (Symbiotic Liquid Lane):** Independent capital providers fund shared vaults that can support multiple tokenized assets simultaneously. Capital remains productive between redemptions (e.g., earning yield in DeFi markets). Exits are settled via a competitive RFQ market where market makers bid. The article argues that the shared layer model offers superior capital efficiency and scalability. It transforms exit liquidity from an asset-specific patch into shared market infrastructure, allowing liquidity capacity to grow with overall market participation rather than being fragmented per asset. This is particularly valuable for longer-duration assets like private credit, where reliable T+0 exits can significantly enhance their utility in DeFi.

链捕手12 dk önce

After Tokenizing Assets, How to Exit?

链捕手12 dk önce

Anthropic's Triple Moment: Code Leak, Government Confrontation, and Weaponization

This article analyzes Anthropic's recent conflicts and strategic moves following the U.S. government's emergency halt of its new Fable model, citing national security concerns over potential "jailbreaks." The author argues this incident reveals deeper tensions between AI labs, governments, and the software industry. While critics view Anthropic's safety-focused rhetoric as marketing fear, the author suggests it serves as a commercial moat masking the company's core economic imperative: moving closer to end-users and their valuable data to avoid being commoditized. The piece outlines a coming clash between frontier AI labs like Anthropic and established software companies. Labs need real-world usage data for model improvement via reinforcement learning, creating a cycle where better products attract more users and more data. This threatens software firms who, as Microsoft's Satya Nadella warns, risk having their value captured by a few dominant models. Anthropic's controversial policy changes—initially secretly degrading Fable's performance for LLM development and expanding data retention—are framed as assertions of control, justified by its safety narrative. The company's foundational belief that it alone is sufficiently concerned about superintelligent AI dangers legitimizes its actions, from resisting government demands to shaping usage policies. The author concludes that this alignment of mission, talent, and business strategy is powerful but concerning, as it concentrates immense potential power in the hands of those convinced of their own righteous understanding.

marsbit22 dk önce

Anthropic's Triple Moment: Code Leak, Government Confrontation, and Weaponization

marsbit22 dk önce

Xpeng and NIO Compete on Computing Power, Li Auto Shifts Architecture

On June 15, 2026, Li Auto unveiled details of its self-developed chip, Mahe M100, for its new L9 Livis model. CTO Xie Yan stated the goal was not just a faster chip, but a fundamentally different one, targeting the chip architecture itself. While competitors like NIO, Xpeng, and Huawei highlight TOPS (computing power) figures for their self-developed chips, Li Auto’s Mahe M100 focuses on redesigning the underlying architecture. It employs a "dynamic data flow architecture" to address memory bandwidth bottlenecks in large model inference, claiming up to 3x the effective computing power of Nvidia's Thor U for its specific workloads and a 40% reduction in latency. The chip's design was peer-reviewed and accepted at ISCA 2026. However, this performance is highly optimized for Li Auto's own VLA2.1 algorithm, meaning it may not generalize as well to other tasks. Li Auto aims to achieve full-stack in-house development with Mahe M100, covering chip, compiler, OS, AI algorithms, and domain controller—a level of vertical integration few competitors match. Beyond the chip, CEO Li Xiang introduced a new strategic narrative: the "embodied intelligent vehicle," defined as an integration of an EV, a professional driver, an AI computer, and a life assistant. This shifts competition from features like large screens to systemic AI capabilities. A key commitment was that Li Auto's Mahe VLA autonomous driving model will match Tesla's FSD V14 by Q4 2026, with specific OTA milestones set for July, September, and December. Financially, Li Auto faces pressure with declining revenue and vehicle gross margins since Q4 2025, while maintaining high R&D investment (approx. ¥12B in 2026, 50% AI-related). Its 2026 sales target is 550,000 vehicles, up from 406,000 in 2025. The new L9 Livis garnered over 10,000 pre-orders in two weeks. The effectiveness of these strategic moves—new products, OTAs, and the novel chip architecture—will begin to show in Q3 2026 financial results, with the year-end FSD V14 benchmark being the ultimate test.

marsbit1 saat önce

Xpeng and NIO Compete on Computing Power, Li Auto Shifts Architecture

marsbit1 saat önce

The Year of AI Applications: Saying 'Yes' While Ignoring Risks? A Comprehensive Open Source Log of Software Development's Journey

The Year of AI Applications: Blindly Saying "Yes" While Ignoring Risks? A Software Development Log Goes Fully Open Source. AI-generated code harbors risks hidden within seemingly correct programs, potentially leading to data leaks or asset loss. The open-source project "Narwhal AI Code Risks," from Peking University's Narwhal-Lab, compiles real-world cases, early warning signs, and typical risk pathways. Its goal is to help developers identify potential hazards early and avoid repeating past mistakes. In 2026, code is generated faster than ever but deployed with less scrutiny. The danger often lies not in glaring errors, but in code that appears normal—syntactically correct, passing all checks—yet introduces subtle but critical flaws like non-existent dependencies, excessive permissions, or exposed databases. A stark example is the Moonwell cbETH oracle incident. A configuration file error, where a cryptocurrency price was set to ~$1.12 instead of ~$2,200, slipped through 28 checks and a pull request signed by both AI (Claude, Copilot) and human developers. This "semantic deviation" resulted in a loss of $1.78 million. The risk is that AI can produce functionally valid code that is semantically wrong for the business context. As AI moves beyond simple code completion to modifying configurations, installing dependencies, and operating via autonomous agents, it traverses longer, less traceable paths within software engineering, blurring traditional boundaries and oversight points. The Narwhal AI Code Risks project structures information into three layers: `/cases` for documented real-world incidents, `/inferred` for early warning signals, and `/scenarios` for clear, generalized risk patterns not yet tied to specific events. This aims to create a lasting, public record to prevent collective amnesia about past AI-coding pitfalls. Risks are categorized into seven areas: Software Supply Chain (e.g., recommending fake packages), Code-Level Vulnerabilities (e.g., reintroducing path traversal bugs), Cloud & Infrastructure Misconfiguration (e.g., overly permissive settings), Agent Risks (from autonomous tool execution), Vertical Domain Risks (e.g., in finance, healthcare), Intellectual Property & Compliance issues, and Human Factors (like over-reliance on AI output). The project's core value is transforming isolated incidents into reusable knowledge—a foundational resource for developers to spot similar issues, for security researchers to build upon, for toolmakers to create detection rules, and for the community to contribute new findings. As AI integration accelerates, this open-source "logbook" serves as a crucial navigational aid, charting past errors to help future projects steer clear of the same traps.

marsbit1 saat önce

The Year of AI Applications: Saying 'Yes' While Ignoring Risks? A Comprehensive Open Source Log of Software Development's Journey

marsbit1 saat önce

İşlemler

Spot
Futures
活动图片