---
title: "Testing 3DS"
description: "Learn how to test 3D Secure 2.0 flows in KOMOJU using test card numbers that simulate various authentication outcomes."
url: "https://docs.priv.staging.komoju-dev.tools/en/docs/development/testing-3ds"
source_url: "https://docs.priv.staging.komoju-dev.tools/en/docs/development/testing-3ds.md"
language: en
last_modified: "2026-08-04"
---

3D Secure 2.0 is a protocol designed to help prevent credit card fraud by providing an additional means of customer authentication. Please see [https://ja.komoju.com/blog/news/3d-secure/](https://ja.komoju.com/blog/news/3d-secure/) (Japanese only) for more information.

Many regulations and rules require merchants to support 3D Secure.

KOMOJU supports 3D Secure 2.0 out of the box for our primary integration methods ([Hosted Page](https://docs.priv.staging.komoju-dev.tools/en/docs/integration-guides/web-integrations/introduction-to-hosted-page.md), [Hosted Fields](https://docs.priv.staging.komoju-dev.tools/en/docs/integration-guides/introduction-to-hosted-fields.md)). However for merchants who [create payments directly](https://docs.priv.staging.komoju-dev.tools/en/docs/integration-guides/payments-api-overview.md), some extra work is required in order to support 3DS.

You can read more about how to test 3D Secure through API in [3D Secure Without a Session](https://docs.priv.staging.komoju-dev.tools/en/docs/integration-guides/payments-api-3ds.md).

# Test Cards

You can use the following credit card information to test the 3D Secure flow in **test** mode. Name and CVV can be anything, and expiration date can be any future date.

To improve the reliability and performance of our payment environment, KOMOJU is upgrading its underlying 3D Secure (3DS) infrastructure vendor. **From 2026/Sep/01**, **please use the new test cards to test 3DS.**

## Authentication success (3DS frictionless)

These card numbers can be used to complete a transaction without an authentication challenge.

| Card Number | Type |
| --- | --- |
| 4100000000000100 | Visa |
| 5100000000000107 | Mastercard |
| 3528000000000106 | JCB |

### From 2026/Sep/01, please use the following cards

| Card Number | Type |
| --- | --- |
| 4000000000000010 | Visa |
| 5200000000001021 | Mastercard |
| 3528000000000056 | JCB |
| 340000000001023 | Amex |
| 6029690000000002 | UnionPay |
| 36000000000008 | Diners/Discover |

## Authentication with challenge (3DS friction)

These card numbers can be used to test transactions with a password challenge. Please use `123456` to pass the challenge.

| Card Number | Type |
| --- | --- |
| 4100000000005000 | Visa |
| 5100000000005007 | Mastercard |
| 3528000000005006 | JCB |

### From 2026/Sep/01, please use the following cards

You can use `1234` to pass the challenge or `1111` to fail the challenge.

| Card Number | Type |
| --- | --- |
| 4000000000000028 | Visa |
| 5100000000000010 | Mastercard |
| 3528000000000064 | JCB |
| 6029690000000028 | UnionPay |
| 36000000000248 | Diners/Discover |

## Authentication rejected (3DS frictionless failure)

These card numbers can be used to test a rejected authentication without a challenge.

| Card Number | Type |
| --- | --- |
| 4100000000500000 | Visa |
| 5100000000500007 | Mastercard |
| 3528000000500006 | JCB |

### From 2026/Sep/01, please use the following cards

| Card Number | Type |
| --- | --- |
| 340000000001031 | Amex |
| 4000000000000044 | Visa |
| 5100000000000008 | Mastercard |
| 3528000000000122 | JCB |
| 6029690000000044 | UnionPay |
| 36000001000122 | Diners/Discover |

## Authentication failed on challenge

These card numbers can be used to test transactions with a challenge password that will fail. Please use any number to simulate a failed authentication.

| Card Number | Type |
| --- | --- |
| 4100000000300005 | Visa |
| 5100000000300002 | Mastercard |
| 3528000000300001 | JCB |

**From 2026/Sep/01**, use the test cards in “Authentication with challenge” section and use `1111` to fail the challenge.