Introduction

• This file format is the Standard BPOINT Batch Format and can be specifically adjusted for the purpose of tokenisation of card and bank account numbers in the BPOINT DataVault of a single Merchant Facility (in the MULTI module). Any changes made to the BPOINT Batch Format will change all batch formats and functions related to this document.

• Account Numbers may contain either Credit Card numbers or Bank Account numbers (only if the Bank account option is enabled by the Bank). Valid Credit Card numbers also include Scheme Debit Cards such as MasterCard Debit and Visa Debit.

File Naming Convention

• The File Name can contain characters A-Z, a-z, 0-9, “_” or “-“

• File name must be less than 45 characters in length.

• The file extension must be either “.DAT”, “.TXT” or “.CSV”.

• Files may be uploaded as zipped. A zipped file may contain several batches. The zip file should not be password protected.

• Except via sFTP, the result file will be named the same as the upload file with “-R” appended to the file name, e.g. “XYZ.CSV” will have a result file “XYZ-R.CSV”.If received via sFTP, the result file name will be unchanged from the upload file name.

File Format Rules

• File is in CSV format, i.e. comma delimited.

• The last field in each record does not close with a comma.

• Fields are left-justified with no trailing spaces.

• An empty field is signified by a comma immediately following the comma after the previous field, e.g. “,,”.

• Each record (Header, Detail Record and Trailer) must end in a Carriage Return Line Feed (CRLF) character (ASCII values 13 and 10).

• Each file should have at least a File Header, File Trailer and at least one Detail Record (Payment or Refund).

• The File Creation Date must be within 90 days of the submission date and may not be in the future. At the point of uploading the file the processing may be set to process either as soon as possible or at a future date, which must be within 6 weeks. 
 

Data Definition

The batch format includes fields for both the submission and results returned from a transaction request, these are shown in the Detail Record below. Depending on the type of transaction you are processing, some of these fields do not need to be included within the record and can be omitted. Other fields must be included in every record. Detail Records for the types of transactions and samples are included below. File Header and Trailer records are mandatory.

File Header Record

Group Header Record (Optional)

Group headers and trailers should only be used if you are submitting records on the behalf of multiple BPOINT Merchant Facilities (multiple Merchant Numbers) in the one batch file. Records for each facility should be grouped within one Group Header Record and Group Trailer Record. If you wish to include a Group Header in your batch file do not include the BPOINT Merchant Number in the File Header. If records are only submitted against one BPOINT facility, the Group Header Record and Group Trailer Record will not be returned in the results file. 

Detail Record(s)

Below is the format of the batch detail record showing all fields. The fields used are determined by the type of transaction you are submitting in the batch file. The Record Type field is used to identify which fields are available for each type of batch record. Note that not all fields are Mandatory and you should refer to the specific type of transaction you are submitting from the list below.

Transaction Results are returned on a processed transaction and can be used to capture the transaction results for your business purposes. 

Group Trailer Record (Optional) 

Group headers and trailers should only be used if you are submitting records on the behalf of multiple BPOINT Merchant Facilities (multiple Merchant Numbers) in the one batch file. Records for each facility should be grouped within one Group Header Record and Group Trailer Record. If you wish to include a Group Header in your batch file do not include the BPOINT Merchant Number in the File Header. If records are only submitted against one BPOINT facility, the Group Header Record and Group Trailer Record will not be returned in the results file. 

File Trailer Record 
 

Sample File

1.1 Batch File for Single Merchant

Batch File:

01,CBA-EVOLVE,20120804,081712,,1,5353109191111111 50,,1234,Mr Fred Smith,945678,1000,0,5123456789012346,99/00,M 50,,25487,Mrs Audry Smythe,,2000,0,5123456789012346,99/00,M 50,,8945,Mr John Chimes,5689,1001,0,5123456789012346,99/04,M 99,5,4001

Result File:

01,CBA-EVOLVE,20120905,120946,,1,535310919111111150,,1234,Mr Fred Smith,945678,1000,0,,99/00,M,,,,,,,,512345...346,MC,1,91749883,26709699883,,,A00 50,,25487,Mrs Audry Smythe,,2000,0,,99/00,M,,,,,,,,512345...346,MC,1,91749881,26709699881,,,A0050,,8945,Mr John Chimes,5689,1001,0,,99/04,M,,,,,,,,512345...346,MC,0,96533092,28165983092,CANCELLED CARD,3,C04 99,5,4001,3000

