We’re reaching out to request assistance with an issue we’re seeing in our current payment workflow integration.
Our Sertifi system, which we use to collect guest credit card information, does not support CVV collection, storage, display, or retrieval at any point in the process. This is intentional and required for PCI compliance, as CVV data cannot be retained or accessed under any circumstances. CVV is only used at the time of authorization and is not stored after validation.
Despite this, it appears that the CVV field is still being requested within our PMS/payment flow. Since this requirement cannot be supported on the Sertifi side, it will need to be disabled or removed within the PMS configuration or payment settings.
Could you please help us identify where this CVV requirement is enabled and advise on how to disable it? If needed, we’re happy to coordinate with your technical team to review the configuration together.
Please let us know the next steps or if you need any additional information from our side.
Good afternoon,
We’re reaching out to request assistance with an issue we’re seeing in our current payment workflow integration.
Our Sertifi system, which we use to collect guest credit card information, does not support CVV collection, storage, display, or retrieval at any point in the process. This is intentional and required for PCI compliance, as CVV data cannot be retained or accessed under any circumstances. CVV is only used at the time of authorization and is not stored after validation.
Despite this, it appears that the CVV field is still being requested within our PMS/payment flow. Since this requirement cannot be supported on the Sertifi side, it will need to be disabled or removed within the PMS configuration or payment settings.
Could you please help us identify where this CVV requirement is enabled and advise on how to disable it? If needed, we’re happy to coordinate with your technical team to review the configuration together.
Please let us know the next steps or if you need any additional information from our side.
Thank you,
Christine