Pull
You make requests to third-parties and receive their filtered responses.
The merchant initiates a call to a Channel through PCI Proxy.
For Pull requests to channels, you are requesting potentially sensitive information from third-party partners. The channel sends its response through us and you will receive a tokenized version of it.
In sandbox mode, only test credentials are allowed.
Example
The Booking.com Pull (Channel) integration has been added to your account and you can then request booking information from them.
curl --request POST \
--url 'https://sandbox.pci-proxy.com/v1/pull' \
--header 'pci-proxy-api-key: {{pciProxyApiKey}}' \
--header 'x-cc-merchant-id: {{merchantId}}' \
--header 'x-cc-url: https://secure-supply-xml.booking.com/hotels/xml/reservations' \
--data '<?xml version="1.0" encoding="UTF-8"?>
<request>
<username>providermachinelogin</username>
<password>********</password>
</request>'
<?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 visibility -->
</reservation>
</reservations>
The cc_number and cc_cvc fields have been substituted with their corresponding tokens but rest of the response is the same. The raw text fields are stored in our vaults.
Updated 10 months ago