Task you can run code by using
./mvnw spring-boot:runPlease note that it's better to only implement half of requirements but do absolutely best you can.
Payment creation
Client should be able to create payment of one of 3 types - TYPE1, TYPE2, TYPE3. Fields 'amount' (positive decimal), 'currency' (EUR or USD), 'debtor_iban' and 'creditor_iban' (texts) are mandatory for all types.
Additional type-specific requirements:
-
TYPE1 is only applicable for EUR payments, has additional field 'details' (text) which is mandatory;*
-
TYPE2 is only applicable for USD payments, has additional field ‘details’ (text) which is optional.
-
TYPE3 is applicable for payments in both EUR and USD currency, has additional field for creditor bank BIC code (text) which is mandatory.
Payment cancelation
Client should be able to cancel the payment. It is possible to cancel payment only on the day of creation before 00:00. When cancel happens, cancelation fee should be calculated and saved along the payment in database.
Cancelation fee is calculated as: h * k
Where h - number of full hours (2:59 = 2h) payment is in system;
k - coefficient (0.05 for TYPE1; 0.1 for TYPE2, 0.15 for TYPE3). Result is an amount in EUR.
Payments querying
It should be possible to query all payments that aren't canceled as well as filter them by amount. Query should return payment IDs.
There should also be an option to query specific payment by ID, and it should return payment ID and cancelation fee.
Client country logging
Resolve clients country (use any external web service to resolve it by user IP) and write it to the log (that’s OK if it will fail sometimes). Information about clients country won't be required anywhere in business logic.
Notification
Imagine other (micro)service should be notified about the fact we saved valid TYPE1 or TYPE2 payment.
Send HTTP request to resources of your choice (should be different for TYPE1 and TYPE2 payments). Consider any 2XX response status code as a success.