|Max number of destinations in a Send request||25|
|Max number of outbound messages to return in a query||25|
|Max number of inbound messages to return in a query||25|
|eFolio maximum total file size||4 MB|
|eFolio supported file types||PDF, PS, GIF, JPEG, PNG, HTML, RTF, TIFF, TXT|
|TTL: Time To Live. The time frame of the messages left in the Property's inbound messages||9,999 seconds by default, if the user has not specified otherwise|
|Data saved in database timeframe - credit card data and security code||Current; no time limitation|
|Session timeout (IDLE timeout)||15 minutes|
|Supported browsers - card display form and card capture form||Latest version of Internet Explorer, Google Chrome and Safari|
List of allowed characters in the password
|4||#||Number sign, Hashtag, Octothorpe, Sharp|
|23||[||Left Square Bracket|
|25||]||Right Square Bracket|
PCI compliance guidelines state that CVV cannot be stored indefinitely. According to the compliance regulations, the CVV can only be stored until it is "used" - the definition of the CVV being "used" is based on your individual workflow.
In order to comply with the guidelines, we incorporate a CVV restriction policy which allows customers to set, with approved limits, the relay restrictions and storage period limits of the CVV that are stored in their tokens. This allows customers to match the CVV retention policy to their own individual workflows.
For more information, please read about managing CVV Restrictions.
PCI Booking does not limit customers on how long cards can be stored. Customers can keep cards in the system for as long as required based on their needs and requirements - regardless of and information in the card itself (for example, customer can keep storing cards that have expired).
PCI Booking offers customers the ability to delete stored cards on demand (using our delete method or automatically as part of the CVV retention policy.
Updated about 1 year ago