Effective from October 1, 2025, JCB will require more data fields to meet their minimum requirements for 3D Secure (J/Secure) checks.
Note that at this time, JCB will not assess non-compliance fees or decline transactions that don’t include this data.
We recommend providing the minimum data to improve authentication performance across all supported schemes, not just JCB.
What new data will JCB require?
JCB will require the following data fields in their authentication requests:
| Required field | Example input |
| source.name string <= 254 characters | “John Smith” |
| source.email* string [2..45 characters] | “john.smith@email.com” |
| source.home_phone*: object | |
| source.home_phone.country_code string [1..3] characters | “44” |
| source.home_phone.number string <= 15 characters | “204567895” |
| source.mobile_phone* object | |
| source.mobile_phone.country_code string [1..3] characters | “234” |
| source.mobile_phone.number string <=15 characters | “204567895” |
| source.work_phone* object | |
| Source.work_phone.country_code string [1..3] characters | “234” |
| Source.work_phone.number string <= 15 characters | “204567895” |
The following information is only required if already collected from the cardholder:
| Required field | Example input |
| source.billing_address.city string <= 50 characters | “London” |
| source.billing_address.country string = 2 characters | “GB” |
| source.billing_address.address_line1 string <= 200 characters | “Wenlock Works” |
| source.billing_address.zip string <= 50 characters | “N1 7BQ” |
| source.billing_address.state string <= 3 characters | “ISL” |
* You must provide EITHER the cardholder email address OR at least one phone number (work, home, or mobile).
Checkout.com will collect and submit the browser IP address, screen height, screen width, language, and time zone on your behalf due to your integration.
Please ensure that you continue to send any existing mandatory or optional fields you already provide.