Skip to content

Payment Webservice, Service for payment from one user to other user. There is not include parts that use bank api to redeem money from this service or deposite money to this service.

Notifications You must be signed in to change notification settings

ppanya/KUPaymentService

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

39 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

KUPaymentService

Description

Payment Webservice, Service for payment from one user to other user. There are two sides of user first is customer and merchant. User want to pay money to merchant by kupaypal. After check out payment from merchant, website will direct to kupaypal login. User have to have kupaypal id before login then kupaypal will show the order id merchant name total amount and time of purchased, user will choose accepted or decline for confirm that payment. Then kupaypal will redirect user to merchant website.
There is not include parts that use bank api to redeem money from this service or deposite money to this service.

Stakeholder

* Merchant * Customer * Payment System Admin
note:I consider that merchant and customer is a different user type. But I still consider about customer to customer transaction, should this service support it or not.

Specific Term

* Payment - a payment for goods/services that merchant send to the recipient (customer). * Problem - a problem that broke an agreement of two stakeholders which is merchant and customer.
note: It should have a standard for Problem term but it seem hard to set it up.

Use Cases

1. Send a payment

When client get price, order id, merchant id, and date time, it can POST payment to webservice. * Primary Actor: Merchant * Scope: Payment System * Level: Very High * Story: Merchant send a payment to customer.

Scenario Create payment

Main Success Scenario and steps

1. User choose product 2. User proceed and check out 3. Merchant website will send order id, merchant id, total amount, and date time for create payment to webservice Create Payment

Extensions

2a. Total amount is minus value .1 Merchant have to send order id, merchant id, total amount, and date time again

Trigger

User selects to pay by "Ku paypal"

Guarantee

User can create payment

2. Accept a payment (funds transferred)

When customer sure for transfer money, they can PUT payment to accept the payment. * Primary Actor: Customer * Scope: Payment System * Level: Very High * Story: Customer approve a payment then funds transferred to merchant. (payment completed)

Scenario Accept a payment

Main Success Scenario and steps

1. User will see all of detail of payment 2. User accept the payment

Create Account

Precondition

User is logged in to ku paypal User proceed or check out from merchant

Guarantee

User pay the payment

3. Reverse/chargeback a payment

When customer see payment description, price/merchant is not correct, Customer will decline this payment. * Primary Actor: Customer * Scope: Payment System * Level: Low * Story: Some problem occured. Customers want to refund their funds back. They go and try to reverse/rollback a payment.

Scenario Charge back

Main Success Scenario and steps

1. User full fill form for reverse paymnet from merchant 2. Merchant tell webservice to charge back 3. User get charge back

Extensions

2 Admin of website do not permit to charge back

Trigger

User selects to pay by "Reverse"

Precondition

User paid payment already

Guarantee

User can get charge back from payment

4. User registration

When customer can not login to the system. * Primary Actor: Customer * Scope: Account management * Level: High * Story: Customer want to become a member of the system.

Scenario Register

Main Success Scenario and steps

1. User types a user name of his or her choice 2. User types a password 3. User retypes the password 4. User types his or her first name 5. User types his or her last name 6. User types his or her Address, Date of birth (Optional) 7. User types his or her credit card number. Create Account

Extensions

1a. User name is already in use .1 User is requested to select another user name and password 3a. The two passwords are different .1 User is requested to retype (twice) his/her password

Trigger

User selects the "Sign Up" link

Precondition

User is not logged in

Guarantee

User becomes a registeredplayer

5. User Log In

When customer want to accessto the system. * Primary Actor: Customer * Scope: Account management * Level: High * Story: Customer want to login to the system.

Scenario Login User

Main Sucess scenario

1. User types his/her user name 2. User types his/her password Login

Extensions

2a. User provides invalid login parameter (see Login Failed)

Trigger

User selects the "Login" link

Precondition

User does not login yet

Guarantee

The user can see his/her own information in paypal

6. User Log In Failed

When customer want to accessto the system. * Primary Actor: Customer * Scope: Account management * Level: High * Story: Customer want to login to the system.

Scenario Login failed

Login Failed

Precondition

-The user provides invalid login parameters Precondition should be identical with the condition of the extension point

Main success scenario

1.System redirects the User to the Login page 2.System informs the User that he/she typed a non-registered user name

Login without Registration

Precondition

-The User typed a non-registered user name Precondition should refine the precondition of Login Failed

Main success scenario

1. System redirects the User to the Login page 2. System informs the User that he/she typed a non-registered user name

Functional Requirement

1. Transaction history 2. Current balance for each user. 3. (Extra) Support multiple currency and multiple language

API Specification

[API Specification at github's wiki](https://github.com/maixezer/KUPaymentService/wiki/API-Specification)

Reference

This part is reference of my research through paypal system. I found this [link](https://www.paypal.com/cy/webapps/mpp/ua/servicedescription-full) is really helpful.

Developer

* Atit Lelasuksan 5510546201 * Parinthorn Panya 5510546085 * Wat Wattanagaroon 5510546140

About

Payment Webservice, Service for payment from one user to other user. There is not include parts that use bank api to redeem money from this service or deposite money to this service.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages