The AuvProxy Service

The AuvProxy service is an edge tokenization service supporting inbound and outbound data protection over secure communications. Both tokenization and detokenization services are available.

The AuvProxy service supports several payment processors and Online Travel Agency (OTA) specifications.

The proxy supports both generic and custom tokenization and detokenization services.

The AuvProxy service from Auric Systems International is part of the AuricVault® family of products.

Contact Auric sales at sales@AuricSystems.com to discuss how a PCI/PII/PHI compliant proxy service like the AuvProxy can improve your security and reduce your compliance scope.

Edge Tokenization for Compliance

The AuvProxy edge tokenization service removes sensitive information (such as credit card account numbers) from data flowing into your business environment.

Likewise, the AuvProxy service can securely detokenize data as it flows out from your business environment.

This two-phase edge tokenization / edge detokenization allows you to process critical business information while maintaining security standards (such as PCI, HIPAA, etc.)

Terminology

This documentation describes all HTTPS requests in terms of a two-way conversation between Your Server and a Target Web Service. The AuvProxy sits in the middle of this conversation.

Pull Requests

Pull requests originate at Your Server. Your Server starts the transaction by POSTing an HTTPS request to the AuvProxy service.

_images/pull-overview.svg

The AuvProxy:

  • forwards the unmodified request to the Target Web Service; or

  • detokenizes or tokenizes the request before forwarding it.

The Target Web Service response flows back through the AuvProxy service, which:

  • returns the unmodified response to Your Server; or

  • tokenizes or detokenizes the response before returning it.

Push Requests

Push requests originate from a third-party service POSTing to Your Web Service through the AuvProxy service. In this instance, your web service is considered the Target Web Service.

_images/push-overview.svg

The AuvProxy:

  • forwards the unmodified push request to the Your Web Service; or

  • detokenizes or tokenizes the request before forwarding it.

Your Web Service response flows through the AuvProxy service, which:

  • returns the unmodified response to the Target Web Service; or

  • tokenizes or detokenizes the response before returning it.

Three Dataflows

The proxy service implements three dataflows:

  • Detokenize outbound pull requests to a Target Web Service

  • Tokenize pull request responses from a Target Web Service.

  • Tokenize inbound push requests from a Target Web Service.

Tokenize What Matters®

The initial proxy functionality focuses on payment card tokenization, but the AuvProxy tokenization and detokenization proxy service is adaptable to any data:

  • Personal Health Information (PHI)

  • Personally Identifiable Information (PII)

  • Credentials (tokenize the credentials you use with the Target Web Service)

Supported Data Formats

The AuvProxy can transform the following data formats:

  • HTML

  • JSON

  • Name/Value Pairs

  • SOAP/XML

Sandbox Environment

Auric provides a sandbox environment for you to use for development and testing. Please note that the AuvProxy sandbox environment is not PCI/PII/PHI compliant. Use only test data in the sandbox environment.

Firewalled Production Environment

The AuvProxy production environment has both inbound and outbound firewall restrictions, ensuring you know where your data is flowing.