Processing Rules and Deadlines

Technical guidelines for the timing and logic of the Automatic Debit engine.

Submission Windows

These rules control when files can be submitted and how they are grouped for processing:

• The 24-Hour Rule: Files must be uploaded at least 24 hours before the Charge Date defined in the file.
• Batch Frequency: Processing occurs once daily during the nightly maintenance window.
• File Consistency: A single file can only contain records for one specific Charge Date.

Refund and Cancellation Logic

The following points describe how to correct mistakes or reverse charges once a file has been submitted:

• Modifying Submissions: You can delete a file via the Merchant Portal as long as its status is Listo para procesar or Inválido. Once it moves to En progreso, no further changes are possible.
• Issuing Refunds: Refunds are handled by submitting a new Input file. You must set the Operation Type to CANCEL and reference the ID de transacción received in the original Output file.

Data Integrity Rules

To avoid validation errors, make sure all data obeys these integrity rules before uploading a file:

• Zero Padding: The system requires numeric fields (like Card PAN and Amount) to be fixed-width, padded with leading zeros. Failure to pad these fields will result in an INVALID file status.
• Currency Units: All amounts must be expressed in the smallest unit (cents/centavos). For example, a transaction for $1,500.00 must be sent as 150000.
• Record Limit: Any file exceeding 1,000,000 lines or 250 MB will be automatically rejected by the portal during the upload phase.

Next Steps

Use these related references to apply timing and integrity rules correctly in production.

• Before sending a batch, review Input File Specifications to ensure every line complies with field sizes, formats, and operation definitions.
• For practical submission flow and validation checkpoints, follow Uploading and Managing Collection Files and schedule your upload with the required lead time.
• After execution, use Output File Data Dictionary to interpret statuses, error codes, and identifiers during reconciliation.