Honor Fluers_Magento

This engagement shall cover implementation of Scenario 2 as whole being the universal set and ensures cover for Scenario 1 default. End objective of completion is: • Customer must be able to make partial payments if the transaction amount is more than the Maximum Transaction Limit (QAR 90,000). • Please keep this limit flexible, in case in future if need be we must simply change the figure on specified line of code if there’s no dynamic User Interface developed. • Customer must be blocked onto the Checkout page unless he/she completes all the outstanding partial payments. • Once the payment initiated, any part payment made must be initiated for processing to the Merchant Account. Technical Constraint: In the current state of application, we’ve identified that the MIGS payment gateway has a maximum limit for transaction which is QAR 95,000. As a result, any events which are above this allowed limit cannot be purchased at the moment and likely, even this affects any purchase of multiple items where the cumulative amount exceeds the allowed limit. Solution: To overcome this limitation, we propose a recursive payment not installments. This must be intuitive and the Buyer must be prompted on Checkout screen that the payment will be broken into “’X’ partial payments each being QAR ‘Y’” Scenario 1: Assume Product A is worth $100,000 Threshold for transaction is $40,000 Issue: User cannot purchase the Product A Solution: When User is redirected from Checkout page to Payment Gateway, we need to breakdown the payments and make it recursive. In this case the first part payment would be $40,000 and once success, the User will be again redirected to Check out page displaying that another part payments must be done and have to pay $40,000 and upon success again redirected to Checkout page to make $20,000 which is the outstanding price. Use Case 1: User honestly follows the procedure of making part payments Use Case 2: User made one part payment, but: • Internet connectivity lost/didn’t continue the payments and went back to website. User must be prompted of the outstanding payment. Any part payment which is already made must be credited to the Merchant Account. Also, the product purchase status must be handled properly and the User must have provision and easy access to make the outstanding payment. Scenario 2: Assume Product A is worth $70,000 & Product B $30,000 Threshold for transaction is $40,000 Issue: User cannot purchase the Product A & Product B Solution: When User is redirected from Checkout page to Payment Gateway, we need to breakdown the payments and make it recursive. In this case the first part payment would be $40,000 ($10,000 for Product A + $30,000 for Product B) and once success, the User will be again redirected to Check out page displaying that another part payments must be done and have to pay $40,000 and upon success again redirected to Checkout page to make $30,000 which is the outstanding price. Use Case 1: User honestly follows the procedure of making part payments Use Case 2: User made one part payment, but: • Internet connectivity lost/didn’t continue the payments and went back to website. User must be prompted of the outstanding payment. Any part payment which is already made must be credited to the Merchant Account. Also, the product purchase status must be handled properly and the User must have provision and easy access to make the outstanding payment. Thanks and look forward to your response.