Skip to main content
9 events
when toggle format what by license comment
Jul 10, 2018 at 13:26 comment added Falco I would say yes! Pro: if the payment service changes internally you only have to update the UI - and you will not have transitive dependencies (payment changes -> donation changes -> UI changes)
Jul 10, 2018 at 13:22 comment added LangeJan On the same topic: When creating the donation, should we include payment specific options (like payment method) in the same way? So the donation-request includes a payment-request but does not know anything about the contents of the payment request?
Jul 10, 2018 at 13:21 comment added Falco You may decide if the UI code dealing with the payment-result belongs to the payment-service and include the sources there, or if your UI is a consumer which will only share the definition of the interface "payment-result" with the payment service
Jul 10, 2018 at 13:05 vote accept LangeJan
Jul 10, 2018 at 13:05 comment added LangeJan This sound like a solid solution, think it's time to make a proof of concept.
Jul 10, 2018 at 12:51 comment added Falco The payment-result can be of type payment-failed, payment-successfull or payment-pending - where payment-pending includes a callback-url to access the pending payment and maybe provide additional details.
Jul 10, 2018 at 12:49 comment added Falco The donation-service returns a donation-result which will include a payment-result which is opaque to the service. So it does not need to know about the details of a payment service, just that the interface will return some kind of payment-result, which will be sent to the client as part of the donation-result.
Jul 10, 2018 at 12:46 comment added LangeJan I like the idea of this, but doesn't that mean that the donation service returns the redirect url which feels to mee that it needs to know about the payment implementation? That indicates that there is coupling again.
Jul 10, 2018 at 12:36 history answered Falco CC BY-SA 4.0