1. Card BIN File
Reconciliation Files & Specifications
  • Overview
  • Reconciliation Files
    • File-01 Activity_Detail Online Transaction Detail File
    • File-02 Settlement_Detail Settlement Transaction Detail File
    • File-03 Miscellaneous_Detail Manual Settlement Transaction Detail File
    • File-04 PSP_Reconciliation_Detail PSP Settlement Reconciliation Transaction Detail File
    • File-05 PSP_Miscellaneous_Detail PSP Settlement Exception and Special Transaction Detail File
    • File-06 Interchange_Scheme_Fee_Detail Interchange and Scheme Fee Detail File
    • File-07 PSP_Interchange_Scheme_Fee_Detail PSP Interchange and Scheme Fee Detail File
    • File-08 Network_Token_Cryptogram_Detail Network Token Cryptogram Detail File
  • Card BIN File
    • BIN File
  1. Card BIN File

BIN File

Overview#

In addition to transaction detail reports, the Evo Payment clearing and settlement system also provides a table file showing the corresponding card BIN information, for customers to query card brand, card number range, issuing bank, and other card BIN attributes.
Note :
Only Acquirer-level configuration is supported; Group, Merchant, and Store levels are not provided;
The file is generated monthly and is not generated with the daily cutoff cycle;
After the large-file splitting feature is enabled, the file name will include a BatchNum (001–999) suffix;
After the PSP dimension report feature is enabled, the file name will include a PSPName suffix; when both features are enabled, PSPName precedes BatchNum.

File location and naming rules#

File levels and file codes#

The Card BIN File supports only the Acquirer level and does not distinguish other dimensions.
File levelFile codeReport name template
Acquirer levelBIN-FileBIN_File_{Version No}_{Acquirer ID}_YYYYMMDD

File name field descriptions#

Each field is joined with an underscore (_), and the field meanings are as follows:
FieldDescription
Fixed valueBIN_File
Version numberThe first character is the file identifier: P for the production environment and T for the test environment; the last three characters are a numeric number, from 001 to a maximum of 999 (new versions are compatible with old versions)
Acquirer IDThe customer's Acquirer identifier
DateYYYYMMDD, the report generation date
PSP name (optional)Added when the Acquirer file is configured with the PSP Dimension Report feature, using the PSP name
Batch number (optional)Added when the Acquirer file is configured with the Batch Generate Threshold feature, with a value range of 001–999

File name examples#

Production environment (Acquirer level)
BIN_File_P001_88888888_20240430.csv.zip
Test environment (Acquirer level)
BIN_File_T001_88888888_20240430.csv.zip
With batch number
BIN_File_{Version No}_{Acquirer ID}_YYYYMMDD_(BatchNum)
With PSP name
BIN_File_{Version No}_{Acquirer ID}_YYYYMMDD_(PSPName)
When PSP name and batch number are used together
BIN_File_{Version No}_{Acquirer ID}_YYYYMMDD_(PSPName)_(BatchNum)

Retrieval methods#

MethodDescription
Platform downloadEvo Payment G2 service platform
SFTP transferSee the SFTP path and login below
API retrievalPull through the API

SFTP path and login#

ItemDescription
SFTP modeEvo Payment is the SFTP Server
Default directory/in/{YYYYMMDD}
Login methodPublic/private key
Transfer completion markerEmpty TXT file with the same-name .ok suffix (e.g. BIN_File_P001_88888888_20240430.csv.ok)
Important : Before pulling and parsing the Card BIN File, the client should first check whether the same-name .ok file exists to confirm that Evo Payment has completed the file transfer.

Report structure#

Basic file properties#

PropertyValue
File formatCSV, delivered compressed as .zip
File encodingNot defined in the specification; observed without BOM
Line breakNot defined in the specification; observed as \n (0x0A)
Field delimiterNot defined in the specification; observed as comma ,, with fields not uniformly enclosed in double quotes
File content end markerNot defined in the specification; observed with ***END*** as the last line

File generation time#

Generation cycle: monthly file, generated on the 2nd of each month
Generation time: on the 2nd of each month, 10:00–12:00 AM (Evo Payment node system time)

File data elements#

This section defines the data elements of the BIN File. All of the following 14 fields appear in the Acquirer-level file.
No.Field nameDescription
1cardBrandCard brand
2issAccRangeLowMinimum card number range value
3issAccRangeHighMaximum card number range value
4cardLengthCard number length
5countryCodeCountry code
6currencyCurrency
7creditFlagDebit/credit indicator
8productIDCard product ID
9productTypeCard product type
10issuerIICIssuer code
11issuerNameIssuer name
12createTimeCreation time (time when the Card BIN File is updated)
13dccFlagDCC indicator
143dsFlag3DS indicator

Samples#

cardBrandissAccRangeLowissAccRangeHighcardLengthcountryCodecurrencycreditFlagProductIDproductTypeissuerIICissuerNamecreateTimedccFlag3dsFlag
MCC5102464090000000000510246410999999999916IRLTWDCMBICommercial00000026414CHASE PAYMENTECH EUROPE LIMITE2026-04-18T07:35:25ZY
VIS4999760180000000000499976018999999999916USAUSDCAConsumer499976NEW PEOPLES BANK, INC.2026-07-28T07:31:48ZY
Previous
File-08 Network_Token_Cryptogram_Detail Network Token Cryptogram Detail File
Built with