Skip to main content
It’s important to share the details in these reports with your issuer processor to confirm the expected formats — ensuring the reporting setup with each network is configured to Lead’s specifications.
The report Lead requires on a daily basis from Visa is the VSS-115 report. Typically, issuer processors will deliver a suite of reports, of which the VSS-115 report is a single one. Lead can accept any number of reports, as long as the one that contains VSS-115 data is specified according to the below requirements:
VSS-115 ReportDescription
Folder/network-settlement/visa
/network-settlement/interlink (if Interlink is the secondary network)
File FormatVSS-115
Filename Convention{processing_date}_vss_{timestamp}.txt where processing_date is in the format yyyy-mm-dd and represents the date for which the report was generated. If this convention cannot be met, then Lead requires at minimum the filename to contain the date of the report plus a unique identifier for the file format. Please share this convention with the Client Implementations team once finalized.
FrequencyOnce per calendar day

​
Additional Details

Lead also requires the relevant FTSRE ID in order to parse the correct data from the VSS-115 file. The Funds Transfer Settlement Reporting Entity (FTSRE) is the level at which Visa aggregates reports.For example, Issuer Processor A may have three different BIN programs, each at a different partner bank:Issuer Processor A: FTSRE 100
  • Lead Bank Debit/Prapid BINs: FTSRE 101
    • FTSRE 201 (Debit/Prepaid BIN 1)
    • FTSRE 202 (Debit/Prepaid BIN 2)
  • Lead Bank Credit BINs: FTSRE 102
    • FTSRE 203 (Debit/Prepaid BIN 1)
    • FTSRE 204 (Debit/Prepaid BIN 2)
  • Bank partner B: FTSRE 103
  • Bank partner C: FTSRE 104
In the above example, FTSRE 100 will be the sum of FTSRE 101, FTSRE 102, and FTSRE 103. Then, FTSRE 101 is the sum of the FTSREs below it and so on and so forth. For this example, Lead is interested in FTSRE 101 for the debit/prepaid BINs, which represents all of the activity for a given drawdown related to those BINs.However, if one of the BINs is a credit BIN, then the FTSRE must be distinct from the debit/prepaid activity. In the example above, FTSRE 101 represents the debit/prepaid activity, and one set of network settlement accounting entries is run for that. Then, FTSRE 102 represents the credit activity, which triggers a separate set of network settlement accounting entries.
Due to Mastercard’s setup, there are two reports Lead requires in order to settle with the network:
T140 ReportDescription
Folder/network-settlement/mastercard
File formatT140
Filename conventionT140_{YYYY-MM-DD}_mastercard_{X}_{timestamp}.txt X is the clearing cycle, from 1 to 6.
FrequencySix times per calendar day
T461 (SWCHD363 ReportDescription
Folder/network-settlement/mastercard
File FormatT461 (SWCHD363)
Filename ConventionT461_{YYYY-MM-DD}_mastercard_{00X}_{timestamp}.txt
FrequencyTwo times per calendar day

​
Additional Details

Since multiple files are required for Mastercard, Lead waits until all of these files are present before aggregating across them all to get the relevant data points we need. In addition to the presence of three different files required for Lead, there are two more nuances to call out for Mastercard.The first is the notion of Interbank Card Association number (ICA). The ICA is an identifier for which Mastercard uses to aggregate reporting as well as perform drawdowns. This means that multiple BINs can report on the same ICA, which means a drawdown on that ICA will cover all BINs. Similarly, reporting will roll up to that ICA as well. From Lead Bank’s perspective, ICAs can cover multiple BINs of the same type; credit and debit/prepaid BINs must live under separate ICAs.The second is the number of cycles per day that the BINs are configured for. Lead prefers all 6 cycles to be used, if possible.
Credit-Only ProgramsLead still requires receiving T461 files. It is acceptable in this case for these files to be empty, including without headers.
The report Lead requires on a daily basis from Maestro is the SWCHD363 report. Typically, issuer processors will deliver a suite of reports, of which the SWCHD363 report is a single one. Lead can accept any number of reports, as long as the one that contains SWCHD363 data is specified according to the below requirements:
SWCHD363 ReportDescription
Folder/network-settlement/maestro
File FormatSWCHD363
Filename ConventionT461_{yyyy-mm-dd}_maestro_{00X}_reports_{timestamp}.txt
FrequencyOnce per calendar day

​
Additional Details

Since Maestro is under the Mastercard umbrella, Mastercard will be generating this file. Note that this file is also part of the same suite of reports delivered when Mastercard is the primary BIN.
Exception ItemsCan be included in this report where a transaction clears on settlement_date T, but then is also reversed the same day. As a result, the gross spend of that transaction is included in the transaction amount while the gross reversal is included in the refund amount. This means thats both transactions need to be reported to Lead in order to pass reconciliation.
The report Lead requires on a daily basis from Pulse is the PRC643 report. Typically, issuer processors will deliver a suite of reports, of which the PRC643 report is a single one. Lead can accept any number of reports, as long as the one that contains PRC643 data is specified according to the below requirements:
PRC643 ReportDescription
Folder/network-settlement/pulse
File FormatPRC643
Filename Convention{YYYYMMDDXXXXXX}_{program_name}_PRC643.txt
FrequencyOnce per calendar day

​
Additional Details

Pulse has one nuance that affects reconciliation and cashflows. While the PRC643 report aligns with a given settlement date T, the actual funds movements happen either the next business day (T+1BD) or two business days later (T+2BD) depending on the purpose of funds:
PULSE Settlement Day(00:00:00 - 23:59:59 CT)Funds Will Settle via Wire or Wire Drawdown on This DayFees, IPF & Disputes System Will Settle via ACH on This Day
MondayTuesdayWednesday
TuesdayWednesdayThursday
WednesdayThursdayFriday
ThursdayFridayMonday
FridayMondayMonday
SaturdayMondayMonday
SundayMondayTuesday
As long as Lead receives the PRC643 file T+1 of the settlement date T, Lead manages this complexity behind the scenes, resulting in the following nonstandard behavior:
  • On T+1BD
    • Lead transfers funds representing the net amount of transaction spend (gross spend - gross refunds) from the source of funds to the network settlement account
    • Pulse requests via drawdown the same amount of funds
  • On T+2BD
    • Pulse settles via ACH the aggregate amount of net interchange, net disputes, and net fees to the network settlement account
    • Lead transfer the respective funds to the corresponding destination account
From a reporting standpoint, nothing changes from your perspective: You’ll continues to report the settlement date for each transaction, which aligns with the settlement date that Pulse generates the PRC643 report for.
The settlement date from Pulse’s perspective is not the date for which funds are transferred but rather the date for which transactions are cleared.