1.2 Batch File for Multiple Merchants

Batch File:

01,CBA-EVOLVE,20120918,160000,,1, 10,5353109191111111,AUD 50,,test1,test2,test3,100,,5123456789012346,99/00,R,,,,,,,,,,,,,,,,, 
90,5353109191111111,AUD,1,100 10,5353109192222222,AUD 50,,test1,test2,test3,200,,5123456789012346,99/00,R,,,,,,,,,,,,,,,,, 90,5353109192222222,AUD,1,20099,8,300

Result File:

01,CBA-EVOLVE,20120918,162650,,1,10,5353109191111111, 50,,test1,test2,test3,100,0,,99/00,R,,,,,,,,512345...346,MC,1,92910938,27065510938,,,A00 90,5353109191111111,,1,100,10010,5353109192222222, 50,,test1,test2,test3,200,0,,99/00,R,,,,,,,,512345...346,MC,1,92910937,27065510937,,,A00 90,5353109192222222,,1,200,20099,8,300,300

1.3 Refund File

Batch File:

01,CBA-EVOLVE,20120804,081712,,1,535310919111111160,,25487,Mrs Audry Smythe,,2000,0,5123456789012346,99/00,M,91749881,Ref1 99,3,2000

Result File:

01,CBA-EVOLVE,20120905,121654,,1,535310919111111160,,25487,Mrs Audry Smythe,,2000,0,,99/00,M,91749881,Ref1,,,,,,512345...346,MC,0,96545284,28166805284,DECLINED,4,X99 99,3,2000,0

1.4 Batch File Containing a Payment and a Refund

Batch File:01,CBA-EVOLVE,20120924,113900,001,1,5353109191111111 50,1234006,Test,Test2,Test3,1000,100,5123456789012346,99/00,R,,,AUD,,,,,,,,,,,,,, 
60,1234006,Test1,Test12,Test13,1000,,5123456789012346,99/00,R,93369556,Refund#1595,AUD,,,,,,,,,,,,,, 99,4,2000

Result File:

01,CBA-EVOLVE,20120924,163249,,1,1000000000000006 50,1234006,Test,Test2,Test3,1000,100,,99/00,R,,,,,,,,512345...346,MC,1,93369557,27227629557,,,A00 60,,Test1,Test12,Test13,1000,0,,99/00,R,93369556,Refund#1595,,,,,,512345...346,MC,0,96545886,28166955886,DECLINED,4,X99 99,4,2000,1000

1.5 Batch File Containing Bank Accounts

Batch File:

01,CBA-EVOLVE,20120804,081712,,1,535310919111111150,,25487,Mrs Audry Smythe,,2000,0,12345678,,M,,,,,,,,,,,,,,,,063120,Mrs Symthe 99,3,2000

Result File:

01,CBA-EVOLVE,20120924,164011,,1, 535310919111111150,,25487,Mrs Audry Smythe,,2000,0,,,M,,,,,,,,063120###678,BA,1,36387125,27227767125,,,A00,, 99,3,2000,2000

Appendix 1 - BPOINT TESTING

The BPOINT platform can be configured by the helpdesk to allow for testing of all services. A test transaction is triggered by setting the month field in the expiry date to ‘99’. The test response received can be controlled by setting the year field in the expiry date to a number between ‘00’ and ‘99’. The test transaction will return the same value as what was submitted in the YY field.

Only the below test cards must be used. 

Production Verification Testing

For full end to end testing to your settlement account we recommend the following process.

Business Day 1. Use a valid credit card number and expiry dates for a small amount such as $1.00

Business Day 2. Reconcile your bank account with an entry for the amount transacted on Business Day 1.

Business Day 3. Go to ADMIN within the BPOINT Back Office and SEARCH for the test transactions. You can refund them individually. Alternatively you can create a batch file of refunds and submit it into MULTI.

Business Day 4. Once again you can reconcile your bank account against the refund transactions performed on Business Day 3.