This week’s system design refresher: CI/CD in 5 minutes (Youtube video) Visa dispute and chargeback Deployment strategy Designing a chat applicationThanks for reading ByteByteGo Newsletter! Subscribe for free to receive new posts and support my work.
What if something goes wrong at step 5 such that the message couldn't be enqueued? Wouldn't it be better to make that part async? We could utilise database change stream to do that. What do you think?
Hello Alex,
Great information in your newsletter as always. I'm working in the chargeback backend process for large bank and we have following additional steps :-
Step 14 : Issuer bank submits a pre-arbitration to the network which gets passed to the acquirer bank and then the merchant.
Step 15 : Merchant either accepts it or sends a pre-arbitration response back to acquirer bank which is passed to network and then to issuer bank.
Step 16 : Issuer accepts the pre-arbitration response or files an arbitration with the network.
Thank you.
My answer to the chargeback question is: connect the cardholder with the merchant.
✅ If the merchant agrees, the chargeback process starts from the merchant steps, which should cut costs twice;
⛔ if the merchant disagrees, then the standard flow.
Of course, it will work if the merchant and the cardholder are inside one platform marketplace.
What if something goes wrong at step 5 such that the message couldn't be enqueued? Wouldn't it be better to make that part async? We could utilise database change stream to do that. What do you think?