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 3 Next »

1. Use case name (Required)

"Organization Account" Payment Method

2. Keywords (Required)

custom, payment method, department shortcode, department account, company account, organization’s account

3. Actors + description (Required)

  • As the admin, I want to allow customer to take payment using “Organization Account” payment method

4. Pre-conditions

The company’s account configuration must be enabled in Magento Backend

5. Main flow (Required)

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

  1. The cashier selects “Organization Account” as the payment method when checking out for the customer. The POS system processes and displays the “Terms & Conditions” of the payment method as configured in Magento backend.

  2. The cashier informs the customers of the T&C of the “Organization Account” payment method and selects “I agree to these terms” on the behalf of the customer. The POS system processes and displays “Accept Payment” page with preset payment amount equal to the total value of the order since customer is not able to make partial payment or split payment when choosing to pay with “Organization Account” payment method.

  3. The cashier inputs the Organization Account provided by the customer into the “Short Code” as suggested by the POS system and selects “Accept $”. The POS system validates the Organization Account and account balance through API calling, and automatically emails the receipt to the customer, as also record the transaction.

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%

Organization Account is not available on POS as standard payment method

  • No labels