10.
Install the card-issuer root certificate
in the MPI.
11.
Install the merchant ID and the merchant password
(obtained from the acquirer) in the MPI.
12.
Change the code
to enable the MPI software to point to the production card-issuer directory
server.
5.5.5 Credit Card Use Process
Figure 5.4 illustrates the essentials of the payment process.
76
Manage Software Testing
There is a bottleneck problem when transactions are to be authorized which can be resolved by simply
advising the user that the authorization details will be advised along with any download codes, batching
the transactions, and forwarding them to the credit card issuer at a low-traffic moment. Downloaded
(soft) transactions cannot use this approach since the whole point of such a transaction is to allow the
user download access fast. In practice an email advising the user that the download code will be sent
within 30 minutes is usually satisfactory.
FIGURE 5.4
Payment processing
Start
Card details
held?
User advised Details OK?
Details checked No
No User advised
Transaction
ends No
No
Card charged
No
Yes
User advised
weekly
Void transaction
raised
Payment data
sent to
application server
Yes
Yes
Yes Yes
User decides to
purchase good(s)
Authorization
process
Authorization
code issued
Download code
sent to user
User enters credit
card or bank data
Authorization
OK?
User
cancels
User advised of
authorization
Download
authorized
Reconciliation Settlement Funds transferred Stop
Cancellation
confirmation sent User advised Yes User cancels
No Shipping
authorized Shipped? Logistics
Testing and the Web
77
Note that other methods are used:
??? PayPal (www.
Pages:
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221