Token Replacement
Token Replacement to FTPS
Replace card tokens in a document and upload the result to an FTPS server.
PUT
File Transfer Token Replacement Guide
Replace tokens with card data in FTPS file transfers
Error Responses
Parameter Constraints
- serverAddress: Format is
hostnameorhostname:port. Only one colon is allowed. Default port is 22. - 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
Recommended. A long-lived token for browser-side calls. How to generate.
Alternative. Valid for 5 minutes. How to generate.
Path Parameters
The FTPS server address. This can be an IP address or domain name. Add the port number with a colon if required. For example:
fsgatewaytest.aexp.com:22 or 10.200.1.10.The folder path where the file should be uploaded to. This can be an individual folder or a full path.
The file name for the content being uploaded, including extension. For example:
PCIBTST.xml.Query String
Indicates the format of the file being sent. Read more on Supported Formats.
The timeout, in seconds, for the FTPS server to respond.
Headers
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.
The authorization parameter used to authenticate to the FTPS server.
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. PCI Booking replaces any token placeholders with real card data (based on thefilter format), then uploads the result to the FTPS server.

