ShieldConex v1.9 - 6.30.2022

Version 1.9 of ShieldConex brings new cross organization sharing capabilities and some additional enhancements to the new template editor introduced in the previous release.

New Features

Partner-Specific Token Sharing

ShieldConex can now specify permission sets to share tokens with a specific partner. A specific partner can be given Tokenize or Detokenize permission for a specific template. When it’s configured, it allows specified Partners to use their own keys and credentials to perform the specified actions via API.

To enable sharing between partners safely, the organizations involved first work with a Bluefin specialist and provide consent before they can become visible to one another in the UI. Once set up, this feature can be configured on a template basis by Partner Supervisor users.

From the template that you want to set access on, deselect “Allow Sharing” as that enables ANY ShieldConex partner to tokenize and detokenize given they have the correct template details. A specific partner can be given Tokenize or Detokenize permission for a specific template. That allows them to use their own keys and credentials to perform the specified actions via API.

12541254

Enhancements and Updates

Optional CVV and Expiration Date From Card Information Field

For v1.1 templates, the Card Information field now has additional options in it’s configuration page. You can remove CVV and Expiration date from the group so now it can be set to collect only Card Number.

Input/Output Format in the Custom Field

The Custom Input field now has a configuration option to specify an allowed input and output character set. The options are Numeric, Alphabetic, and Alphanumeric. This is particularly useful if you need your customizable fields to fully support idempotency.

Clear All Button for Search Setting

20482048

To make things simpler for our users, we’ve added an option to clear all search settings. This makes removing parameters easier and no longer required you to refresh the page.

Duplicate System Name Validation

System names are set for each field so that it can be referred to in a specific way in the code. While we have yet to encounter the issue in an enterprise setting, having the same system name multiple times in the same template will cause issues when calling the API. As a safeguard and convenience, this version of ShieldConex automatically checks for duplicates every time you save a new or edited field.

Bug Fixes

  1. Some characters such as the apostrophe were being disallowed in the v1.1 Address Line 1 and Line 2 fields. Any valid special character that can be processed by the security hardware are now permitted as part of the address.
  2. ANSII Sorting of Partners, Clients, and some other entities in ShieldConex will now be ordered Alphabetically instead. E.g. The sorting used to be A,B,C,a,b,c and will now be A, a, B, b, C, c