A telemarketing firm for multiple non-profits uses a third-party website to collect donations for their clients. The third-party website sent credit card information to the telemarketing firm’s custom SOAP/XML web service. The telemarketing firm stored the credit card information and delivered it to their clients via daily batch files.
Significantly reduce the telemarketer's PCI scope by completely removing the credit card account number from the telemarketer's data flow.
Auric provides a custom inbound SOAP proxy service that tokenizes the cardholder data as it is received.
- The Proxy intercepts the incoming SOAP request from the third-party service; and
- replaces the credit card account number with a token.
- The tokenized SOAP/XML request is transparently forwarded to the telemarketing web service.
- The only change required for the Inbound Edge Tokenization was that the third-party website switch the URL to which they posted the payment information.
- The telemarketing service also uses Auric’s Outbound Batch Detokenization service to securely translate and deliver full credit card information to their clients.
- This dataflow was part of a project to completely remove the telemarketing firm from PCI scope.
Inbound Data Flow
Inbound SOAP Proxy data flow.
- The Order Collection Service submits SOAP order transactions to the Auric SOAP Proxy Service.
- The proxy service extracts the credit card account number and sends it to the AuricVault® service.
- The AuricVault® service returns a token.
- The proxy service replaces the credit card account number with the AuricVault® token and then forwards the SOAP order to the Telemarketer’s web service.
The Auric custom Inbound Edge Tokenization service, along with a custom Outbound Batch Detokenization service completely removed the credit card data from the telemarketer’s data flow.
migrated the incoming SOAP HTTPS connection to the latest HTTPS protocol (TLSv1.2) before the telemarketer upgraded their services.
- Data Separation
- Custom PCI Proxy service