PayConexDecryptxShieldConexTECS Platform
Release Notes
Request SandboxContact Us
Back to All

PayConex - 7.13.2021

over 2 years ago by Ryan Cox

Highlights from this release include the release of our PayConex Account Creation API, and RSAPI Pagination along with enhancements to IP blocking and Recurring Label options.

New Features

Automated Account Creation API
We have streamlined our merchant onboarding process so that the account creation process within PayConex is quick and seamless. This new workflow will be time-saving and will aid in the systematic creation of Merchant/Agent Accounts.

Pagination through our Reporting APIs (RSAPI)
We have enhanced our Reporting APIs to support large datasets. Clients integrated to us through these will now be able to break large datasets down into discreet pages & in an optimal way.

Recurring Label
Merchants that leverage our recurring plans will now be able to input or edit a ‘Recurring Label’ to identify different plans quickly.

IP Blocking
Historically our IP blocking functionality was not blocking IP addresses if the request had an api_accesskey.

You now have more flexibility and the option to allow IPs to be blocked even if the request came with an API Access Key. To take advantage of this feature, you need to enable IP Blocking under Card checking / IP blocking and set “Check Access Key Request” to “NO.”

  • If “Check Access Key Request” is set to No, & the API access key is received as part of the request, it won't check against these access rules.
  • If “Check Access Key Request” is set to Yes, it doesn't matter whether the API Access key is received or not; transactions will be subjected to the ‘IP Blocking’ set preferences.
630

If Check Access Key Requests' is set to Yes, then enabling this feature will also apply to the merchant's IP addresses. This could potentially impact processing from the Merchant's servers to PayConex. The IP Whitelist Management can be used to bypass the checks when transactions originate from the merchant's IP addresses. This allows Card Checking/IP Blocking to be applied to all transactions coming from the Internet except those originating from the merchant's servers. IP Whitelist Management is found under the “Tools” tab.

Here is a step by step on how to do that:

The Whitelist Status will have to be set to “Partial” and the IP addresses will need to be added to avoid triggering the IP Blocking tools against the valid addresses.

📘

Note

To unblock the IPs caught by the IP Blocking tool, merchants can access ‘Manage IP Blockist’ under the Settings Tab.

IP Whitelist Management
Our merchants can now utilize the IP Whitelist management tool in different ways:

  • Disabled - the whitelisting of an IP address will be ignored.
  • Partial – IPs listed can process; others will be subjected to IP blocking set preferences.
  • Full - only the IPs listed can process transactions.

This selection is available through the Whitelist status selection box.

682

📘

Note

Under the reports tab, we have a Whitelist Exceptions Report that shows traffic coming from addresses not whitelisted. This report is only visible if IP Whitelist Status is set to Full/Partial.

Custom Reports
We have added ‘ddds_protected’ as a new attribute on our Custom Reports. Our clients that have 3D Secure turned on can now report on this field.

Bug Fixes

Payment iFrames
Clients integrated to PayConex via iFrames were experiencing a Javascript error message on IE 11 or iOS13. This issue has been fixed & clients that are using older browsers should have a seamless experience.

TTech ACH Settlement File Discrepancies
PayConex sends a daily settlement file to TTech. Recently, a few of the Account and Routing numbers were being sent in a non-numeric value, causing reconciliation issues. We have added code that can identify such transactions & inform PayConex not to include those records in the settlement file.

Transaction Timeouts on Omaha
Merchants that use Omaha were experiencing an issue where the transaction seemed to timeout, whereas the actual problem was a delay in settlement. Therefore, we adjusted the code to make the settlement happen in the background so that the current transaction could continue.