PULL Method

Process flow

Pull method allows you to send a request via PCI Proxy to a Channel API endpoint to receive a response where the payload is filtered for credit card data and automatically tokenized. Just add the specified header parameters to your request and redirect your request to the /v1/pull endpoint. All other headers and your payload will be kept and routed through PCI Proxy without modification.

Process Flow with PCI Proxy

post
PULL method - API request

https://sandbox.pci-proxy.com/v1/pull
Request
Response
Request
Headers
x-cc-merchant-id
required
string
Your unique merchant id at PCI Proxy (e.g. 1000011011)
pci-proxy-api-key
required
string
Your API Key (ynTIoCUuUnlHkbW460eZb0zr4WBL0ntg)
x-cc-url
required
string
API endpoint (https://api.channel.com/)
Response
200: OK
Response will contain tokenized credit card data.
<?xml version="1.0" encoding="UTF-8"?>
<reservations>
<reservation>
<customer>
<cc_cvc>xC80dmLNReahfVnMNeW6DHt_</cc_cvc>
<cc_expiration_date>07/2018</cc_expiration_date>
<cc_name>John Doe</cc_name>
<cc_number>AAABcHxr-sDssdexyrAAAfyXWIgaAF40</cc_number>
<cc_type>Visa</cc_type>
</customer>
<truncated>...for better visibility</truncated>
</reservation>
</reservations>

Masked card number will be returned in the response as HTTP headerpci-proxy-masked-aliases AAABcHxr-sDssdexyrAAAfyXWIgaAF40=424242xxxxxx4242

In test mode, only test credit cards are allowed.

Example

Once a PULL Channel is added to your merchantId, simply redirect requests to it via the PCI Proxy:

Pull reservations from Booking.com
Response
Pull reservations from Booking.com
curl https://sandbox.pci-proxy.com/v1/pull \
-H 'x-cc-merchant-id: merchantId' \
-H 'pci-proxy-api-key: MfJag98oHh0rCiSXc8g3mCsqP8wrSer7' \
-H 'x-cc-url: https://secure-supply-xml.booking.com/hotels/xml/reservations' \
-d '<?xml version="1.0" encoding="UTF-8"?>
<request>
<username>providermachinelogin</username>
<password>********</password>
</request>'
Response
<?xml version="1.0" encoding="UTF-8"?>
<reservations>
<reservation>
<booked_at>2016-06-01T11:57:22+00:00</booked_at>
<commissionamount>21.09</commissionamount>
<currencycode>EUR</currencycode>
<customer>
<address>Vista 2, 3º izq</address>
<cc_cvc>xC80dmLNReahfVnMNeW6DHt_</cc_cvc>
<cc_expiration_date>07/2018</cc_expiration_date>
<cc_name>John Doe</cc_name>
<cc_number>AAABcHxr-sDssdexyrAAAfyXWIgaAF40</cc_number>
<cc_type>Visa</cc_type>
<city>Madrid</city>
<company />
<countrycode>es</countrycode>
<dc_issue_number />
<dc_start_date />
<email>[email protected]</email>
<first_name>Juan</first_name>
<last_name>Valdez</last_name>
<remarks>Booker is travelling for business...</remarks>
<telephone>666 428 664</telephone>
<zip>28004</zip>
</customer>
<!-- remaining response has been truncated for better visability -->
</reservation>
</reservations>

The response from Booking.com is automatically filtered for credit card data. Located card data is now stored in our vaults in Switzerland while card tokens have been inserted into the payload.