to the body of this page

JCB

HOME  >  For Business Partners  >  Security  >  J/Secure™ - The E-Commerce Solution -

J/Secure™ - The E-Commerce Solution -

The image of Online shopping with J/Secure

There has been notable growth in the e-commerce sector, which has led to greater demand in increased card security. JCB are continuously working hard to provide their cardmembers with the confidence to use their cards online, by reducing the risk of doing so.

Secure Online Shopping with J/Secure™

J/Secure™ is our answer to improving our cardmembers online transaction security. Currently, payer authentication for online purchases consists of the user inputting their credit card number and expiration date. J/Secure™ adds an additional layer of verification, by identifying the cardmember through a password, or by using further information gathered during the authentication process, such as the cardmember’s device or country.

How J/Secure™1.0 Works

  1. At a J/Secure™1.0 compliant merchant's website, the JCB cardmember enters his/her card number and expiration date in the area for payment information. Next, the MPI* on the merchant's server delivers the information to the corresponding JCB card issuer to verify the cardmember's registration status with the J/Secure™ program.
  2. If the cardmember is enrolled in J/Secure™, a password entry screen appears on the user's PC.
  3. The JCB cardmember enters their password.
  4. The card issuer identifies the password. The result is then delivered to the merchant.
  5. The merchant's system receives the result and if the passwords match, the merchant proceeds with the authorization and sales transactions following the designated procedure.

*MPI(Merchant Server Plug-in):MPI is a plug-in software that must be installed on the merchant’s system in order to offer the J/Secure™ authentication service.

How J/Secure™2.0 Works

  1. On a J/Secure™2.0 compliant merchant’s website or mobile application, the JCB cardmember enters their card number and expiration date in the area for payment information. Next, the 3DS Requestor (who initiates verification on the merchant’s server) delivers the information to the corresponding JCB card issuer to conduct risk-based authentication, without interacting with the cardmember.
  2. If further interaction with the cardmember is not required, authentication is completed, and the result is then delivered to the merchant.
  3. If further interaction with the cardmember is required, the JCB cardmember is required to authenticate themselves using any method that the issuer requires. This could be a one-time password, biometrics or an issuer’s application. The result is then delivered to the merchant.
  4. The merchant’s system receives the result and if the cardmember is authenticated, the merchant proceeds with the authorization and sales transactions following the designated procedure.
Contact Us
JCB, Co., Ltd. Brand Infrastructure & Technologies Department
publications@info.jcb.co.jp
*We apologize in advance if we may not be able to answer some of your queries.

Back to Top

to the body of this page