Configure FicherosTXT with ImaCash
FicherosTXT receives POS requests through text files. The provider must prepare the format and collect results before commercial use. It is not Ficheros Alcornoque, FicherosRCSCash or a test profile; the name does not validate every device or operating system.
1. Prepare the exchange
Reserve a folder dedicated to this POS and installation. The ImaCash Windows user needs to read, create, move and delete files and create subfolders. Do not select the drive root, personal documents or backups. Check access to any network share under that same user; do not assume multiple concurrent readers.
2. Select FicherosTXT
Open Configuration > Integration, choose the ImaCash category and select FicherosTXT. Configure the cash device separately. The method name does not make other file connectors equivalent or require switching to a hidden or test profile.
3. Set the folder
Under Sales, select the exchange directory confirmed by the provider, not an individual file. Older screenshots may show Transactions and a former Save button. The connector does not request its own SQL server, database, port or credentials. Keep the path and network share credentials private.
4. Prepare the TXT
Each file contains one request: only the first line is read, with exactly six semicolon-separated fields. Do not add a header or rely on additional lines. The POS must finish the file before making it visible as TXT; agree encoding and format with the provider for the regional settings of the ImaCash Windows installation.
| Field | Content the provider must confirm |
|---|---|
| Amount | Requested amount and sign, with no thousands separator. Validate the decimal separator under the actual ImaCash regional settings. A negative amount does not prove refund authorization. |
| Terminal | POS workstation identifier retained as request data, not the device model. |
| Reference | Unique, valid operation identifier suitable for naming the response, with no path separators. Do not reuse or change it to repeat an uncertain payment. |
| Salesperson | Operator identifier or label sent by the POS; it must match filters without assuming a user catalog. |
| Date and time | Date and time that ImaCash can interpret under its regional settings. Confirm format and business date with the provider. |
| Payment type | 1 for cash or 0 for card, according to the agreed format. Do not send other values or treat the field as bank authorization. |
5. Save when closing
Close Configuration and confirm saving when prompted; follow the proposed restart if applicable. Startup checks basic directory access and writing, but a connected indicator does not prove format, file movement, payment or receipt of the response by the POS.
6. Distinguish capture from payment
Available TXT files are read without rebuilding history from the synchronization date. Files may move to processed when incorporated or reviewed locally; that does not mean paid. Empty or malformed files may move to error, without every failure generating a .KO response. Do not delete, edit or reintroduce files from those folders to force a payment.
7. Check cards and filters
Type 1 identifies cash and 0 identifies card. Accept cards allows card requests to be included; it does not authorize or settle a bank payment, and the format does not split mixed payments. Check terminal and salesperson against local filters; the six fields supply no independent company or till and no store or operator catalogs. Item, shift and bank total retrieval is not validated.
8. Verify responses and cancellation
Confirmation attempts to write an .OK response identified by the reference, which may differ from the original TXT filename. Cancellation uses .KO and may rename its request file; not every format issue is a cancellation. The POS must use the cancellation format agreed with the provider. A file being present does not prove that the source has read it or closed the operation, or that cash has been refunded.
9. Validate the complete flow
Test the request, incorporation, amount and sign, outcome in ImaCash and the device, and response receipt in the POS with the provider. Confirm business date, currency, filters and supported cancellations without promising a universal two-hour window or freedom from duplicates. If uncertain, review systems and actual cash before repeating, resending, changing references, resynchronizing or restarting. This documentation review does not replace a physical test.