Project

General

Profile

Specification » History » Version 14

chin-yeh, 02/09/2012 10:18 AM

1 2 chin-yeh
{{toc}}
2
3 1 chin-yeh
h1. Specification
4 2 chin-yeh
5 5 chin-yeh
The chosen integration method is *Customer Link*. The consumer enters payment information on GlobalCollect's hosted payment pages and GlobalCollect will forward the payment result to the merchant through *Payment Status Communicator* (PSC).
6
7 6 chin-yeh
h2. Introduction
8 1 chin-yeh
9 6 chin-yeh
*Payment Flow*:
10 1 chin-yeh
!flow_diagram.jpg!
11 6 chin-yeh
12
13
h3. Java Package Name
14
15
Package name:
16
<pre>
17
my.com.eCosway.globalcollect
18
</pre>
19
20
h3. Table(s) used
21
22
<pre>
23
GLOBALCOLLECT_INTERFACE
24
</pre>
25
26
h2. Configuration
27
28
The GlobalCollect's *Customer Link* requires the merchant to provide the following URL:
29
* *Return URL* - A link to be displayed on GlobalCollect's payment pages. 
30
* *PSC URL* - GlobalCollect sends the payment information to this URL after the consumer has completed a payment attempt successfully.
31
32
h3. globalcollect.properties
33
34
This properties file is located at:
35
<pre>
36
resources/properties/uk/globalcollect.properties
37
</pre>
38 11 chin-yeh
> The properties file for development environment:
39
> <pre>resources/properties/uk/globalcollect-dev.properties</pre>
40 14 chin-yeh
> *important note:* rename to <code>globalcollect.properties</code>
41 6 chin-yeh
42
*Properties Description*:
43
|_.Property Name|_.Description|
44
|cl.url|The API URL for Customer Link|
45
|merchant.id|The merchant ID (provided by GlobalCollect)|
46
|merchant.ip|The merchant's public IP address|
47
|order.api.version|The API version of INSERT_ORDER|
48
|order.status.api.version|The API version of GET_ORDERSTATUS|
49
|currency.code|3 letter currency code (ISO-4217)|
50
|country.code|2 letter country code|
51
|language.code|2 letter language code (ISO-639)|
52
53
h2. Programming
54
55
This section contains 3 parts:
56
* Generate redirect URL - describes how to generate the redirect URL
57
* Back URL - describes how to handle the returned consumer
58
* PSC URL - describes how to capture the payment information
59
60 9 chin-yeh
h3. Required libraries
61
62
Apache HttpClient:
63
* httpclient-4.0.3.jar 
64
* httpcore-4.0.1.jar
65
* httpmime-4.0.3.jar
66
67
Download link:  http://hc.apache.org/downloads.cgi
68
69 6 chin-yeh
h3. Generate redirect URL
70
71 12 chin-yeh
The generated URL will be used to redirect the consumer to GlobalCollect's payment pages. 
72 6 chin-yeh
73
*Step-by-Step:*
74
# Prepare  the following parameters:
75
** *connection* - an established database connection
76
** *orderId* - the unique order ID, 20 alphanumeric characters
77
** *amount* - the order amount in cents, and integer values only
78
# Pass the above parameters to the following interface:
79
<pre>
80
String redirectUrl = PaymentUtils.genRedirectPaymentUrl(connection, orderId, amount);
81
</pre>
82
# Insert the order ID information into session.
83 1 chin-yeh
# Redirect the consumer to the generated URL using *JavaScript* or *HttpServletResponse.sendRedirect*. 
84 12 chin-yeh
85
h3. Generate redirect URL with address info and email
86
87
The generated URL URL will be used to redirect the consumer to GlobalCollect's payment pages. 
88
89
*Step-by-Step:*
90
# Prepare  the following parameters:
91 13 chin-yeh
** *transactionType* - the transaction type, e.g. PURCHASE, REGISTRATION
92 12 chin-yeh
** *connection* - an established database connection
93
** *orderId* - the unique order ID, 20 alphanumeric characters
94
** *amount* - the order amount in cents, and integer values only
95
** *email* - the email of the customer
96
** *profileAddress* - the address of the customer
97
** *shippingAddress* - the shipping address of the customer
98
# Pass the above parameters to the following interface:
99 1 chin-yeh
<pre>
100 13 chin-yeh
String redirectUrl = PaymentUtils.genRedirectPaymentUrl(transactionType, connection, orderId, amount, email, profileAddress, shippingAddress);
101 12 chin-yeh
</pre>
102
# Insert the order ID information into session.
103
# Redirect the consumer to the generated URL using *JavaScript* or *HttpServletResponse.sendRedirect*. 
104
105
106 6 chin-yeh
107
h3. Back URL
108
109
The back URL acts as receipt URL also. This is where the consumer will be redirected to after completed the payment.
110
111 8 chin-yeh
As GlobalCollect will not forward payment information to the URL, one has to obtain the order details via the active session. The following guide assumes the order ID is stored in the session.
112 6 chin-yeh
113
*Step-by-Step:*
114
# Prepare the following parameters:
115
** *connection* - an established database connection
116
** *orderId* - the unique order ID, 20 alphanumeric characters
117
# Pass the above parameters to the following interface:
118
<pre>
119
String orderId = (String) session.getAttribute("test_ord_id");
120
PaymentUtils.persistPaymentStatusForReceipt(connection, orderId);
121 1 chin-yeh
</pre>
122 8 chin-yeh
# And then, one can obtain the payment status in the interface table (see [[Specification#Table-used|Table Name]]);
123 6 chin-yeh
124
h3. PSC URL
125
126
For every payment transaction with the status 500 and above, GlobalCollect will post the payment information to the PSC URL.
127
128
*Step-by-Step*:
129
# Prepare the following parameters:
130
** *connection* - an established database connection
131
** *request* - the HttpServletRequest object
132
# Pass the above parameters to:
133
<pre>
134
PaymentUtils.persistPaymentStatusForPsc(dataBean.getConnection(), request);
135
</pre>
136
# *[Important]* The PSC must not contains any HTML element except a *'OK'* string e.g., 
137
<pre>
138
out.print("OK");
139 1 chin-yeh
</pre>
140 6 chin-yeh
 
141 8 chin-yeh
h2. FAQ
142 7 chin-yeh
143
*PSC:*
144
* GlobalCollect post the payment result within 2 minutes after completed payment
145
* The PSC URL must be a HTTPS URL
146
* Only those payment result with status 500 or above will be posted to PSC URL.
147 10 chin-yeh
* The number of retry attempt is 10. If reached the maximum retry attempt, the PSC posting will be disabled.
148
* The retry interval is 2-minutes for the first attempt and 1-minute for the subsequence attempts.