Posted: July 10, 2024 at 2:39 pm
|
Is EE aware of these changes? Do Chase’s changes require the EE Chase add on to be updated? J.P. Morgan is continually improving products and services provided to clients. As part of its modernization agenda, the firm is transitioning to new Data Centers providing superior performance, increased security, and better overall service reliability. This migration will change underlying IP addresses and the certificate for URLs being moved. URL names will stay the same. VAR migrations start July 22, 2024, and production starts August 5, 2024. If you hard code IP addresses Add the new IP addresses to your allow list and keep the old IPs until after the migration. Note: Add the complete set of 3 IPs corresponding to the URL listed in the table below. If you cache IP addresses Add the new IP addresses and keep the old IPs until after the migration. Recycle servers. Note: Add the complete set of 3 IPs corresponding to the URL listed in the table below. If you use Certificate Pinning Upload the new certificate as outlined in the Connectivity Solutions section of the Developer Center. If you use NetConnect Keep Alive URLs Ensure your cookie size capacity can support a minimum of 1,000 bytes for the following URLs: netconnectka1.chasepaymentech.com Contact them immediately to make sure the appropriate Entrust Root Certificate Authority-G2 (Serial # 4a 53 8c 28) is installed in your trust store before 9/1/2024. If you received your POS terminal or e-commerce solution from your Corporate or Franchisor Head Office Expect a call to discuss the appropriate steps to update your software, if necessary. If you use your own application to accept payments Access the Developer Center where you can review detailed information on the new certificates and make any appropriate updates to your current solution. We’re here to help If you have any questions or need further assistance, please contact our Help Desk. For US and Canada Email Merchant.Support@chase.com |
|
|
Is EE aware of changes? Do Chase’s changes require the EE Chase add on to be updated? J.P. Morgan is continually improving products and services provided to clients. As part of its modernization agenda, the firm is transitioning to new Data Centers providing superior performance, increased security, and better overall service reliability. This migration will change underlying IP addresses and the certificate for URLs being moved. URL names will stay the same. VAR migrations start July 22, 2024, and production starts August 5, 2024. If you hard code IP addresses Add the new IP addresses to your allow list and keep the old IPs until after the migration. Note: Add the complete set of 3 IPs corresponding to the URL listed in the table below. If you cache IP addresses Add the new IP addresses and keep the old IPs until after the migration. Recycle servers. Note: Add the complete set of 3 IPs corresponding to the URL listed in the table below. If you use Certificate Pinning Upload the new certificate as outlined in the Connectivity Solutions section of the Developer Center. If you use NetConnect Keep Alive URLs Ensure your cookie size capacity can support a minimum of 1,000 bytes for the following URLs: netconnectka1.chasepaymentech.com Contact them immediately to make sure the appropriate Entrust Root Certificate Authority-G2 (Serial # 4a 53 8c 28) is installed in your trust store before 9/1/2024. If you received your POS terminal or e-commerce solution from your Corporate or Franchisor Head Office Expect a call to discuss the appropriate steps to update your software, if necessary. If you use your own application to accept payments Access the Developer Center where you can review detailed information on the new certificates and make any appropriate updates to your current solution. We’re here to help If you have any questions or need further assistance, please contact our Help Desk. For US and Canada Email Merchant.Support@chase.com |
|
|
Thank you, I will forward this to our tEEm for review and confirmation. thanks again for reporting this. |
|
|
Topic was closed with no news. Did EE need to make changes? Are there any outstanding issues to keep Chase payments working? Thanks |
|
|
Hi there, Can you please share a direct where you see the information about the changes in the Chase Paymentech? |
|
|
I received an email from Chase about security and url changes they were making and copied that into my previous question. That’s all I have. |
|
|
Hi there, My apologies for the delayed reply. I’ve merged the two threads together so that I can reference the reply in mine. I’m going to breakdown the details from the email included above and response n relation to Event Espresso but in short, if the changes are specifically those in the email I don’t think it relates to our integration. There is one exception which is the root cert, but even then that related to the server config rather than something within the EE payment method itself… more shortly.
We do not hardcode IP address into the payment method. So should be fine.
Nor do we cache them.
As far as I am aware, we do not use this feature within our payment method.
We do not use those URL’s.
This is the exception I mentioned earlier… however, it relates to the root certs installed on your server, most will already have the above cert and if not, you’d have likely un into other issues by now. Chase is requiring the use of the above cert, so if you server doesn’t have it installed it will fail when attempting payments. It not so much an issue we can fix within the EE payment method but the payments could fail from it…. but… if you server is maintained and kept up with updates this shouldn’t be a problem.
I’ve tried multiple times to gain access to the developer portal to see if there are any more details docs within there, but everything I do fails at some point or another and then I end up at a dead end or dead links. So whilst I know you’re looking for a a definitive answer on if the Chase payment method will continue to work, I can’t say for sure. But based on the info available it looks like it should as long as the server has the correct root cert installed (again, most will). |
|
You must be logged in to reply to this support post. Sign In or Register for an Account
