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.

important

This is needed for certification and should be part of testing during implementation.

API FieldField NameSizeTypeOption/DescriptionInOutStore
0001Transaction Type2NTran Type 14 Batch Inquiry.YesYes
0109Terminal ID1-8A/NTerminal ID
Optional, if inquiring for the entire Chain Code or Location leave blank.
YesYes
1003Elavon Response Code1-4NElavon Gateway Response Code.
Yes
1004Host Response Code1-80A/NHost Response Message, Either verbatim or evaluated. May contain Elavon Gateway Message.
Yes
1010Elavon Response Message1/80A/NElavon Gateway verbose response message corresponding to error code returned in API field 1003.
Yes
1012Elavon Batch Number1-8NElavon 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
1013Local Batch Net Amount1-20CNet amount of transactions captured in the Fusebox batch file. This field will contain a leading “-” sign if net amount is negative.
Yes
1014Local Batch Tran Count1-9NTotal count of transactions captured in the Fusebox batch file.
Yes
1016Host Batch Net Amount1-20CFor 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
1017Host Batch Tran Count1-9NFor host capture processors capable of returning this information. Total count of transactions captured in the host batch file.
Yes
1018Funded Batch Amount1-20CThis value will be blank on a batch inquiry of an open batch.
Yes
1019Funded Batch Count1-9NThis value will be blank on a batch inquiry of an open batch.
Yes
7007Transaction Link Identifier21NThis field is the unique identifier to a transaction in Fusebox.
Yes
8002Location16A/NLocation name passed in the transaction.
*Optional if inquiring for the entire Chain Code leave blank.
Yes *Yes
8006Chain Code6A/NChain Code passed in the transaction (required).YesYes

* Optional field is based on the level at which you are choosing to settle; Chain Code, Location, or Terminal ID.

Force Close

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.

  • Test: https://gatewaydemo.elavon.net/ui/portal.html
  • Production: https://fusebox.elavon.net/ui/portal.html

Ensure the user has proper access rights and permissions to log in to process a settlement.

Request

0001,0013<–Transaction Type–>
0109,TERM01<–Terminal ID–>
8002,LOC1<–Location Name–>
8006,TSTLAR<–Chain Code–>

Response

0001,13<–Transaction Type–>
0109,TERM01<–Terminal ID–>
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–>
8002,LOC<–Location Name–>
8006,TSTLAR<–Chain Code–>