-
Notifications
You must be signed in to change notification settings - Fork 0
Use Case
b5510546140 edited this page Dec 15, 2014
·
2 revisions
After customer decide to check out via ku paypal, client/merchant's website create a json data which contain order id, merchant email and total price to POST in our service.
* Primary Actor: Merchant
* Scope: Payment System
* Level: Very High
* Story: Merchant create a payment in service's system.
1. Customer choose product from Merchant's website.
2. Customer place order and check out.
3. Merchant's website will send order id, merchant email, total amount to create payment in our service.
Merchant email is exist in kupaypal system.(merchant have an account to validate a payment and get his/her money.)
1. Total amount has negative value
2. Merchant have to resend his/her data to our service.
Customer selects to checkout via "Ku paypal"
Merchant create a payment so customer can accept it.
After merchant's website create a payment. Customer want to pay that payment, customer just GET a acception path to accept a payment.
* Primary Actor: Customer
* Scope: Payment System
* Level: Very High
* Story: Customer accept a payment, service system hold his/her balance to wait merchant come and validate a payment.
1. Customer retrieve a payment information from merchant's website e.g. list of item, total price.
2. Merchant's website redirect to payment acception page.
3. Customer accept a payment.
Customer have an account in kupaypal system.
Customer accept a payment.
After customer accept a payment, merchant come to kupaypal system and validate a payment to retrieve money.
* Primary Actor: Merchant
* Scope: Payment System
* Level: Very High
* Story: Merchant validate a payment and retrieve money to account.
1. Merchant go to validate path (/payment/{id}/validate) to get validation page.
2. Merchant validate a payment.
Customer already accept a payment.
Merchant validate a payment.
If customer or merchant found that payment information is not correct or have a problem, they want to cancel/reverse this payment.
* Primary Actor: Customer or Merchant
* Scope: Payment System
* Level: Low
* Story: Some problem occured in a payment. Customer/merchant want to reverse/cancel a payment. They go and try to reverse/rollback a payment.
1. Customer fullfill a cancel/reverse form in merchant's website.
2. Merchant GET cancel path to cancel/reverse a payment.
3. Customer and Merchant get chargeback amount.
Admin of website do not permit to charge back
Customer selects to cancel/reverse a payment. (depend on what merchant's website provided.)
Payment already created.
Customer can get his/her money back.
User want to pay via this service, they need to register.
* Primary Actor: Customer
* Scope: Account Management
* Level: High
* Story: User want to become a member of the system.
1. User provide email, password, first name, last name and address in registration form.
2. User selects "register".
1a. E-mail is already in use
.1 User need to change his/her email.
3a. The two passwords are different(use for password validation)
.1 User retype his/her password
User selects the "Sign Up".
User is not logged in.
User becomes a registered user.
Customer want to access the system. Customer can retrieve his/her profile and balance.
* Primary Actor: Customer
* Scope: Account management
* Level: High
* Story: Customer want to login to the system.
1. User provide his/her email and password.
2. User select "Sign In".
2a. User provides invalid login parameter
(see Login Failed)
User selects the "Sign In".
User access resource that need authentication.
User does not login yet.
User can see his/her own information in paypal.
When customer want to accessto the system.
* Primary Actor: Customer
* Scope: Account management
* Level: High
* Story: Customer want to login to the system.
- The user provides invalid login parameters
Precondition should be identical with the condition of the extension point
1.System redirects the User to the Login page
2.System informs the User that he/she typed a non-registered user name
- The User typed a non-registered user name
-
Precondition should refine the precondition of Login Failed
1. System redirects the User to the Login page
2. System informs the User that he/she typed a non-registered user name
1. Transaction history
2. Current balance for each user.
3. (Extra) Support multiple currency and multiple language