PayConexDecryptxShieldConexTECS
Release Notes
Request SandboxContact Us
Back to All

ShieldConex® v1.22.0 - 11.3.2026

5 days ago by ReadMe API

ShieldConex 1.22.0 introduces FF1 format-preserving encryption for enhanced tokenization security, along with new limits on Partner ID and template reference lengths (32 characters maximum). The release includes various API improvements and portal usability enhancements. Existing integrations require no immediate action.

FF1 tokenization

ShieldConex 1.22.0 introduces FF1 tokenization and detokenization through tokenization templates v2.0. FF1 is a NIST-approved format-preserving encryption method that offers enhanced security for ShieldConex tokenization. Templates created from scratch use FF1 as their only tokenization scheme. The FF1 update also addresses token output handling and character-set configuration in predefined card templates and tokenization requests.

No immediate action is required for existing integrations. Customers who need a new FPE or FPT template can clone an existing v1.1 template. Before adopting FF1, review the input and idempotency requirements below.

Requirements and compatibility

FF1 requires values of at least six characters; shorter values are rejected.

For repeated tokenization of the same value to remain idempotent, keep both the idempotency group and idempotency key the same. Changing either can change the token returned. Idempotency does not carry across tokenization algorithms: moving from FPE or FPT to FF1 does not preserve the same tokens, and historical data is not migrated to preserve them.

BFID behavior is unchanged.

Template and iFrame updates

The template editor includes an idempotency group field that accepts a signed integer. FF1 idempotency keys are supported in Tokenization API requests and through the iFrame SDK. Existing workflows remain the same, with FF1 configuration differences centered on idempotency.

Partner ID and template reference limits

Newly created Partner IDs and template references may contain up to 32 characters. ShieldConex Manager and the Management API enforce this limit. Existing longer values remain unchanged and usable, including when updating other fields without changing those identifiers.

API and usability improvements

  • Fixed a size limitation issue with bulk tokenization requests.

  • Improved Management API and orchestration request handling, including validation of required partner and client fields and better error handling for invalid orchestration configuration IDs.

  • Improved portal usability:

    • Clearer report export filenames.
    • Dashboard content appropriate to the user's role.
    • Automatic browser and OS password-saving behavior.
    • Text wrapping for long orchestration results.
    • Refreshed portal styling.