Implementation Options

Get an overview of the different ways you can implement ShieldConex.

Before you dive in, there are a few things you should know.

Code Languages

Any language that can make a Rest API request in JSON can write to ShieldConex. All of our sample requests are in Node.js.

Two Implementation Methods

Detokenization is always performed via API so that you can isolate code changes within your Data Access Layer, but there are 2 ways for you to implement data tokenization with ShieldConex. Like detokenization, you can perform tokenization using only the API, but we also provide a path using the Secure iFrame. This way, you don't have to worry about protecting data from the points of entry to tokenization – we host the data intake and you fetch the resulting tokens from us via API. For more information, take a look at the iFrame Tokenization guide.


Regardless of your implementation method, you'll need to implement API authentication. For testing purposes, you can use RSA or basic API authentication, however in the production environment, the use of HMAC authentication is required so that we can provide the most secure solution possible. We've put together an Authentication Guide outlining exactly how to set it up so you can start making secure calls with very little time or effort.