Batch processing API
Batch processing allows a merchant to deliver a file using the gateway name/pair values. 360 One will email confirmation that the file was received and a follow up email once the batch of requests have been processed.
Contents
The API interface is a simple POST message, therefore language is up to the developer.
Introduction
To effectively implement the batch processing, basic API programming knowledge is required. While requests are submitted as simple POST, it is recommended to use a server-side scripting language to build the HTTP request.
System Architecture
The batch processing option may be used for large files, typically recurring transactions, that require both authorization and capture (sale transaction), or in conjunction with an authorization performed directly with Payment Gateway. For example, capturing all pre-authorizations at the end of day, which were authorized through the Payment Gateway.
Batches may also be submitted and response files retrieved via the 360 One web portal.
Technical Overview
Steps taken by the developer and 360 One to validate the transactions submitted to the 360 One Payment Gateway contain the proper fields to qualify transactions at desired Interchange rates.
Batch processing supports two actions: Upload and Download.
Example Upload request
In the upload file, periods have been added to represent spaces, and ¶ have been added to represent line breaks.
- POST /srv/api/bpUpload HTTP/1.1
Content–Type: multipart/form–data
Cache–Control: no–cache
Pragma: no–cache
User–Agent: Java/1.7.0_21
Host: www.merchante–solutions.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: xxx—————————–41184676334
Content-Disposition: form-data; name=”userId”pjones
—————————–41184676334
Content-Disposition: form-data; name=”userPass”xxxxx
—————————–41184676334
Content-Disposition: form-data; name=”testFlag”Y
—————————–41184676334
Content-Disposition: form-data; name=”reqFile”; filename=”upload_file.txt”
Content-Type: text/plaintransaction_type=P&card_number=4012888812348882&card_exp_date=1216&transaction_amount=1.00&cvv2=123&cardholder_street_address=123+N.+Main&cardholder_zip=55555&invoice_number=123456
transaction_type=P&card_number=4012888812348882&card_exp_date=1216&transaction_amount=1.00&cvv2=123&cardholder_street_address=123+N.+Main&cardholder_zip=55555&invoice_number=123456
transaction_type=P&card_number=4012888812348882&card_exp_date=1216&transaction_amount=1.00&cvv2=123&cardholder_street_address=123+N.+Main&cardholder_zip=55555&invoice_number=123456
transaction_type=P&card_number=4012888812348882&card_exp_date=1216&transaction_amount=1.00&cvv2=123&cardholder_street_address=123+N.+Main&cardholder_zip=55555&invoice_number=123456
Example Upload response
Upon successful upload, an email will be sent to the address associated with the merchant account. A follow-up email will additionally be sent once the batch has finished processing.
- rspCode=000&rspMessage=OK
Example Download request
- POST /srv/api/ausStatus HTTP/1.1
Content–Type: application/x–www–form–urlencoded
Cache–Control: no–cache
Pragma: no–cache
User–Agent: Java/1.7.0_21
Host: test.merchante–solutions.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: xxxuserId=pjones&userPass=xxxxx&respFileID=124
Example Download response
The download file will contain Payment Gateway responses, in the same order as the requests in the request file.
- transaction_id=19c680eb42053f5684300a9c225c124c&error_code=000&auth_response_text=Exact Match&avs_result=Y&cvv2_result=M&auth_code=T9692H
transaction_id=dc9e7ea485dc3bd29918be980a45088d&error_code=000&auth_response_text=Exact Match&avs_result=Y&cvv2_result=M&auth_code=T9696H
transaction_id=bd440051e9063cbe8a09efd296829224&error_code=000&auth_response_text=Exact Match&avs_result=Y&cvv2_result=M&auth_code=T9697H
transaction_id=0e19f0816d993a6ebf797fc87f29eb65&error_code=000&auth_response_text=Exact Match&avs_re
