Skip to content

3.1 File Types

3.1.1 - Files generated by processors

3.1.1.1 - Original Transactions File (.otf)

This is the only file that the processor is responsible for creating and uploading.

Note that the encoding of the file needs to be ISO-8859-15.

Purpose: To send in transactions to be captured during the next processing cycle.
When: The cut-off time is 01:00 AM (GMT) every day.

Example of OTF file
909999012018-08-1506.20.11901otfTEST3.3.1
9699990199999901SS864401EE2018-08-15DEMOSTORE01              Hfj          IS9999352
05M5204730000004635   0000000100003522018-08-1500772042741031122021900000000000001  
05V4761340000032467   0000000101003522018-08-1530976642740938346021900000000000002
06V4761340000032467   0000000102003522018-08-1530976642740938346021900000000000003
9799990199999901SS864401EE000003000000000030300
9699990199999901SS864401EF2018-08-15DEMOSTORE02              Hfj          IS9999352
05M5204730000004635   0000000103003522018-08-1500772042741031122321900000000000004  
05V4761340000032467   0000000104003522018-08-1530976642740938346021900000000000005
06V4761340000032467   0000000105003522018-08-1530976642740938346021900000000000006
9799990199999901SS864401EF000003000000000031200
9699990199999901SS864401EG2018-08-15DEMOSTORE03              Hfj          IS9999352
05M5204730000004635   0000000000003522018-08-1500772042741031122821900000000000007  
9799990199999901SS864401EG000001000000000000000
9699990199999901SS864401EH2018-08-15DEMOSTORE04              Hfj          IS9999352
05M5204730000004635   0000000100003522018-08-1500772142741031123544MCC010188888888  
50427410311235CD0012289F2608BC9A4D0ECF8A9FC29F2701809F102306031203A000000F0300000746930000005307FF4CFD849F3704AD40357E9F3602013B9A032205129C01009F02060000000001005F2A020208820220009F1A0202089F33030048409F34033F00009F3501218407A00000012147119F09020001
06V4761340000032467   0000000105003522018-08-1530976642740938346021900000000000008
05V4761340000032467   0000000104003522018-08-1530976642740938346021900000000000005
05M5204730000004635   0000000100003522018-08-1500772142741031197044MCC010177777777  
50427410311970CD0012289F2608BC9A4D0ECF8A9FC29F2701809F102306031203A000000F0300000746930000005307FF4CFD849F3704AD40357E9F3602013B9A032205129C01009F02060000000001005F2A020208820220009F1A0202089F33030048409F34033F00009F3501218407A00000012147119F09020001  
9799990199999901SS864401EH000001000000000000000
98999901000004

3.1.2 - Files generated by Rapyd

The files below will appear (if present, cf. notes below) in the processor's folder on the SFTP server as soon as processing has taken place. This might be delayed on rare occasions if the load on our systems is exceptionally heavy.

3.1.2.1 - Daily confirmation file (.dcf)

Purpose: To inform the processor if there are any transactions declined in clearing, for example if the authorisation isn't found or because of format errors. Please note that only transactions that are declined are sent in the dcf file. If a batch is processed error free you'll only see the batch header and trailer and no transactions. Declined transactions will not be settled.

Files are generated per .otf file from processor and have the same filename but with the .dcf extension, i.e. 20530922.dcf

Please note

The additional data that relates to declined transactions is only available in .dcf file versions 3.3.2 and later

Example of DCF file
909999012018-08-1606.20.11901dcfTEST3.3.2
9699990199999901SS864401EE2018-08-15DEMOSTORE01              Hfj          IS9999352
06V476134******2467   0000000102009782018-08-15309766427409383460219000000000000022026Unauthorized amount
9799990199999901SS864401EE000001000000000010200
9699990199999901SS864401EF2018-08-15DEMOSTORE02              Hfj          IS9999352
9799990199999901SS864401EF000000000000000000000
9699990199999901SS864401EG2018-08-15DEMOSTORE03              Hfj          IS9999352
05M520473******4635   0000000000008402018-08-15007720427410311220219000000000000012025Transaction amount must not equal zero
50427410311220RD5c12c3bd-9e26-4ef1-8486-bb2269b701b1              
9799990199999901SS864401EG000001000000000000000
9699990199999901SS864401FE2018-08-15DEMOSTORE01              Hfj          IS9999352
9799990199999901SS864401FE000000000000000000000
9699990199999901SS864401FF2018-08-15DEMOSTORE02              Hfj          IS9999352
9799990199999901SS864401FF000000000000000000000
9699990199999901SS864401FG2018-08-15DEMOSTORE03              Hfj          IS9999352
05M520473******4635   0000000000008402018-08-1500772142741031197044MCC0101777777772025Transaction amount must not equal zero
9799990199999901SS864401FG000001000000000000000
9699990199999901SS864401GE2018-08-15DEMOSTORE01              Hfj          IS9999352
9799990199999901SS864401GE000000000000000000000
9699990199999901SS864401GF2018-08-15DEMOSTORE02              Hfj          IS9999352
9799990199999901SS864401GF000000000000000000000
9699990199999901SS864401GG2018-08-15DEMOSTORE03              Hfj          IS9999352
05M520473******4635   0000000000008402018-08-1500772142741031123544MCC0101888888882025Transaction amount must not equal zero
9799990199999901SS864401GG000001000000000000000
98999901000009

Please note

The Daily Confirmation File can be delivered with card numbers masked (6+4).

3.1.2.2 - Settlement report file (.srf)

Purpose: To inform the processor what was settled in the settlement process.
When: This file is only generated when a settlement is done, so can be daily, weekly, bi-weekly etc., depending on the settlement process agreed with merchants.

3.1.2.3 Settlement detail transaction file (no file extension)

The Settlement Detail Transaction File is an optional enhanced settlement report delivered via secure FTP. Note that each Settlement Detail Transaction File will be uploaded to the processors FTP folder and the name formatted as _(as defined in the batch header within each file) without any file extension. The file format is basic ASCII text file. Note that this file is not created unless it's specifically asked for.

3.1.2.4 - Copy request file (.crf)

Purpose: To inform the processor if a card issuer has raised a copy request for some transactions.
Note: This file is only generated if a copy request has been raised by an issuer.

3.1.2.5 - Fraud report file (.frf)

Purpose: To inform the processor that a card issuer has reported fraud on a prior transaction.
Note: This file is only generated if a fraud has been reported by an issuer.

3.1.2.6 - Chargebacks file (.cbf)

Purpose: To inform the processor if a card issuer has reported a chargeback on a prior transaction.
Note: This file is only generated if a chargeback has been raised by an issuer.

3.1.2.7 - Re-presentments file (.rpf)

Purpose: To inform the processor that Rapyd has sent a re-presentment on a prior transaction.
Note: This file is only generated if a re-presentment has been issued by Rapyd.

3.1.2.8 - Early reconciliation file (.erf)

Purpose: To inform the processor of detailed information about each transaction. Files are generated per file from processor and have the same filename, i.e. 20530922.erf.

Note: This report only shows approved transactions and it's generation is only started upon request.

For more detailed information about ERFs please visit the Early Reconciliation section of our specifications.