Design a Payment System - System Design Interview

0:00 - Context
0:45 - How a payment system works?
3:05 - Scope the problem
5:21 - Functional and Non-Functional Requirements
6:05 - Payment System Components
8:27 - Asynchronous Payments
12:40 - Dealing with Payment Failures
13:17 - Guarantee transaction completion
14:59 - Dealing with Transient Failures
17:54 - Timeout Pattern
19:58 - Fallbacks
20:55 - Dealing with Persistent Failures
22:36 - Idempotency (Avoid double payments)
25:14 - Making use of Distributed Systems
26:56 - Encryption for Data-at-Rest and Data-in-Transit
29:31 - Data Integrity Monitoring
20:43 - Conclusions

[teemalukez]

I’ve been working with payment systems for 2 yrs now. This video has just validated that I haven’t been wasting my time for the past 2 yrs, even though most of the time, I feel like I don’t know what the hell I’m doing 😅. Thank you so much for this video ✌🏾

[kkakaneilthomas]

I'm a PM for a fintech firm. This video is brilliant!! There were so many edge cases that you laid out very well and also explained industry standard solutions. Also, you've structured the video really well. Top class!!! Would've loved if you included DB design as well, but that'd probably be me asking for too much. Thanks again.

[onionsandwich]

This is pure ambrosia. Ah, feed me more, feed me more. I'm savoring each video in the playlist, one at a time, to make it last as long as possible.

[RaghunandanChakravarthy]

Thank you for this video. Any System Designer or a Technical Architect can easily understand the effort and hard work to come up with such presentable content and sharing knowledge.

[carlostelevida]

there's no other video outhere like this, this kind of effort is really appreciated. ❤

[jeffs]

Nice explanation with a good blend of high level and low level concepts. The most important thing that I learned though is that I never want to be involved with a payment system 😀

[egor.cleric]

I would say, that the problem in distributed systems is not 'tight coupling', but in 'high cohesive'. Because one service cannot make system working without another one, but that's ok. Tight coupling means - when you change something in one service - it leads to changes in another service - that's what we should avoid.
I would suggest to check the principles 'low coupling - high cohesive'

[PRATIKGHATAK]

This is absolutely remarkable. Loved how detailed the vlog was covering all the aspects of the implementation. Thank you very much for sharing.

[anirbanchatterjee]

Awesome understanding of the system underlying a payment service architecture.

[AdrianMark]

A truly well presented and thought out video. Learning so much from you. Ps. Don't listen to the guy with the comment on your intonation. You sound a little bit like Károly Zsolnai-Fehér, the voice behind "Two Minutes Papers", which is huge. Hopefully your channel becomes just as big! Keep it up, and thank you for sharing your impeccable logic and comprehensive knowledge.

[eugeneyap]

Came across this video with the intention of learning kafka in payment system, but ended up learning a lot more on the payment system design.
Thanks for the well presented video. Just subscribed to this channel =)

[alexanderzuev]

Wanted to say thanks for this video! In contrast to some other videos on this topic you stay very neat, have really great structure (thanks for breaking the discussion in parts). Keep it up!

[freefortravelsshorts]

This is very well presented op. Kindly share more such videos of complicated systems. This is simply great work, extremely helpful and an amazing free resource for folks preparing for an interview. So a big thank you on behalf of everyone!

[anwar-arif]

Very well explained. This is the best video on payment system I've ever searched for. Thanks for sharing

[yungifez]

Man, you know your channel is good when I watch the first video I encounter and subscribe

[RajdeepBiswasInd]

Very good and relevant explanation. Just edit the video and add the HLD.

[ng.manisha]

Great video. Could you please share a link to the final design diagram as well, and if possible api design and db model? That would really clear major system design concepts

[Trex]

Good video with nice explaination. Only feedback would be the delivery of content. You sound very robotic and that makes watching the video a little boring at times. Perhaps change the pitch and tone of your voice to keep the audience engaged. Keep up the good work!!

[codewithray]

Thanks for sharing this video. You've nicely explained various aspects of designing payment systems.

[huangli]

what a nice explaination about the whole flow! thank you so much!