Payflow Application Migration
In the coming weeks, maintenance will be performed on both the production and pilot Payflow applications and databases in order to relocate these services from Phoenix to Salt Lake City. Similar to last year when we moved Payflow services from Denver to Phoenix, new IP addresses will be introduced and added to the domain name system (DNS) as the various migrations occur. If your integration with PayPal is through the practice of hardcoded IP addresses versus using DNS and/or through applying an access control list in your network firewall configurations, it is very important to review all of the scheduled activities to ensure that your business is prepared for the upcoming changes. As a result of the scheduled maintenances, various Payflow services will undergo a planned downtime during different timeframes. Please read below for specific details:
Payflow Production and Pilot applications will be migrated from Phoenix to Salt Lake City over the course of 4 weeks. There is no interruption in service expected as a result of moving these applications. If your integration uses hardcoded IP addresses and/or uses an access control list in your firewall configuration to allow connections to applications such as Reporting, PayPal Manager, XML Registration, etc, you will need to make necessary changes detailed in the special section below***. This will prevent you from losing connectivity if the Phoenix datacenter is pulled out of rotation. For more information on the new IP addresses, go here.
*********************************************************************************************
***A Special Notice to Organizations that Hardcode IP Addresses and/or use Access Control Lists in Firewall settings
Phoenix will switch from being our production site to our hot back-up site. One of our primary goals is achieving a seamless production environment where we can rotate between our hot back-up site and our primary datacenters without an interruption in service.
If your integration uses hardcoded IP addresses today, please ensure that DNS is used to connect to these URLs dynamically. If merchants do not use DNS, they will encounter an interruption in service when we switch Payflow services between our datacenters. In order to still lock down IP addresses that have access to the network, PayPal strongly recommends that instead of hardcoding IP addresses, merchants use DNS behind the firewall and use an access control list (ACL) in firewall settings to allow for the current and new IP addresses in the network as outlined in this bulletin. Please ensure that along with adding new IP addresses mentioned in the bulletin, IP addresses for the Phoenix datacenter also remain in the access control listing.
Because of this special notice, it is imperative merchants share this information with their networking team to determine what changes are necessary, if any, to support this upcoming datacenter migration. If necessary changes are not made, it could result in connectivity failures, latency with transaction processing or time-outs in processing requests.
*********************************************************************************************
The Payflow Pilot test environment, including the primary test database, will migrate to Salt Lake City. The migration is scheduled to begin at 11:30 PM PDT on August 9 and is expected to complete August 10 at approximately 3:00 AM PDT. For the most up-to-date information regarding the PILOT migration, please go here.
*****************************************************************
The following PILOT services will be impacted for approximately 30 to 60 minutes between August 9, 11:30 AM PDT (August 10, 7:30 AM BST) and 1:00 AM PDT on August 10 (August 10, 9:00 AM BST). *****************************************************************
Service/Application
Service interrupted
Processor Outages
For 30 to 60 minutes during the maintenance window, PILOT/TEST transactions sent for processing will fail. PILOT/TEST transaction requests will either fail with a communication error or return Result Code=-1 (Failed to connect to host).
The Payflow LIVE environment will migrate to Salt Lake City. The migration is scheduled to begin at 11:30 PM PDT on August 25 and is expected to complete August 26 at approximately 4:00 AM PDT. For the most up-to-date information regarding the LIVE migration, please go here.
Maintenance Start Time: August 25, 11:30 PM PDT (August 26, 7:30 AM BST) Maintenance End Time: August 26, 04:00 AM PDT (August 26, 12:00 PM BST)
The following provides the services and expected service interruption schedule:
*****************************************************************
The following LIVE services will be impacted for approximately 30 to 60 minutes between August 26, 12:00 AM PDT (August 26, 8:00 AM BST) and 2:00 AM PDT on August 26 (August 26, 10:00 AM BST). *****************************************************************
Service/Application
Service interrupted
PayPal Payments Pro accounts using a Payflow integration/SDK
For 30 to 60 minutes during the maintenance window, transactions sent for processing may:
· Return Result Code 19 (original transaction ID not found) or Result Code 99 (General Error) when ‘referencing’ transactions that were processed prior to the start of the migration. This includes performing Delayed Capture, Credit, Void, Inquiry, New Referenced Authorization and New Referenced Sale attempts. Transactions that received a Result Code 19 or Result Code 99 may be re-submitted once the migration activities have completed.*
· Return Result Code 19 (original transaction ID not found) or Result Code 99 (General Error) when ‘referencing’ transactions that were processed during the migration activities. This includes performing Delayed Capture, Credit, Void, Inquiry, New Referenced Authorization and New Referenced Sale attempts to transactions that were processed during the migration. Transactions that received a Result Code 19 or Result Code 99 may be re-submitted once the transaction being referenced has been loaded into the database. **
· Not be viewable in PayPal Manager or in any reports until the migration activities have been completed. **
Duplicate Suppression
For 30 to 60 minutes during the maintenance window, transactions sent for processing may receive the following in the API response:
DUPLICATE=-1 (-1 means that the database is currently down and no duplicate check was performed on the transaction).
*************************************************************************
The following application will be impacted for approximately 2.5 hours on August 26, 2012 between 12:00 AM PDT (August 26, 8:00 AM BST) and 3:00 AM PDT (August 26, 11:00 AM BST). ************************************************************************
Service/Application
Service interrupted
PayPal Merchant Manager https://paypalmanager.paypal.com
For approximately 2.5 hours during the maintenance window, your account will be accessible, but the following services will be unavailable:
· Virtual Terminal
· Recurring Payments
· Website Payments Pro Hosted Solution customization
· Create/View Payflow API credentials
*************************************************************************
The following applications will be impacted for approximately 4.5 hours on August 25, 2012 between 11:40 PM PDT (August 26, 7:40 AM BST) and August 26, 4:00 AM PDT (August 26, 12:00 PM BST). *************************************************************************
XML Reporting/Reporting API
For approximately 4.5 hours during the maintenance window, XML Reporting/Reporting API will be unavailable. Reports may be incomplete until August 26, 06:00 PM PDT (August 27, 2:00 AM BST), as the reports may not contain all transactions that were processed during the migration period. **