Concepts

We introduce some keywords and concepts which we refer to throughout this documentation.

Filter Proxy

We sit between you and your partners so that sensitive data is filtered and the result is that you only receive tokens.

PCI Proxy sits between you and third-party partners.

Forward Proxy

When you need to send tokens out to partners, you can forward them through us and your partners will receive plain text values.

PCI Proxy will detokenize your data before it reaches third-party partners.

📘

Read more about Filter and Forward Proxies.

Integrations

For the majority of use cases, including Filter and Forward, PCI Proxy acts as a shield between you and sensitive data. This sensitive data may be coming from a third-party, or you may be wanting to send this data out. We refer to integrations as an association of your PCI Proxy account with another web resource. Here, we will refer to different types of integrations depending on who initiated them (you, the merchant, or the third-party), or what type of request it is.

Types of requests

We distinguish between two types of requests when talking about integrations.

📘

Pull requests are those that are initiated by you, the merchant.

You can send or receive tokenized data.

📘

Push requests are those that are initiated by a third-party.

The third-party can send or receive sensitive data.

Types of third-parties

Receivers

Receivers are third-party partners who receive sensitive data, for example, plain credit card numbers. Typically they will store this data and use it for a downstream purpose, for example, payment processing.

Channels

Channels are third-party partners that send out sensitive data. Often these are partners who aggregate other services, of which you may be a merchant of.

📘

Adding integrations can be done via the dashboard.

Check out Adding Integrations for more details.