How It Works
- Your system sends a PUT request to PCI Booking’s SFTP/FTPS relay endpoint, providing the destination host, file path, server credentials, and the file content with card tokens.
- PCI Booking applies a content filter to locate tokens in the file, retrieves the real card data, and substitutes it.
- The modified file, now containing real card data, is uploaded to the destination SFTP or FTPS server.
Supported File Formats
PCI Booking supports several preset content filters for common file formats:Need a file format that is not listed? Contact support with information about your third party and the file format, and we will add support for it.
Listing Tokens
Provide the tokens in theX-PciBooking-cardUri request header, as a comma-separated list, in the order the cards should appear in the file:
- If a card should appear multiple times in sequence, append the number of occurrences in square brackets immediately after its token. A card appearing once needs no count.
- If the header lists fewer tokens than there are card locations in the file, the last token is repeated for all remaining card locations.
When sending many tokens (hundreds, for example), list only the 32-character token IDs instead of full URIs:
Authentication
Destination server credentials (username and password) are passed via the HTTP Basic Authorization header on your relay request. PCI Booking uses these credentials to connect to the destination SFTP or FTPS server. Card tokens are specified in theX-PciBooking-cardUri request header.
The reverse operation is also available: you can download a file from an SFTP/FTPS server through PCI Booking, which tokenizes any card data found in the file before returning it to your system. See File Transfer Tokenization.
Next Steps
Token Replacement in Request
Send card data via HTTP proxy instead.
Use Tokens Overview
All detokenization methods.
Retrieve Card Details
Retrieve raw card data via API.

