Bringing Virtual Card Numbers to Capital One Debit and Credit Customers Across Teams

You are a product manager at Capital One, asked to bring virtual card numbers to the bank's debit and credit card customers. Explain how you would work with other teams to set the strategy, design the product, and get it built and launched. ```hint Map teams to decisions List the decisions that only another team can make or block for a bank card product, such as risk limits, compliance sign-off, card-network rules and dispute handling, then decide when each team must join. ``` ### Clarifying Questions - Is this a brand-new capability, or an extension of virtual numbers the bank already offers on some cards? - Which kinds of virtual cards are in scope: single-use numbers, numbers locked to one merchant, or longer-lived numbers with spending limits? - Is the launch for consumer cardholders only, or for small business customers as well? - Where should customers create and use virtual numbers: the mobile app, the website, a browser extension, or all three? ### What a Strong Answer Covers - The customer problem and business goal behind virtual cards, with the differences between debit and credit made explicit - Which teams are involved, what each owns and when each joins, including risk, compliance and card-network partners - Key product design choices for creating, using and managing virtual numbers, including refunds and disputes - An execution plan with a phased rollout and launch-readiness criteria - Success metrics and guardrails covering fraud and customer service ### Follow-up Questions - The fraud team wants a cap on how many virtual numbers a customer can create, and design wants none. How do you resolve it? - How would you measure the fraud reduction when customers who adopt virtual cards may already be more careful than others? - What would make you delay the debit launch while credit goes ahead?