Enrollment Request
In order to start MPI Compliance Test, Vendor must click
here and enroll for testing at first. The following information must
be provided during enrollment:
| Login Information | Tester ID | A unique value to identify Tester |
| Password | A credential to be used for login | |
| Tester Information | Company Name | Name of a company whose product is to be tested *This will be posted to "J/Secure Compliant Product List" |
| Address | Address of the company | |
| Country | ||
| ZIP/Postal Code | ||
| Name of Authorized Representative | Name of the person who is responsible for the testing | |
| Title of Authorized Representative | Title of the person above | |
| E-Mail address to be posed to "J/Secure Compliant Product List" | ||
| Contact Information | Name | Name of a person who will be a primary point of contact |
| Phone Number | Phone number of the contact person. Please specify the country code. | |
| Fax Number | Fax number of the contact person, if applicable. Please specify the country code. | |
| E-Mail address of the contact person. All information needed for testing will be sent to this address. | ||
| Product Information | Product Name and Version | Name of the product and its version to be tested *This will be posted to "J/Secure Compliant Product List". Please enter the same information as in Visa compliance notice, if nothing has been changed. |
| 3-D Secure Protocol Version | The version of 3-D Secure protocol which the tested MPI supports | |
| 3-D Secure Specification with which this product is compliant | The errata which the tested MPI supports | |
| Supported Protocol | The protocol of each payment scheme which the tested MPI supports | |
| Cache of Directory Information | Whether the tested MPI can send CRReq and process the responding CRRes | |
| Merchant Password Encryption | Whether the tested MPI can encrypt Merchant password | |
| Authentication Page Generation | Method supported by the tested MPI to generate an authentication page | |
| JavaScript for Redirection | Whether the tested MPI uses JavaScript for redirecting PaReq form | |
| PAReq/PARes JavaScript Fallback | Whether the tested MPI supports fallback when cardholder browser does not support JavaScript. | |
| Visa Compliance | Recognized as 3-D Secure ver.1.0.2 compliant product by VISA | Whether the tested MPI has been recognized as compliant product by VISA |
| Issuance date of Visa compliance notice | Date of a compliance notice issued from Visa | |
| Expiration date of Visa compliance notice | Date of expiration, if specified in Visa compliance notice | |
| Reference Number of Visa compliance notice | A number to uniquely identify the product, if provided by Visa | |
| Testing Information | MPI URL | A fully qualified URL where JSTAT should send the Buy form to the tested MPI. Port information should be included in the URL, if required. |
| Error Return | Whether the tested MPI will be configured to return Error message, when it detects Error in the response from JSTAT or validation error in PARes signature |
After submitting enrollment request through the web site, Vendor must submit a copy of Visa compliance notice to JCB listed below. It can be provided by any method, postal mail, fax, or e-mail.
| Mailing
Address |
J/Secure Test Support Advanced Technologies Department JCB Co., Ltd. 5-1-22 Minami Aoyama, Minato-ku, Tokyo 107-8686 Japan |
| Fax
Number |
81-3-5778-7925 |
| E-Mail
Address |
J_Secure_Test@info.jcb.co.jp |
Upon receiving the enrollment request and a copy of Visa compliance notice from Vendor, JCB will review them and approve the enrollment. JCB will send an email to the contact person specified in the enrollment form to notify that the enrollment has been approved.
Vendor
can use JSTAT for 15 continuous calendar days from the approval, to run
Compliance Test.
*NOTICE*
Vendor can neither login to JSTAT nor run Compliance Test unless the enrollment
request has been approved by JCB.
In order to run Compliance Test, Vendors are required to do the following activities:
-
Provide support for a standard Buy form. JSTAT will send the Buy form (HTML ‘FORM’) to MPI, which should trigger the MPI to send the VEReq to JSTAT. This form contains only ‘pan’ field (HTML ‘INPUT’ field) for most cases, but sometimes includes install and recur elements (install, recur_frequency, recur_endrecur).
-
Create a certificate request and deploy the certificate issued from JSTAT to the server where JSTAT will send the Buy form and to the server where JSTAT will send PARes.
-
Install the JSTAT root certificate and intermediate certificate in your list of trusted certificates.
-
Use the specific values for Merchant.acqBIN, Merchant.merID, and Merchant.password. These values should be configured based on the PAN received in the Buy form.
The detailed information will be provided after the enrollment request has been approved.