SFTP Export Data Documentation

SFTP Upload Files

Overview:

The SFTP Upload section provides description services to facilitate the secure upload of various ISO-related files through the Secure File Transfer Protocol (SFTP). These files cover a wide range of financial data and transaction details, enabling institutions to handle and process critical operations such as ACH transactions, chargebacks, transaction authorization, compliance, and reporting.

Data is usually uploaded once a day. Format of data XML or JSON.

📘
Data model
See the method responses that describe the structure of files. In the response there is a description of fields and information that is contain in the file.

Using SFTP for file uploads ensures the secure transfer of sensitive financial data, allowing for automated and manual submission of files required for different operational and regulatory processes.

Supported File Types:

Transactions:
- Files containing detailed information about financial transactions, including payments, transfers, and deposits.
- Used for processing and reconciliation of customer and institutional transactions.\
ACH:
- Files used for Automated Clearing House (ACH) transactions, including direct deposits, bill payments, and inter-bank transfers.
- Supports the transfer of funds electronically between banks and other financial institutions.
TransAuth:
- Transaction authorization files, containing details about approved or declined transactions.
- Used for processing real-time transaction approvals and ensuring security in payment systems.
Chargeback:
- Files related to chargeback transactions, which occur when a customer disputes a transaction.
- Includes details on the reversal of funds and the reasons for the dispute.
ACHRejectsCollects:
- Files detailing ACH rejects (failed transactions) and collections.
- Used to manage and correct failed ACH transfers and initiate recovery processes for unsettled transactions.
MASM1001 / MASD1001:
- Specific formats used for MAS (Merchant Accounting System) files.
- These files include merchant financial data, settlement details, and reconciliation data for the corresponding financial periods.
SimplifiedFormat:
- A simplified file format for reporting transactions or account details.
- Designed for easier parsing and processing by institutions with limited technical complexity.
TransactionsExtendedData:
- Files containing extended transaction data beyond standard transaction details.
- May include additional metadata, such as customer information, transaction history, or enhanced reporting fields.
TINMismatch:
- Files related to TIN (Taxpayer Identification Number) mismatches.
- Used to report inconsistencies between tax identification details provided by clients and the IRS database, for tax compliance purposes.
PCIStatuses:

Files that report Payment Card Industry (PCI) compliance status.
Essential for monitoring and reporting on the adherence to PCI Data Security Standards (PCI DSS), ensuring the secure handling of credit card data.

Reserve Funding:
- The Reserve Funding file provides a detailed daily snapshot of reserve account activity for each merchant. It captures gross sales, ACH deposit amounts, reserve withholding calculations, release schedules, and running reserve balances — giving institutions full visibility into rolling and fixed reserve management.
- Data is exported once daily in JSON format and delivered to the configured SFTP directory.
  
  Example JSON
Statements:
- 11.1 The system generates a structured XML file containing the Acquiring service statement data, including customer account details, billing period, usage metrics, and financial transactions. Once generated, the XML file is securely transmitted to the configured SFTP server using predefined credentials and folder paths. This format is suitable for integration with external systems that process financial or service data automatically.
  Example XML
- 11.2 The system generates a customer-friendly PDF version of the Acquiring service statement, visually formatted for readability and compliance. This document includes branding elements, billing summaries, payment instructions, and detailed usage information. Once the PDF is created, it is uploaded securely to the SFTP server, typically for archival, auditing, or customer communication purposes.
  Example PDF

Workflow:

SFTP Setup:
- Users must have SFTP credentials and proper permissions to securely upload files.
- Each file type must adhere to specific formats and validation rules as required by the system.
File Upload Process:
- Upload files through the SFTP interface to designated directories based on the file type.
- The system automatically processes uploaded files, validates their content, and integrates them into the corresponding financial workflows (e.g., transaction processing, ACH settlement, compliance reporting).
File Status Monitoring:
- After upload, users can track the processing status of their files (e.g., processed, rejected, errors) and take corrective action if necessary.
- Detailed error reports or success acknowledgments are provided based on the file processing outcome.
Compliance and Reporting:
- Many of the files (e.g., TINMismatch, PCIStatuses) are critical for regulatory compliance and need to be regularly uploaded to meet legal and industry standards.
- Files are subject to periodic audits and reviews as part of institutional compliance processes.

Security:

All file transfers through SFTP are encrypted to ensure the confidentiality and integrity of sensitive financial data.
Strong authentication and access control measures are in place to ensure that only authorized personnel can upload and manage these files.

This API section is essential for handling a broad range of operational, regulatory, and financial processes, allowing financial institutions to manage critical data efficiently while ensuring compliance and security.

SFTP FILES EXPAMPLES:

https://drive.google.com/drive/folders/1PAuaT8JmzsI_RQFu3iWXeivRVbM7Z8aN?usp=drive_link