Cross-Border Money Transfer Product on Crypto Rails for Coinbase

You are a product manager at Coinbase. Design a product that lets people send money to another country using crypto. ```hint Follow the money end to end The sender starts with local money, and the recipient usually needs local money too. Trace every step in between and ask which steps crypto makes cheaper or faster, and which it makes harder. ``` ### Clarifying Questions - Which sender-to-recipient corridor should the first version serve: for example the US to Mexico or the Philippines, or a corridor where the receiving currency loses value quickly? - Must the recipient have a Coinbase account, or should they be able to receive local currency without ever touching crypto? - Is the main goal to bring new users to Coinbase, to grow everyday use of a stablecoin, or to run a profitable transfer business in its own right? - Which payout methods matter in the target country: bank deposit, mobile wallet or cash pickup? ### What a Strong Answer Covers - Why a crypto-based transfer can beat incumbent remittance services for a chosen segment on cost, speed or access, and where it cannot. - A specific sender and recipient segment and corridor, with the pain points that justify the choice. - The end-to-end flow, including how money enters and leaves crypto and who carries price and exchange-rate risk along the way. - Compliance, fraud and trust concerns (identity checks, licensing, irreversible transfers, scams) and how they shape the first version. - Success metrics with guardrails, and a launch plan that starts with one corridor. ### Follow-up Questions - Most recipients in your launch corridor collect cash rather than use a bank or a wallet. How does the design change? - An established transfer service matches your price in the launch corridor. How do you keep growing? - Some recipients want to keep their money in a dollar stablecoin instead of cashing out. Should the product encourage that, and what could go wrong?