Apple Card Missed Payments: Diagnose Causes, Plan Fixes and Measure Success

Apple Card customers are missing their monthly payments in large numbers. The missed payments are hurting their accounts, and the volume of complaint calls is high. You are a product manager on the Apple Pay team and are asked to work through the problem in three steps. ### Clarifying Questions - Is this a recent spike, or a level that has been building for a while? - Do the complaint calls reach Apple support, the issuing bank's service line, or both, and are they tagged by reason? - Is the problem concentrated anywhere, for example new accounts, customers with installment plans, or customers paying from one particular bank? - Does "not making payments" mean missing the minimum due, or paying less than the full balance and being charged interest? ### Part 1 — Why payments are missed and what it does to accounts Why might customers be having trouble paying on time, and what happens to their accounts when they miss a payment? ```hint Three different customers Separate the customers who tried to pay and failed, those who never tried, and those who could not afford to. Each group needs a different fix and leaves a different trace in the payment data and the calls. ``` #### What This Part Should Cover - A structured set of causes (payment mechanics, awareness and understanding, ability to pay) and how each would be confirmed or ruled out - The evidence used to narrow the cause: call reasons, payment attempts, timing and segments - The consequences of a missed payment for the customer's account, and why they generate calls ### Part 2 — Considerations and a sequenced build plan How should the Apple Pay team address the issue? Which considerations shape the response, what would you build, and in what order? ```hint Who can ship what The issuing bank, not the product team, controls credit terms, hardship programs and collections. Sort your ideas by what the team can ship alone and what needs the bank, and let that inform the order. ``` #### What This Part Should Cover - Constraints: the bank partnership, consumer-credit regulation, privacy, support capacity and customer trust - Specific features mapped to the causes found in Part 1 - A sequence justified by impact, effort and dependencies, and how findings would change it ### Part 3 — Measuring success How would you know the work is succeeding? ```hint Watch for a false win Complaint calls can fall simply because customers stop bothering to call. Pair each success metric with one that would expose a misleading improvement. ``` #### What This Part Should Cover - Primary outcomes for on-time payment and for complaint volume - Guardrails such as credit losses, notification opt-outs and satisfaction - How changes would be attributed to the work, given that payments happen monthly ### What a Strong Answer Covers - A hypothesis-driven diagnosis that uses data and call reasons before jumping to features - Different responses for customers who hit a broken flow, who forgot or misunderstood, and who cannot afford to pay - A clear split of responsibilities between Apple and the issuing bank, including compliance limits - Customer trust and financial wellbeing weighed against short-term interest revenue ### Follow-up Questions - The data shows most missed payments follow a bounced payment from the customer's linked bank account. What changes in your plan? - Reminder notifications raise on-time payments but also raise complaints about too many alerts. How do you decide what to keep? - Finance points out that interest revenue falls when fewer customers carry a balance. How do you respond?