Collecting and exchanging payment information is a common reason to tokenize data. Here are some of the most popular scenarios for using TokenEx to protect sensitive payment data.
(TokenEx Solutions: Hosted iFrame, Vaultless Tokenization, Transparent Gateway)
In this instance, a company is collecting payment data on its website that needs to be sent to its payment services provider (PSP). The website uses a TokenEx Hosted iFrame to capture the sensitive credit card information. The iFrame allows the payment data to go directly to TokenEx so the sensitive info never goes through the company's systems. This minimizes its exposure to Payment Card Industry (PCI) scope and its compliance requirements. TokenEx returns the tokenized version of this data to the parent page for storage and future use. Finally, it detokenizes the payment information using the Transparent Gateway and sends it to the PSP.
(TokenEx Solutions: Hosted iFrame, Vaultless Tokenization, Fraud Services, Transparent Gateway)
Here, a company wants to do an additional fraud check on the transaction to minimize the potential for false declines and chargebacks. Payment data is collected on the website with the TokenEx Hosted iFrame. This payment information is sent to a fraud services provider to determine risk. If the transaction is evaluated as high-risk (according to the logic you've set up with your fraud provider), it will be declined. Otherwise, TokenEx will pass on the payment information to the PSP to complete the transaction via the Transparent Gateway.
Please contact us if you have additional questions on how the TokenEx platform can help you accept, secure, and transact payment data.
Updated 11 months ago