Payments - architectural dilemma
Hi everyone 
I'm working on a complex payment application that needs to integrate multiple payment providers (Stripe, PayPal, etc.). I've been pondering the best architectural approach and would love to get some insights from someone who has experience with Payments.
My main dilemma is:
1. Should I implement each payment provider as a separate service within a single solution?
2. Or should I create a separate solution for each payment provider?
I've attached screenshot of 2nd scenario architecture. Any advice would be greatly appreciated.
I'm working on a complex payment application that needs to integrate multiple payment providers (Stripe, PayPal, etc.). I've been pondering the best architectural approach and would love to get some insights from someone who has experience with Payments.
My main dilemma is:
1. Should I implement each payment provider as a separate service within a single solution?
2. Or should I create a separate solution for each payment provider?
I've attached screenshot of 2nd scenario architecture. Any advice would be greatly appreciated.
