Proxies and Routing Data
VGS proxies provide a lightweight connectivity layer between your applications (e.g., mobile apps and websites), your servers, and third-party providers (e.g,. PSPs).
VGS proxies are configured by setting up routes that can tokenize, store, and transform data in your API payloads before it reaches your servers and after it leaves them. Along with tokenization and vaulting (storage), our proxy services have access to a full-featured, secure, event-driven computing layer, which allows us to offer highly versatile and scalable payment solutions.
You can configure a proxy route for inbound requests to your api endpoints or outbound requests to external services’ endpoints. You can apply tokenization and processing to both the request side payload and the response side payloads. To make it even easier, we have prebuilt template configurations for standard PSP integrations (e.g., Stripe or Adyen) and standard client-side integrations (e.g., Apple Pay or Google Pay).
All API requests sent through our proxy services have full observability through our observability tool suite.
VGS proxies route data for various data transmission protocols, including HTTPS, SFTP, FTPS, and SMTP. VGS Routes are payload-agnostic and can transform any binary or text-based payload, including JSON, XML, HTML, PDFs, and compressed files.
VGS can also handle transforming encrypted payloads through key sharing within our vault infrastructure or by integrating directly with your AWS KMS through our BYOK service.
We also support proxying device communications built on ISO8583 POS/ATM messaging standards and support proxying 3270 Mainframe and other telnet-based protocols.
HTTP Routing

Inbound HTTP Routes
VGS Inbound HTTP Routes set up VGS as a reverse proxy in front of your web service. You can selectively apply processing to requests to any endpoint on your service. If you only need to apply processing on a few endpoints, requests that do not match a configured endpoint are passed through to your host.
Learn how to set up an Inbound HTTP Route
Outbound HTTP Routes
VGS Outbound HTTP Routes set up VGS as a forward proxy between your internal applications and your third-party web services. Just as with Inbound HTTP routes, you can selectively apply processing to outbound requests to any endpoint on your third-party service.
Outbound HTTP Routes are implemented using an HTTPS Connect Tunnel, similar to a VPN connection, creating a TLS-encrypted tunnel through which HTTP requests are routed.
Learn how to set up an Outbound HTTP Route
SFTP Routes

VGS supports large files transferred from payment servicing providers that need to be tokenized using our SFTP proxying capability. You can set up our SFTP proxy in front of an SFTP service. The configured SFTP route can tokenize structured and unstructured data within the transferred files as they pass through the SFTP proxy to the SFTP server. VGS also supports FTPS for transferring files over SSL/TLS.
Learn how to set up an SFTP Route
Note: SMTP proxy sits in front of your SMTP service and is triggered by file submission - we can also schedule file processing and tokenization using our Managed File Tokenization (MFT) service.
SMTP Routes
VGS supports tokenizing emails coming into your email services through the SMTP protocol. VGS SMTP Routes utilizes pattern matching and structured payload searches to find information inside the SMTP request envelope, tokenizing and transforming the information before it forwards it to your email service, keeping your customer service email servers out of PCI scope. SMTP proxies can also be used to protect PII sent to your customer service emails.
SMTP Routes are an enterprise feature that requires you to contact VGS sales and support to plan an implementation.
ISO8583 Routes

ISO 8583 Routes intercept any ISO 8583 message and can optionally convert to a more user-friendly JSON-based payload in transit. ISO 8583 Routes are also paired with VPN Connections to allow VGS to handle all routing to and from any PSP or Issuer, including pre-established connections for most major providers, including those who require hardware routers.
ISO8583 Routes are commonly used in card issuing or payment-specific use-cases to allow customers to react to real-time payment messaging requests without incurring PCI scope.
ISO 8583 Routes are an enterprise feature that requires you to contact VGS sales and support to plan an implementation.
3270 Mainframe Routes
3270 Mainframe Routes secure the data being passed to and from mainframes to their operators. You can use these routes to integrate with legacy third-party systems without incurring any PCI scope.
ISO 8583 Routes are an enterprise feature that requires you to contact VGS sales and support to plan an implementation.
Last updated