Miva Merchant PayPal modules and recent PayPal service upgrade announcement

[oliverands]

I received this message from PayPal via email this morning. Can someone from Miva comment on the status of the Miva PayPal modules re: this PayPal service upgrade?

Thanks.

________________________

PAYPAL SERVICE UPGRADES

***Please do not disregard this email. Failure to make necessary changes to your PayPal integration may result in an inability to make API calls and/or receive payments through PayPal. PayPal continues to make significant investments and improvements to its infrastructure to improve our performance, scalability and availability to our customers. These improvements sometimes require us to perform necessary site maintenance upgrades. These upgrades sometimes require merchants to make changes to or update their existing integration. Please make sure you are ready for this event by consulting with your technology team or individual(s) responsible for your PayPal integration. What’s happening? Because of a system upgrade, the following API endpoints are being updated: api.paypal.com api-3t.paypal.com svcs.paypal.com When is this happening? This event is scheduled for the following date(s) and time(s): Date: March 25, 2014 Time: 11:00 p.m. Pacific Daylight Time (PDT) Why is this happening? We are performing this upgrade to ensure more efficient services for PayPal API users. What do I need to do? Merchants integrated in the following non-standard ways with PayPal’s API calls will be impacted when we update the API endpoints: Merchants calling our APIs with a hardcoded PayPal API endpoint IP address rather than using DNS resolution. See section A below. Merchants using HTTP methods other than GET, POST, DELETE and PUT. See section B below. Merchants using the HTTP 1.0 protocol. See section C below. Merchants whose firewall is configured to allow incoming and/or outgoing traffic from only a specific set of IP addresses will need to reconfigure their integration. See section D below. ***If you are integrated with a partner or a cart, please visit this FAQ for more important information. Action items Your technical team or individual(s) responsible for your PayPal integration will need to examine your current integration and make necessary changes. Below are merchant action items for each of the impacts listed above: Merchants calling our APIs with a hardcoded PayPal API endpoint IP address rather than using DNS resolution Impact to your business: API calls will timeout or the merchant will encounter an internal error from their system Your call to action: Use DNS resolution to access our API endpoints and/or open your firewall to the new IP addresses which will be communicated Merchants using HTTP methods other than GET, POST, DELETE and PUT: Impact to your business: API calls will return HTTP/1.0 400 Bad Request or HTTP Error 405 Method not allowed Your call to action: Send the API requests using one of the allowed methods. Heartbeat calls using the HEAD method will not be allowed Impact to your business: API calls will return HTTP/1.0 400 Bad Request Your call to action: Merchants should update their code to HTTP 1.1 and include the Host header in the API request Impact to your business: API calls will error out for merchants whose system responsible for making API calls to PayPal is behind a firewall that uses Access Control List (ACL) rules, and restricts outbound traffic to a limited number of IP addresses. Your call to action: You need to update your firewall ACL to allow outbound access to a new set of IP addresses available here. Test your integration on Sandbox (the IP addresses for Sandbox API endpoints are listed here). Merchants using the HTTP 1.0 protocol: Merchants needing firewall changes to allow new IP addresses: To assist with any questions you may have, we have an FAQ available here. For additional details of this event, please refer to this blog. Please note that maintenance events can be postponed, rescheduled or cancelled so it’s important that you review this information periodically. If you have any questions, please contact PayPal Merchant Technical Services by filing a ticket; refer to LIVE API integration change in preparation for March 25. For real time system updates, please go to www.paypal.com/sitestatus. Thank you for your understanding. Sincerely, PayPal Keep up-to-date with the latest technical information on our new portal www.PayPal-Notify.com. The portal will give you everything you need to know about planned site maintenances, unplanned events, and site changes. Just sign up using your PayPal, Google, Yahoo or Facebook account login details.

[Rick Wilson]

Re: Miva Merchant PayPal modules and recent PayPal service upgrade announcement

We're working with PayPal on this. The only item that impacts us if them forcing http 1.1. Assuming we have to make a change for this, it'll be an Engine level change and not anticipated to be a module level change.

[oliverands]

Re: Miva Merchant PayPal modules and recent PayPal service upgrade announcement

Thanks Rick. If it turns out an engine-level change is required, will you somehow be proactively notifying users that an update needs to be applied, or will we have to stay tuned in somewhere to get that information once a determination is made?

[Rick Wilson]

Re: Miva Merchant PayPal modules and recent PayPal service upgrade announcement

If you're hosted with us, we'll auto update your engine automatically.

Otherwise watch the Forums for an Engine release announcement.

[lesliekirk]

Re: Miva Merchant PayPal modules and recent PayPal service upgrade announcement

Thanks for the update on this - I'm getting asked the same questions.

[Rick Wilson]

Re: Miva Merchant PayPal modules and recent PayPal service upgrade announcement

FYI - Of these changes the only one we have an issue with is HTTP 1.0 being retired, which for us to support HTTP 1.1 we have to make an engine change.