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: 09/10/2019
Support is added for EMV PreAuth, PreAuth and PreAuthCaptureByRecordNo. For a PreAuth, TSYS is sent a purchase transaction with a “HOLD”. If a merchant is a “hold capture participant” then NETaPay can include a “HOLD” tag in the authorization request. Including this authorization tag prevents the transaction from being captured and settled. For PreAuthCaptureByRecordNo, an adjustment transaction with the Reference Number is sent to TSYS with a “CAPTURE”. This will cause the held authorization to be released and will be captured during the next batch close. Note: If a merchant is not a “hold capture participant” and a “HOLD” tag is sent to TSYS, the host will reject the transaction and respond with "Not Allowed”.
If an Incremental Auth or Partial Reversal has been run following a PreAuth, then the amount captured must be exactly the final authorized amount. The final capture cannot have an additional TIP added or the purchase amount reduced.
Following the initial PreAuth, a TIP can be added to the capture. Also, following the initial PreAuth, a lesser purchase amount can be captured as long the <OriginalAuthorized> amount is sent with the capture.
The Batch Summary and Batch Close responses from TSYS reflect totals of transactions authorized, not settled. If a transaction is captured in a subsequent batch (the “HOLD” is removed), then the totals returned by the Batch Summary and Batch Close will not match the amount settled. If all transactions are captured prior to the Batch Close, then the totals returned by the Batch Summary and Batch Close will match the amount settled.
- The latest Store and Forward library is released with this version. Version 5.0 library prevents storing a transaction offline while an SAF_ForwardAll is in progress.
New build released 9/18/19 - Updated to use SAF library 6.0 to fix a critical stop error which can occur while forwarding without IP connectivity.
New build released 10/29/19 - Update to SAF library 7.0. This fixes a critical stop error which can occur where a forward contains a voided transaction with more than 1 child. This also corrects an issue where transactions may go online even though ForceOffline is set to "Y".