Skip to main content
PUT

File Transfer Token Replacement Guide

Replace tokens with card data in FTPS file transfers
Performs token replacement on a file and uploads the result directly to an FTPS server. Use this when your payment processor or partner requires batch file delivery over FTPS (FTP over TLS). PCI Booking replaces all card tokens in the file body with real card data before uploading.

Error Responses

Parameter Constraints

  • serverAddress: Format is hostname or hostname:port. Only one colon is allowed. Without a port, PCI Booking connects on port 22. Most FTPS servers listen on port 21, so you will usually add :21.
  • filter: Must be one of: GBT, SIMPLECSV, SIMPLEJSON, AIR, IUR, TADC, CSV. Case-insensitive.
  • Authorization header: Must contain valid Basic Auth credentials (username:password) for the FTPS server.

Parameters

Authentication

Access token or session token. This endpoint does not accept the API key. Generate a token with your API key and pass it as a query parameter. Send one of the two.
string
Generated on your side. Single use, and valid for up to 72 hours. How to generate.
string
Returned by an API call. Valid for 5 minutes, and can be used more than once within that time. How to generate.

Path Parameters

string
required
The FTPS server address: an IP address or domain name, optionally followed by a colon and the port. For example: ftps.gateway.com:21 or 10.200.1.10:21. PCI Booking connects with explicit TLS; implicit TLS (port 990) is not supported.
string
required
The folder path where the file should be uploaded to. This can be an individual folder or a full path.
string
required
The file name for the content being uploaded, including extension. For example: PCIBTST.xml.

Query String

string
required
Indicates the format of the file being sent. Read more on Supported Formats.
string
The timeout, in seconds, for the FTPS server to respond.

Headers

string
required
Comma-separated token values to insert into the file. Tokens should be listed in the order of their appearance. For tokens appearing multiple times, include the number of occurrences in square brackets. Full token URIs or bare 32-character token IDs are both accepted. If fewer tokens are listed than there are card locations in the file, the last token is repeated for all remaining locations.
string
required
The authorization parameter used to authenticate to the FTPS server.
string
Supported compression formats: gzip and deflate. Omit this header if no compression is needed.

Request Body

The request body contains the raw file content as text, in the format named by the filter parameter. The preset filter determines where card data belongs in that format; PCI Booking inserts the card details of the tokens listed in X-PciBooking-carduri, in order, then uploads the result to the FTPS server.

Response