Wireframe: https://alex-mathai.neetowireframe.com/admin/projects/nzJ/pages/rnq
We capture one payment entry. For a meeting with a payment of 100 INR, if the user books 5 recurring meetings, one payment will be made of 500 INR. The payment entry will be a single entry of 500 INR.
Implementation.
- Clicking on booking link from payments page, should take you to booking with query ?tab=associated to show recurring bookings.
Decision 2: Should we support partial refund?
There seems to be not much work to support partial refund.We just need to calculate the amount. From a UX there will be least change if we support partial refund.
Edge cases:
1. Discount codes
Same as existing logic.
2. Tips
Tip is calculated on a % basis and there will not be any changes. % will be on total amount.
3. Taxes
Taxes can be % or value.
If %, total amount's tax % is taken.
If value, total tax is tax per meeting * number of meetings.
4. Split payment - Total amount will be split.
5. Manual confirmation needed.
- In the wireframe
- Add context to the modal
- Reduce width of the modal
- In case single booking, let's add context of meeting date, and price.
- In case of recurring, add list of recurring meetings, and total price.
- Note the change in first line for both cases, they are different. (This booking for single, n bookings for recurring)
Booking details page.
No change in screens. Payment for each meeting will be shown individually.