Advertisement

BIN 353700 – JCB/RuPay Debit Card (India)

353700 is the BIN of a JCB/RuPay debit card, registered in India. Below: card format, test numbers and related BINs.

Advertisement
353700JCB/RuPay Debit
Network
JCB/RuPay
Type
Debit
Level
–
Issuer
Not in the data
Country
India IN
Card length
16 digits (up to 19)
Security code
3-digit CAV2 on the back
8-digit range
35370000–35370099

Generate test numbers with this BIN Open in BIN generator

Sample test numbers for BIN 353700 Test data

NumberExpiryCVVCopy
3537 0028 4111 924306/2031270
3537 0032 1271 720104/2030133
3537 0096 6662 335711/2029951

Luhn-valid numbers built from this BIN for testing forms and BIN rules. No bank issued them: they belong to no account and every real payment with them is declined.

Advertisement

About BIN 353700

BIN 353700 is listed as a JCB/RuPay debit card in India. Debit cards draw money directly from the cardholder's bank account, so checkouts and gateways often treat them differently from credit cards (fees, holds, recurring billing).

The dataset does not name the issuing bank for this range. That is common for ranges that are new, private or used by processors on behalf of several banks.

India has 12,256 BINs in the dataset; among the 8,163 that name an issuer, the main networks are RuPay (54%), Visa (22%), Mastercard (13%), and 78% are debit. See the India BIN list or the India card generator.

JCB/RuPay number format for BIN 353700

Starts with353700 (the BIN). First digit 3: travel and entertainment
Length16 digits (up to 19)
Security code3-digit CAV2 on the back
Check digitThe last digit, calculated with the Luhn algorithm
Printed as3537 0028 4111 9243

A checkout that receives a number starting with 353700 should detect JCB/RuPay, expect 16 digits and ask for a 3-digit security code. The generator creates as many numbers with this BIN as you need, with expiry dates and CVVs, as CSV, JSON or XML.

Advertisement

Nearby BINs

The BINs closest to 353700 in our data. Neighbouring ranges often belong to the same bank, but not always — each range is assigned separately.

Frequently asked questions

Which bank issued BIN 353700?

The dataset does not name an issuer for BIN 353700, only the country (India). The network is JCB/RuPay.

Is 353700 a debit or a credit card BIN?

It is recorded as debit. Debit cards draw money directly from the cardholder's bank account, so checkouts and gateways often treat them differently from credit cards (fees, holds, recurring billing).

How many digits does a card with BIN 353700 have?

JCB/RuPay card numbers have 16 digits (up to 19), and the security code is a 3-digit CAV2 on the back. The first six digits are the BIN, the last digit is the Luhn check digit, and the digits in between identify the account.

Can I generate test card numbers with BIN 353700?

Yes. Open the generator with this BIN to create Luhn-valid numbers with expiry dates and CVVs for testing forms, validation and BIN-based rules. They are test data: not issued by any bank, linked to no account and declined by real payment systems.

Does a BIN tell me whether a card is valid?

No. A BIN describes a range of card numbers — network, issuer, country and product — not a particular card. Whether a card exists or can be charged is known only to the issuing bank. To check the format of a full number (length and check digit), use the card validator.

A BIN identifies the card network and the issuing institution only. It reveals nothing about an individual card, cardholder or account, and it cannot show whether a card exists or can be charged. Test numbers generated from a BIN are for development and QA only and are declined by every real payment system.

BIN checker · BIN list by country · BIN generator · Free BIN API

BIN data: bin-list-data by Venelin Kochev (a lite version of binlookup.io), licensed under CC BY 4.0. Changes made by Fakecreditcard: issuer, brand and country names re-cased and standardized, spelling variants of the same issuer merged, malformed phone numbers and web addresses removed.

Advertisement