Vault Proxy

If you have read our Token Vault introduction page, you already know that Payrails offers multiple ways to use our Token Vault, as a standalone Token Vault or within the Payment Orchestration and processing with Payrails. If you would like to use Payment Processing module and want to know how to tokenize payment instruments in this module where the customer is facing a card form on a website or mobile app, you can switch to reading Tokenize payment instruments.

If you would like to use our Vault as a proxy solution, where you will receive or send sensitive data by using our PCI-compliant vault, this page will help you introduce the concept of proxy connections.

There are many use cases regarding where proxy connections are used. Here's a non-extensive list of examples:

• When the card data is not coming from the end-user on a checkout page but instead from a third-party entity, such as a travel agency, a hotel, or an airline.
• When the stored card data in our Vault is sent to payment processors or other PCI DSS-compliant third parties.

This guide describes Payrails' Vault Proxy feature, which solves these and many more use cases. This approach ensures compliance and security while keeping our merchants' systems outside the scope of PCI DSS requirements.

Like any of our modules, it can be used as a standalone product or integrated with the rest of the Payrails ecosystem.