PayConexDecryptxShieldConexTECS Platform
Release Notes
Request SandboxContact Us
Back to All

ShieldConex v1.19 - 7.17.2025

2 days ago by Patrick Dozier

This release introduces Network Tokenization with full API and iFrame support, adds time-based detokenization controls, enforces 2FA, and enhances orchestration with customizable BFID headers and improved logging.

New Features

Network Tokens

ShieldConex v1.19 introduces Network Tokenization, a powerful new feature that enables businesses to securely create, manage, and utilize Network Tokens for payment transactions. Network Tokens replace sensitive cardholder data with secure, tokenized representations that remain dynamically up-to-date with the issuing bank, reducing fraud risk and improving transaction approval rates.

With this release, ShieldConex now provides the ability to:

  • Provision a Network Token – Generate network tokens through integration with payment networks.
  • Retrieve Payment Credentials – Securely obtain tokenized card details, including cryptograms, for enhanced transaction security.
  • Get Network Token Status – Monitor network tokens to maintain control over tokenized payment data.
  • Delete Network Tokens – Support the right to delete and ensure your Network Token vault operates as efficiently as possible.

These capabilities are now available via API and integrated into the ShieldConex platform, ensuring a seamless and secure payment tokenization experience.

In addition to the Network Tokenization API, we added the following tools and functions to support your Network Token integration:

  • Accessibility Via the ShieldConex Tokenization API - Network tokens can be created as part of ShieldConex’s existing Tokenization endpoint and can be retrieved with a Cryptogram via our Detokenization endpoint, enabling streamlined integration and support for the ShieldConex iFrame
  • API Logging - Gain insight into specific API calls to accelerate integration
  • Summarized Reporting - Review summarized API activity to understand volume over time

Enhancements

ShieldConex Manager

Changes to the Time-Sensitive Detokenization Configuration

In ShieldConex 1.17, we introduced the ability to restrict the time frame in which tokens could be detokenized. This is configured in ShieldConex Manager’s Template Editor as an offset from the time of tokenization. We have simplified configuration and that time frame is now simply expressed in a matter of Years and Days.

Enforce 2FA and Update Login Frequency for ShieldConex Users

To enhance security, ShieldConex now enforces Two-Factor Authentication (2FA) and has updated login session durations to align with industry best practices.


ShieldConex Payment Orchestration

Add bfidHeaderName Field to Tokenization Actions

A new bfidHeaderName field has been introduced for tokenization actions, allowing custom header naming for BFIDs in response payloads. This means that ShieldConex Orchestrations can perform multiple tokenization events and return a BFID for each.

Log Settings Under Actions Do Not Overwrite but Add to Automated Masking Rules

Automated masking rules now include additional logging settings without overwriting existing configurations, ensuring data security.