Hei, in my assignment there is a specific backend protocol defined for communication between the application and the payment platform. The thing is that when it comes to payments the first thing I can think about is something like PAYPAL where the customer is redirected directly to a form provided by Paypal itself.
But in order to conform to the requirements where the protocol is a backend protocol I need to create a form within my application where the customer will enter the credit/debit card information and then send it over this protocol to the payment platform.
I have a very strongt desire to make an assumption that the payment platform provides access to a web based form where the customer may feel the payment details. But I am afraid that this will go agains the requirements defind in the assignment. On the other hand I can still use this backend protocol to capture payment notifications or initiate monthly payments on abonament basis.
Do you think that such assumption about the Payment portal is a bit too much of an assumption.
Probably I should stick to the protocol and just implement myself the payment information form.
Not sure how using "backend protocol" or not affects the design, but if it's just where that CC form is (in your app or external), then ... wait for it... an assumption will do.
If that "backend protocol" is so important, the assignment should have say what the protocol is.
Hei Tsang, thanks for the replay. The thing is that in the assignment it is explicitly specified that the backend protocol for communication with the payment system JMS. But if I assume that the payment system provides a form for entering the credit card details and so on.. I am basically going away from the protocol they have specified. It is still true that I can capture notifications for received payments or initiate the recurring payments from the backend. But I am a bit afraid that I am violating the requirements if I dont hold my own form for setting up the credit card details.
