Batch Close (13)
The Batch Close (13) transaction can perform all of the functions of the Batch Create and Inquiry (14). Batch Close can also close the batch in Fusebox.
Deposits or settles transactions in conjunction with the POS initiated or API Based Settlement through PBFE feature.
This is needed for certification and should be part of testing during implementation.
|API Field||Field Name||Size||Type||Option/Description||In||Out||Store|
|0001||Transaction Type||2||N||Tran Type 14 Batch Inquiry.||Yes||Yes|
|0109||Terminal ID||1-8||A/N||Terminal ID
*Optional, if inquiring for the entire Chain Code or Location leave blank.
|1003||Elavon Response Code||1-4||N||Elavon Gateway Response Code.||Yes|
|1004||Host Response Code||1-80||A/N||Host Response Message, Either verbatim or evaluated. May contain Elavon Gateway Message.||Yes|
|1010||Elavon Response Message||1/80||A/N||Elavon Gateway verbose response message corresponding to error code returned in API field 1003.||Yes|
|1012||Elavon Batch Number||1-8||N||Elavon Gateway batch number. A global number generated to represent a batch of transactions. The batch may contain many different TPPs, each uploaded under a different host batch number.||Yes|
|1013||Local Batch Net Amount||1-20||C||Net amount of transactions captured in the Fusebox batch file. This field will contain a leading “-“ sign if net amount is negative.||Yes|
|1014||Local Batch Tran Count||1-9||N||Total count of transactions captured in the Fusebox batch file.||Yes|
|1016||Host Batch Net Amount||1-20||C||For host capture processors capable of returning this information. Net amount of transactions captured in the host batch file. This field will contain a leading “-“ sign if net amount is negative.||Yes|
|1017||Host Batch Tran Count||1-9||N||For host capture processors capable of returning this information. Total count of transactions captured in the host batch file.||Yes|
|1018||Funded Batch Amount||1-20||C||This value will be blank on a batch inquiry of an open batch.||Yes|
|1019||Funded Batch Count||1-9||N||This value will be blank on a batch inquiry of an open batch.||Yes|
|7007||Transaction Link Identifier||21||N||This field is the unique identifier to a transaction in Fusebox.||Yes|
|8002||Location||16||A/N||Location name passed in the transaction.
*Optional if inquiring for the entire Chain Code leave blank.
|8006||Chain Code||6||A/N||Chain Code passed in the transaction (required).||Yes||Yes|
* Optional field is based on the level at which you are choosing to settle; Chain Code, Location, or Terminal ID.
Either the POS will send an API-based batch close message to Fusebox, or the user will log in to the user interface to close a batch.
Fusebox automatically creates a batch with all financial transactions sent from the POS and will accrue them into batches by Site ID. If a batch remains open for 7 days, it will automatically close in Fusebox.
To settle from the Elavon Gateway User Interface, login to the User Interface and ensure the amounts about to be settled have been reconciled in the previous steps.
Ensure the user has proper access rights and permissions to log in to process a settlement.
1003,0000<–Elavon Gateway Response Code–>
1004,ACKNOWLEDGED<–Host Response Message–>
1010,COMPLETE<–Elavon Gateway Response Message–>
1012,0007<–Elavon Gateway Batch Number–>
1013,1587,00<–Net amount of Transactions in a batch–>
1014,101<–Total transactions in batch file–>
1016,1587,00<–Net amount of transactions in host batch file–>
1017,101<–Total count of transactions in host batch file–>
1018,11587,00<–Total amount funded in a batch if accepted–>
1019,101<–Total number of transactions to be funded in a batch to be funded if accepted–>
7007,1234567890123456<–Transaction unique identifier–>