iveri Networked Credit Card System BATCH PROCESSING FIXED FORMAT SPECIFICATION Version 1.04

Transcription

1 iveri Networked Credit Card System BATCH PROCESSING FIXED FORMAT SPECIFICATION Version 1.04

2 iveri Batch Processing Page 2 of 11 Preface Changes included in this document include : 1. Original Document. 2. Changes made by R. Elferink changing the Merchant Invoice Field to 32 characters and adding the Merchant Reference Field as well as the Budget Period 3. Added the reconciliation status to indicate whether the transaction has been reconciled with the bank and if so, if it is correct. 4. Changed the brand name to iveri from Set2Go 5. Added the ability to Perform Authorisations and Authorisation Reversal. Corrected CCYY to YYYY to clear up confusion with 2101 being the year 01 in the 21 st Century. Corrected formatting in Reference Invoice Number 6. Change the names of the following fields in line with that used thoughout the iveri Gateway (previous name new name): Merchant Invoice Number Merchant Reference Transaction Request Date/Time Purchase Date/Time Transaction Response Date/Time Acquirer Date/Time

3 iveri Batch Processing Page 3 of 11 INTRODUCTION The Batch File to be processed (Batch Upload File) is an ASCII text file with a fixed field record structure. Each transaction is recorded as a single line in the text file. Once a Batch has been processed the Result File for the Batch is available for download. Note that the Reconciliation Status of the individual transactions might not yet be updated, since the reconciliation process only occur the day after processing. The following banks are able to support this batch processing environment Nedbank

4 iveri Batch Processing Page 4 of 11 The Batch Upload File Record Layout The Batch Upload File consists of three sections namely :- Header Transaction records Trailer HEADER RECORD Record Type N*2 "00" Bank Code Identifier for the N*2 "NN" bank at which the USN is valid Merchant USN The USN to use to N*10 "NNNNNNNNNN" process the batch with File Processing Date If this date is the N*8 "YYYYMMDD" current date or up to 1 calendar month old then the file will be processed on the date on which it is uploaded. If the date is up to 1 calendar month in advance of the date on which the file is uploaded, then the file will be held on the iveri server until the specified date when it will then be processed on that specified date. Application ID Your ApplicationID A*36 "AAA AAA" allocated by iveri Merchant Name Your Merchant Name under which your ApplicationID has been registered A* "AAA "

5 iveri Batch Processing Page 5 of 11 CREDIT CARD TRANSACTION RECORD Record Type N*2 "01" Merchant Terminal Number Merchant Reference Used to group transactions together Unique identifier for this invoice or credit note. NOTE: DO NOT USE ANY COMMA s AS PART OF THIS IDENTIFIER A*8 "AAAAAAAA" A*32 "AAA AAA" Transaction Code See Appendix B N*2 "NN" Purchase Date Date the invoice or credit note was raised N*8 "YYYYMMDD" Purchase Time Time the invoice or credit note was raised N*4 "HHMM" Amount Value is in cents N*10 "NNNNNNNNNN" CCNumber Credit Card Number NOTE: Pad with zeros from the left to fill the required field of twenty numbers N*20 "NNN...NNN" Card Start Date The beginning of the period for which the card is valid. If this is not available use the current month and year. N*6 "YYYYMM" Card Expiry Date N*6 "YYYYMM" Authorisation Code Pre-authorisation code if one has been obtained for this transaction N*6 "NNNNNN" Set to "000000" if it does not exist Budget Period Original Merchant Reference The Budget period to request this authorisation to be used with. In number of months The Invoice Number of the original invoice which is being refunded. This is only used for the case where a refund is being performed. Note that the format of this field must be right justified irrespective of whether it is numeric or alphanumeric. N*2 NN Set to "00" if it does not exist A*32 "AAA AAA" Set to " " (all spaces) if it does not exist.

6 iveri Batch Processing Page 6 of 11 TRAILER RECORD Record Type N*2 "09" Total number of N*6 "NNNNNN" transactions Total Amount The simple sum of all the amounts without regard to whether it is a sale or a refund etc N*10 "NNNNNNNNNN"

