IIN/BIN Validations on Tokens
API to fetch card properties using token IIN.
Watch Out
- As per RBI guidelines, businesses and payment acquirers are allowed to save the last 4 card digits and the Bank Identification Number (BIN) only.
- As per current interpretation, businesses and Payment Acquirer are not allowed to save the Issuer Identification Number (IIN) of the card.*
*Razorpay is seeking clarification on this from the industry and RBI.
A token is an alias or surrogate value for the actual card number. Whenever the network tokenises a card, the token generated will be a numeric value with the same length as the actual card number.
When a card is tokenised, the first 6 digits or the IIN of the card gets updated. The new IIN for the card is referred to as token IIN.
Use the following API to fetch the properties of the card using token IIN.
token_iin
mandatory
integer
The token IIN.
iin
string
The Issuer Identification Number (IIN). The first 6 digits of credit or debit card number. For example, 411111.
entity
string
The name of the entity. Here, it is iin.
network
string
The card network for the given IIN. Possible values:
Visa
RuPay
MasterCard
American Express
Diners Club
Bajaj Finserv
Maestro
JCB
Union Pay
Unknown
type
string
The card type for the given IIN. The card payment pricing may differ based on the card type. Possible values:
credit
debit
prepaid
unknown
sub_type
string
The card sub-type for the given IIN. The card payment pricing may differ based on the card sub-type. Possible values:
consumer
business
unknown
international
boolean
Determines whether the card is international (issued outside India) or domestic. Possible values:
true
: Card issued outside India.false
: Card issued within India.
issuer_code
string
The 4-character issuer code unique to each issuing bank in India. For example, SBIN.
issuer_name
string
The name of the issuing bank. Available for cards issued in India only. For example, State Bank of India.
issuer_logo
string
URL pointing to the logo of the issuing bank hosted on the Razorpay server.
emi
json object
A JSON object which provides information about the applicability of EMI on the IIN.
recurring
json object
A JSON object which provides information about the applicability of recurring payments on the IIN.
authentication_types
array
Array which lists the possible authentication types for which the IIN is eligible. Possible values:
type
: 3ds: Indicates that the card IIN supports normal 3ds payments.type
: otp: Indicates that the card IIN supports native OTP payments. Native OTP gives you flexibility to accept the OTP entered by the cardholder on your screen.
Was this page helpful?
ON THIS PAGE