Charts

1. Payment Collection Flowchart Using Pagadito

The following is a flowchart detailing the processes carried out to successfully collect payment from a Buyer User by Pagadito Merchant through Pagadito.

 

 

1.1 Commerce Check Out Screen

Pagadito Merchant displays the "Check Out" screen to the Buyer User, detailing his purchase. It communicates with the WSPG to register the transaction.

1.2 WSPG records the transaction

WSPG oversees recording the transaction requested by Pagadito Merchant and passes the control to Pagadito.

1.3 User Login

Pagadito shows the Buyer User a screen with the details of the purchase and a Login chart.

1.4 User Authorizes Payment

The user enters his/her email and password to authorize the charge. If the user does not have enough Pagadito funds, he/she is asked to select a card to charge it.

1.5 Pagadito debits Buyer's Account/Card

Pagadito makes the charge to the Pagadito account or card of the Buyer User.

1.6 credits Merchant’s Account

Pagadito makes the credit to Pagadito Merchant's account (Funds receivable from Pagadito Merchant are effective five business days after payment date). Then redirects the Buyer User to Pagadito Merchant's website.

1.7 Merchant Finalizes Transaction with User

Pagadito Merchant finalizes the payment process, showing a finalization screen to the Buyer User.

Home

2. Collection Sequence Using Pagadito

The following is a sequence diagram detailing the mechanics required to achieve a successful collection process from the Pagadito Merchant platform.

 

 

2.1 User Buyer >> Selects "Buy"

The Buyer User enters the Pagadito Merchant site and selects "Buy" in his shopping cart.

2.2 Pagadito Merchant >> connect()

Pagadito Merchant calls the connect() operation to request a token; sending uid and wsk.

2.3 WSPG >> return

The WSPG returns the Response Structure, with the token in the "value" index.

2.4 Pagadito Merchant >> exec_trans()

Pagadito Merchant calls the operation exec_trans() to register the operation and obtain the url where the payment will be made; sending token, amount, ern, and details.

2.5 WSPG >> return

The WSPG returns the Response Structure, with the url in the index "value".

2.6 Pagadito Merchant >> Redirects

Pagadito Merchant redirects the Buyer User to the url returned by the WSPG, where the payment will be made.

2.7 Pagadito >> "Confirmation of Purchase" Screen

Pagadito shows the "Purchase Confirmation" screen where the details, prices and total of the purchase are listed. In addition, the Buyer User is asked for his/her email and password.

2.8 User Buyer >> Enter email and password

The Buyer User enters his email and password to validate his account and confirm payment.

2.9 Pagadito >> Applies the charge and redirects to the Return URL

Pagadito processes the payment, charges the Buyer User, and credits the Pagadito Merchant's account (Funds to be received from Pagadito Merchant are effective 5 (five) business days after the payment). Pagadito confirms the payment and redirects the Buyer User to the Pagadito Merchant Return URL, previously formatted to include the transaction token.

2.10 Pagadito Merchant >> connect()

Pagadito Merchant calls the connect() operation to request a token; sending uid and wsk.

2.11 WSPG >> return

The WSPG returns the Response Structure, with the token in the index "value".

2.12 Pagadito Merchant >> get_status()

Pagadito Merchant calls the get_status() operation to request the status of the transaction, sending a token and token_trans. The token_trans is the token received in the Return URL as a GET variable.

2.13 WSPG >> return

The WSPG returns the Response Structure, with the transaction status in the "value" index and the transaction ID in the "detail" index.

2.14 Pagadito Merchant >> Completion screen

Pagadito Merchant displays a purchase completion screen to the Buyer User.

Home