Meta Payments Strategy: Build In-House or Partner with a Payments Provider

Suppose Meta had never launched Meta Pay. Would you advise Meta to build its own payment product in-house or to partner with an established payments company? Make a recommendation and justify it. ```hint Split the payment stack "Payments" bundles a wallet and checkout experience, card processing, licenses and compliance, and fraud management. Ask which of those layers create strategic value for Meta before deciding who should own each one. ``` ### Clarifying Questions - Which use cases are in scope: checkout in Facebook and Instagram Shops, Marketplace purchases, person-to-person transfers in Messenger and WhatsApp, donations, or digital purchases such as VR apps? - Is the goal fee revenue, or more completed purchases on Meta's apps that make ads and commerce more valuable? - Does "partnership" mean a processor embedded behind a Meta-branded checkout, or sending users to a partner's own branded wallet? - Which markets come first: the US only, or also WhatsApp-heavy markets that run on their own instant payment systems? ### What a Strong Answer Covers - A clear recommendation tied to what payments would do for Meta's core business - Explicit decision criteria such as control, time to market, cost, regulatory exposure, data and user trust - Each option weighed against those criteria, including a hybrid that splits the stack - A phased plan, the metrics that judge it, and the conditions that would change the decision - Risks specific to Meta: regulatory scrutiny, privacy concerns about payment data, and dependence on a partner ### Follow-up Questions - Your main processing partner raises its fees and launches a competing consumer wallet. How does your plan respond? - Regulators in a large market object to Meta holding payment data. What would you change? - How would the answer differ for person-to-person payments in WhatsApp in a country where a government-backed instant payment system dominates?