Using Vantiv Gateway and First Data Processor, disabling TLS v1.0 next month

This might be specific to NYC licensees but is anyone else dealing with First Data disabling TLS v1.0 next month? If so, did they or Vantiv provide any way to test your configuration to insure that CC processing will still function on Feb 15th with that change? I haven't had much luck getting any assistance with Vantiv. Any help or contacts would be much appreciated.

Parents
  • Adding an update here, we're a non-RAMP client running Tessitura v12.5.1.

    We've disabled TLS v1.0 in our DEV environment which is a single server running the full application, DB, App, IIS, and reporting. The Tess client passed UAT and successfully auth'ed CC using Vantiv's emulation site.

    In our QA environment, we've disabled TLS v1.0 on our app server(CC gateway) as well as our separate IIS server and we successfully auth'ed CC using Vantiv's emulation site as well. Regression testing here was also successful.

    We're planning to make the changes in our STG environment today which will be our first opp to test our site, TNEW, and Ingenico's. Will update with results.

Reply
  • Adding an update here, we're a non-RAMP client running Tessitura v12.5.1.

    We've disabled TLS v1.0 in our DEV environment which is a single server running the full application, DB, App, IIS, and reporting. The Tess client passed UAT and successfully auth'ed CC using Vantiv's emulation site.

    In our QA environment, we've disabled TLS v1.0 on our app server(CC gateway) as well as our separate IIS server and we successfully auth'ed CC using Vantiv's emulation site as well. Regression testing here was also successful.

    We're planning to make the changes in our STG environment today which will be our first opp to test our site, TNEW, and Ingenico's. Will update with results.

Children