7 iveri Batch Processing Page 7 of 11 The Batch Result File Record Layout The Batch Result File consists of three sections namely :- Header Transaction records Trailer HEADER RECORD Record Type N*2 "90" Bank Code Identifier for the bank at which the N*2 "NN" Merchant USN Date when file was created USN is valid The USN used to process the batch with N*10 "NNNNNNNNNN" N*8 "YYYYMMDD" CREDIT CARD TRANSACTION RECORD Record Type N*2 "91" Merchant Terminal Number Merchant Reference Used to group transactions together Unique identifier for this invoice or credit note A*8 "AAAAAAAA" A*32 "AAA AAA" Transaction Code See Appendix B N*2 "NN" Transaction Status Refer to Appendix N*5 "NNNNN" B Acquirer Date Actual Date of the N*8 "YYYYMMDD" transaction Acquirer Time Actual Time of the N*4 "HHMM" transaction Amount Value is in cents N*10 "NNNNNNNNNN" CCNumber The credit card number is passed back in mangled form e.g " " N*20 "NNNN...NN" Authorisation Code Cycle Number Authorisation code allocated to this transaction Along with the Trace Number this forms a unique identifier for this transaction N*6 "NNNNNN" N*6 "NNNNNN"

8 iveri Batch Processing Page 8 of 11 Trace Number Reconciliation Status TRAILER RECORD Along with the Cycle Number this forms a unique identifier for this transaction The Reconciliation Status for this transaction as per Appendix B - Reconciliation Status N*6 "NNNNNN" N*5 "NNNNN" Record Type N*2 "99" Total number of N*6 "NNNNNN" transactions Total Amount The simple sum of all the amounts without regard to whether it is a sale or a refund etc N*10 "NNNNNNNNNN"

9 iveri Batch Processing Page 9 of 11 Appendix A : Field Justification All Fields are justified in the following manner :- Numeric Fields are pre-pended with 0's to the full width of the format Alphanumeric Fields are left justified and ' ' (spaces) appended to the full width of the format A* means an unspecified length field - we read to the end of the line.

10 iveri Batch Processing Page 10 of 11 Appendix B : Field and Reply Codes Bank Code VALUE DESCRIPTION "01" Nedbank "02" Not used - Yet Transaction Code VALUE DESCRIPTION "01" Sale "02" Refund 03 Authorisation 04 Authorisation Reversal Transaction Status Please refer to the Error Codes in the Documentation on Reconciliation Status VALUE DESCRIPTION "00000" Unreconciled - The reconciliation process for this transaction has not taken place yet. "10000" Reconciliation has taken place and the result code accurately depicts the status of the transaction "10001" Reconciliation has taken place and the transaction could not be found. "10002" Reconciliation has taken place and the transactions details either in amount, cardholder, result code, cycle number, trace number does not match.

11 iveri Batch Processing Page 11 of 11 Reply Codes RESULT STATUS: OK (0) ResultCode ResultStatus ResultDescription 0 0 N/A (Approved) RESULT STATUS: NOT OK (1) ResultCode ResultStatus ResultDescription 1-1 Timeout waiting for response. Try again 3-1 Hot card 4-1 Denied 5-1 Please call 6-1 Card Address Failure 7-1 Card Security Code Failure 8-1 Card Type not accepted 9-1 Unable to process the transaction 11-1 Invalid Amount 12-1 Invalid Budget Period 14-1 Invalid Card Number 15-1 Invalid Track Invalid Expiry Date/Card Period 18-1 Invalid Authorisation code Unknown Error ResultCode:255 refers to any unclassified 'NotOK' situation Enterprise Merchants have an exception thrown for ResultCode 255 Therefore ResultCode:255 is will only be seen by Non Enterprise Merchants RESULT STATUS: WARNING (-1) ResultCode ResultStatus ResultDescription 6 1 Warning: Card Address Failure 7 1 Warning: Card Security Code Failure