Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

1. Use case name (Required)

"Student Account Billing" Payment Method

2. Keywords (Required)

custom, new, payment method, student account, billing

3. Actors + description (Required)

  • As the cashier, I want to checkout for customer using “Student Account Billing” payment method

4. Main flow (Required)

The most common path of interactions between the user & the system:

  1. The cashier selects “Take Payment” to complete the transaction for the customer, the POS displays the payment screen

  2. The cashier selects “Student Account Billing” to proceed payment process for the customer, the POS processes and displays “Terms and Conditions” page associated with “Student Account Billing” payment method

  3. The cashier informs the T&C to the customer, especially the return and/or exchange to the customer and select “I agree to these terms” if the customer accept and agree to the T&C, the POS processes and display “Accept Amount” page.

  4. The cashier then enter the amount that the customer want to pay using “Student Account Billing” method and selects “Accept”, the POS processes and records the transaction.

5. Alternative flows (if any)

4.a The cashier can add another payment method by clicking “Add Payment” in case the customer does not want to pay the full amount using “Student Account Billing” payment method, the POS processes and displays other payment methods (i.e. cash, credit card, etc.)

6. Fit & Gap analysis (Keep internal)

Compare this use case with the current Magestore solution to identify 3 types:

  • FIT 100%
  • Partially FIT + What is the GAP then?
  • GAP 100%

There is no “Student Account Billing” supported at the moment

  • No labels