For All Intents And Purposes Part 3 - Accepting Failure π
See Stripe hiring insights
π Hi there! The description you are currently reading is just 3rd part of the problem set. It is highly recommended to read ALL THE PARTS before coding as parts may build on top of each other π³
The rest of the team is thrilled with our progress building Stripe's new Payment Intent processor, but they pointed out a few cases we should handle before releasing the system to the public π₯
First, payments don't alway succeed and can fail for a variety of reasons like a card network declining a transaction or a bank account not having sufficient funds to be debited. Second, even after payments have succeeded, customers need to be able to request refunds from merchant.
Let's update our implementation to handle two new commands: FAIL and REFUND π₯Ή.
Commands
FAIL <payment_intent_id>
REFUND <payment_intent_id>
βΉ ΰ£ͺ οΉποΉποΉCredit to Rachel π³
commands = ["INIT m1 0", "CREATE p1 m1 50", "ATTEMPT p1", "FAIL p1", "ATTEMPT p1", "SUCCEED p1", "CREATE p2 m1 100", "ATTEMPT p2", "SUCCEED p2", "REFUND p2"] return = ["m1 50"]
π«Ά
- Request Routing SystemOA Β· Seen May 2026
- Email Log Processing, Grouping, and SortingOA Β· Seen May 2026
- Generate Available Time SlotsPHONE SCREEN Β· Seen Apr 2026
- Chat Billing CalculationSeen Mar 2026
- Process List of CommandsSeen Dec 2024
- Card Range Obfuscation Part 2 (ML Eng :)Seen Nov 2024
- Card Range Obfuscation Part 3 (ML Eng :)Seen Nov 2024
- Card Range Obfuscation Part 4 (ML Eng :)Seen Nov 2024
public String[] forAllIntentsAndPurposes3(String[] commands) {
// write your code here
}