Processor Tokenization

By offering Processor Tokenization, Silverflow provides an API that safely stores sensitive card information and provides a unique key that can be used across the Silverflow platform to authenticate and authorize initial and subsequent recurring transactions. The goal and benefit of using Processor Tokenization is that the key replaces the card input object, which helps limit exposure to PCI-DSS requirements and minimizes the use of sensitive data in API calls while still enabling the functionality for recurring transaction sequences that the card networks provide.

This form of tokenization is commonly referred to as 'proprietary' or 'acquirer' tokenization. The provided unique keys can only perform actions on the Silverflow platform. This differs from Network Tokens, which can be processed with the acquirer-processor of choice. For more information on this, see our documentation on Network Tokenization.

When you want to store a card safely in our Token vault, you can obtain a processorTokenKey by posting the required card data to the /processorTokens endpoint.

The CVC is optional, as we also allow providing the CVC in the other endpoints, such as /3ds, /charges, and /mit. If the CVC is provided, the cvcPresent indicator is set to true.

The response to the Create a Card call also provides cardInfo, which allows you to determine whether a card is co-branded.

You can use a GET on the /processorTokens endpoint with the processorTokenKey as a path parameter to fetch the card metadata linked to the card stored under the processorTokenKey. This will result in

The lastActionDate on the response shows when this processorTokenKey was last used on the Silverflow platform. Processor Tokens with a lastActionDate longer than 12 months in the past will be archived automatically to ensure there is no stale card information on the platform. If you want to store cards longer than 12 months without using them, we encourage you to use our Network Tokenization functionality or enable Account Updater for the Processor Token.

It is also possible to manually archive a Processor Token on the platform. DELETE can do this with the processorTokenKey as a path parameter to the /processorTokens/{processorTokenKey} endpoint.