Ch 4 - (08/21/2019 Update) Added CardType field, V2 and V3 Versions, and additional info around CB transactions


***Changes made on 08/21/2019 are delineated below in Red.***

Added CardType field, V2 and V3 Versions, and additional info around CB transactions

Connecting to the BIN Intelligence API

Endpoints for Staging and Production


BIN Intelligence Request Field Names

Field

Description

Required

Version

Signature

Base64 encoded SHA256 of SHA512 value that is a hash of timestamp, TransactionId and API Identifier

Y

v2 & v3

Timestamp

Java Epoch time in millis (0:00:00 UTC on 1 January 1970)

Y

v2 & v3

Identifier

api key identifier or Name value

Y

v2 & v3

Algorithm

The hashing algorithm used to generate the Signature value. Valid options include:

  • SHA-256

Y

v2 & v3

TransactionId

Alpha numeric value transactionId. Length 5-55 characters long

Y

v2 & v3

OrgUnitId

Processor/Merchant level OrgUnitId, depending on the endpoint

Y

v2 & v3

Payload

The Payload for the BIN Intelligence request will contain an AccountNumber where the Card BIN to full Card Number will be passed.

Y

v2 & v3
BINsThis field represents the Consumer's Credit Card Number.  The BINs field must contain at a minimum, the Card BIN (first 8 digits) to the full Card Number in the request.Yv2 & v3
AccountNumberThe account number to profile. Must be at least 6 digits.YOnly v3
CardType

Type of cards used for purchase.

Possible Values:

VSA - Visa

MSC - Mastercard

VSD - Visa Delta/Debit (UK)

VSE - Visa Electron

MAE - Maestro (UK, Spain & Austria)

AMX - American Express

DSC - Discover

DIN - Diners

CBLA - Carte Blanche

JCB - JCB

ENR - EnRoute

JAL - JAL

CTB - Carte Bleue

DNK - Dankort

CSI - CartaSi

EAN - Encoded Account Number

UATP - UATP

MAEI - Maestro (International)

CB - Cartes Bancaires

Note : CardType is required to be passed for CB. It is optional for other Card brands.