We have been asked to help a client move from a dedicated server to a new virtual hosting plan on another hosting service. The web application is asp.net and uses Verisign Payflow Pro.

I understand we should be able to move the Verisign certificate. Are there any other consequences (payment gateway configuration) that we need to be aware of?

Thanks for any insight.

...Are there any other consequences (payment gateway configuration) that we need to be aware of?
This depends and the method you are using to send the transactions to the Verisign Payflow host. If you are using a COM or JAVA component, many hosting providers will not allow installing third party components on shared servers or charge a premium to do so, which is understandable. Other than this little gotcha, it should not be an issue. Good luck!

Thanks Steve, guess we will have to dig a little deeper. We've been invited to the party after the application was developed and deployed so have little information as to how it's configured. I'll have to check and see if Verisign has a .NET version of the gateway connector.

I believe you have to register the Payflow Pro com object on the shared server. When moving the certificate you have to make sure that you give the new host the backup file of the certificate. Please note that the two host server software (IIS versions) must match or the new host must be reverse compatible. Otherwise the backup may not work properly.

Also make sure that the new host has the TCP port open for the Payflow Object port. Otherwise the transactions won't hit the Payflow servers.

I hope this helps.

From what I understand VeriSign does not offer certificate re-issue if you didn't opt-in for the feature when you obtained the cert.