Transaction Administration - Batch Auth
This mode allows for multiple authorizations to be processed inside of a single request.
In addition to the below paramters each authorization’s data should be present and numbered, starting from 1, in ascending order.
For a full list of the authorization parameters please see the document here
When including the authorization data in the request each parameter will include a hyphon and the transactions correlating number.
As an example:
card-name-1 = John Doe
card-number-1 = 4111111111111111
card-cvv-1 = 123
card-address-1 = 123 Test St
card-amount-1 = 1.23
card-name-2 = Jane Doe
card-number-2 = 4111111111111111
card-cvv-2 = 321
card-address-2 = 321 Test Rd
card-amount-2 = 123.00
An example as a string will look like this:
publisher-name=yourPnPUsername&publisher-password=yourRemoteClientPassword&mode=batchauth&num_txns=2&card-amount-1=129.95&card-name-1=John Smith&card-number-1=4111111111111111&card-exp-1=01/21&card-amount-2=234.56&card-name-2=Mary Jane&card-number-2=4111111111111111&card-exp-2=01/21
See Credit Card Storage Validation Policy
| Variable | Required | Max Size | Notes |
|---|---|---|---|
| publisher-name | Mandatory | NA | Gateway account username issued to you. |
| publisher-password | Mandatory | NA | Remote Client Password - This is different then the password used to login. |
| mode | Mandatory | NA | Value needs to be set to ‘batchauth’ |
| num-txns | Mandatory | 3 | Number of transactions to submit. |
| notify-email | Optional | NA | Email address to send alert notice for transaction problems. |
Response Values - Batch Auth
| Variable | Value | Notes |
|---|---|---|
| FinalStatus | success/problem/pending | Will return ‘success’ or ‘pending’ (processor dependent) upon success. Will return ‘probelm’ on failure |
| success | yes/no | Will return ‘success’ upon success or ’no’ upon failure. |
| Mstatus | sucess/problem/pending | Deprecated in favor of FinalStatus |
| Aux-msg | Aux message if applicable on success. | orderid has been successfully marked for settlement. |
| MErrMsg | Error message if aplicable on failure. | Transaction already voided. It may not be returned. Order ID does not exist as a previous order. It may not be marked for return. Transaction not yet settled. It may not be returned. Transaction has already been returned. |
| FinalStatus-X | success/problem/pending | Will return ‘success’ or ‘pending’ (processor dependent) upon success. Will return ‘probelm’ on failure Response is related to transaction ‘X’ with ‘X’ being a number from 1 - 99. |
| MErrMsg-X | Error message if applicable on failure. | Response is related to transaction ‘X’ with ‘X’ being a number from 1 - 99. |
| Mstatus-X | success/problem | Deprecated in favor of FinalStatus. |
| Duplicate-X | yes/blank | ‘yes’ indicates the orderID of the transaction was previously submitted. Response related to transaction ‘X’ with ‘X’ being a number from 1 -99. |