3 Stripe phone-screen problems reported July 25–28 (updated July 30)

I found three recent full-time Stripe records in the FastPrep catalog tagged as phone screens. The common thread is not one LeetCode pattern—it is translating business rules into deterministic code.

1. Invoice / Payment Reconciliation — Medium — last reported July 28 — 3 catalog sightings

https://www.fastprep.io/problems/stripe-invoice-payment-reconciliation

What it exercises: parsing semi-structured records, applying match tiers in strict priority, and deterministic tie-breaking.

2. Group Linked Merchant Records — Medium — last reported July 28 — 1 catalog sighting

https://www.fastprep.io/problems/stripe-linked-merchant-groups

What it exercises: normalizing identity fields and grouping indirect connections, not just direct matches.

3. Rule-Driven Transaction Fraud Detection — Medium — last reported July 25 — 1 catalog sighting — also tagged OA

https://www.fastprep.io/problems/stripe-rule-driven-transaction-fraud-detection

What it exercises: mutable rules, updates and deletes, and evaluating each transaction against the state at that moment.

If prep time is limited, the transferable practice here is to make precedence explicit, decide which fields can create relationships, and test state changes in sequence. That seems more useful than memorizing the payment or fraud story.

Important caveat: these are catalogued interview reports, not official Stripe questions. Dates and frequencies are catalog metadata and do not predict what will repeat. The original reports omitted some schema or output details, so FastPrep supplied runnable details in the practice versions.

Disclosure: I work on FastPrep, and the links above are FastPrep practice pages.