This will include:
a. Preparation of all authentication data relevant to the location of the final ???
Buy???
page or
???Check
Out
??? button
b. Presentation of authentication data to the MPI
c. Assessing the answer returned by the MPI after it receives the authentication response.
3. Prepare a
diagram
of the merchant??™s existing or proposed
commerce platform
for the supplier??™s
review.
4.
Review the MPI proposal
with the supplier and identify any other steps required to install the
MPI. Modify the plan.
5.
Unit- and stress-test
the MPI interfacing software.
6.
Unit-test
the MPI interfacing software.
7.
Conduct:
a. System testing
b. Compliance testing
c. Product integration testing on a remote web-testing environment that:
i. Provides the equivalent of all components of the card issuer??™s secure infrastructure
ii. Provides a facility for production readiness testing of
Access Control Server
(ACS) and MPI
component implementations
iii. Verifies that compliant, secure ACS components are integrated at issuer or issuer processor
sites
iv. Verifies that MPI components integrated at a merchant or merchant aggregator sites,
comply with all subject processing requirements, and are production-ready.
8.
Populate
the card issuer database with the merchant data.
9.
Obtain from the acquirer
:
a. The URL of the production directory server
b. The card-issuer root certificate
c. The acquirer-assigned merchant password.
Pages:
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220