This NETePay is available via the NETePay 5 Director which provides a simplified installation process and go-forward automatic software updates. NETePay 5 Director is recommended but if needed the classic installation process is still available by clicking Download as usual.
To learn more about the NETePay 5 Director click here.
Release date: 01/10/2019
This version supports a new Local Batch Inquiry feature. This allows an ISV to programmatically retrieve transaction data from the Local Batch Reporting tables. When using Store and Forward, it provides an easy way to review transaction data for declines which translate directly to merchant losses. The Local Batch Inquiry feature include two new TranCodes – BatchReportQuery and BatchReportTransaction. These are both <Admin> functions. The Local Batch database contains two tables, BATCH and DECLINE. The BATCH table contains all approved transactions. The DECLINE table contains all declines and errors.
- The following are optional XML fields for BatchReportQuery
For <TransDateTimeBegin> and <TransDateTimeEnd>, a date range may be supplied with or without times. Valid formats are “YYYY-MM-DD” or “YYYY-MM-DD HH:MM:SS”. If these tags are not supplied, today’s date is assumed.
For <CmdStatus>, valid values are “Approve”, “Decline” or “All”. Use “Approve” to retrieve data from the BATCH table. Use “Decline” to retrieve data from the DECLINE table. Use “All” to retrieve data from both tables. If this tag is not supplied, “Decline” is the default.
For <SAFOnly>, valid values are “Yes”, “No”, or “All”. Use “Yes” to retrieve data only for transactions that were stored and forwarded. Use “No” to retrieve data only for transactions that were not stored. Use “All” to retrieve data for all transactions whether stored or not. If this tag is not supplied, “Yes” is the default.
Using all defaults, the BatchReportQuery will return transaction IDs for today’s stored transactions that were declined when forwarded. Transaction data returned for BatchReportQuery include <IdNo#> to uniquely identify each transaction, where # is a numeric value. Other response fields include …
- <Status#> - Approved, Declined, or Error
- <IsSAF#> - Yes or No
Using the <IdNo#> value, the BatchReportTransaction can be used to retrieve the detail information for the specific transaction. The value is sent in the <IdNo> tag. Transaction data returned for BatchReportTransaction include values from the BATCH or DECLINE table …
- <IsSAF> - Yes or No
- <Status> - A, X, V, Declined, Error
- <AcctNo> - truncated showing last 4 digits
- <ExpDate> - truncated
- <AccountSource> Swiped, Keyed, etc.
- <Purchase> - Purchase amount
- <Authorize> - Authorized amount
Integration documentation will be updated in the near future to include full examples with all XML fields. These new Admin functions can be implemented via DSIClientX or dsiPDCX. No cardholder data is collected since these are Admin functions.
New build released 1/29/19 - Change to store and forward logic which will allow PreAuth/EMVPreAuth transactions to be captured even if stored records exceed the maximum time length. This prevents a situation where PreAuth/EMVPreAuth transactions must be captured prior to forwarding but can't be