Issues
- 2
One consequence of this design choice is that there are 9 separate Enums where currency is defined which is a maintenance nightmare
#10 opened by RogerBarreto - 1
I never got a successful response. Even with authentication and valid input data, I received 400 responses only.
#8 opened by RogerBarreto - 0
Payment status codes are based on http status codes, this is a bit of a smell to me, I would prefer dedicated codes to avoid any confusion.
#13 opened by RogerBarreto - 0
Add Logging ElasticSearch & Kibana
#16 opened by RogerBarreto - 1
- 0
Gateway project image does not build
#3 opened by RogerBarreto - 1
Authentication failed: "No claims matched in repository to add " for credentials merchant3/merchant3password
#4 opened by RogerBarreto - 0
- 1
CQRS is a good design choice, but this could have been achieved with Command/Query projects (one for each) in the Gateway project.
#9 opened by RogerBarreto - 0
Using third party validation for credit card numbers - this is delegation of critical business logic
#5 opened by RogerBarreto - 1
Expiry date is a date time
#6 opened by RogerBarreto - 0
No tests
#11 opened by RogerBarreto - 0