Input File Specifications
This document defines the technical structure and formatting requirements for the Automatic Debit collection files.
File Naming Convention
Files must follow a strict naming pattern so the engine can correctly identify and route each batch:
*SellerCode*_YYYYMMDD_IN.txt
Example: 65059_20250528_IN.txt
Technical Constraints
The table below summarises the general limits and format requirements that apply to every Input file:
| Requirement | Specification |
|---|---|
| File Format | Plain Text (.txt) fixed-width or delimited (as per integration sheet) |
| Encoding | UTF-8 (without BOM) |
| Maximum Records | 1,000,000 lines |
| Maximum File Size | 250 MB |
| Maximum File Lenght | 203 characters |
Field Specifications
Each record in the Input file must contain the following fields, using the data types and rules described in this table:
| Field Name | Type (Size) | Mandatory | Description |
|---|---|---|---|
| Numero de tarjeta | Numeric (19) | Yes | Card number. Always send exactly 19 digits, padding with leading zeros on the left if needed (e.g., 5123 must be sent as 00000000000000005123). |
| Identificador del debito | String (36) | Yes | Unique ID used to track the debit from enrollment to cancellation. |
| Fecha del debito | Date (YYYYMMDD) | Yes | The date the transaction should be executed. |
| Importe | Numeric (25) | Yes | Value in the smallest unit of local currency (e.g., $102.25 is sent as 0000000000000000000010225 to reach 25 digits). Always pad with leading zeros on the left until the field length is exactly 25 characters. |
| Identificador del cliente | String (36) | No | Merchant's internal identifier for the customer. |
| Soft Descriptor | String (22) | No | Text that appears on the cardholder's statement (e.g., DETALLE*TIENDA). |
| Dato opcional | String (36) | No | Optional field for merchant's usage. |
| Tipo operación | String (6) | Yes | CREDIT, DEBIT or CANCEL. |
| Identificador extreno | Numeric (15) | Yes | External reference number for the merchant's transaction/order identification. |
Formatting Logic
When building each line of the file, apply these formatting rules consistently across all records:
- Decimal Handling: Do not include dots or commas. Multiply the amount by 100 to send the value in cents.
- Padding: Numeric fields must be left-padded with zeros to reach the specified length. String field must be right-padded spaces.
- Refunds: To process a refund, use the CANCEL operation type and provide the Payment ID, sourced from the
payment_IDfield in the output file. - Padding: Numeric fields must be left-padded with zeros to reach the specified length.
- Refunds: To process a refund, use the CANCEL operation type and provide the Payment ID from the original transaction.
Next Steps
Use these related guides to apply this specification in your daily operation.
- When your file is ready, continue with Uploading and Managing Collection Files to submit the batch and verify early validation statuses.
- To understand what is returned after execution, review Output File Data Dictionary so your reconciliation logic maps each result field correctly.
- If you need broader operational constraints, check Processing Rules and Deadlines before scheduling large-volume runs.
On this page
Input File Specifications