Challenges in Payment Software Upgrading

Written by

James Davis

Written by James Davis

Senior Technical Writer at United Thinkers

Author of the Paylosophy blog, a veteran writer, and a stock analyst with extensive knowledge and experience in the financial services industry that allows me to cover the latest payment industry news, developments, and insights. Read more

Reviewed by

Kathrine Pensatori

Reviewed by Kathrine Pensatori

Product Specialist at United Thinkers

Product specialist with more than 10 years of experience in the Payment Processing Industry. I help payment facilitators and PSPs solve their various payment processing issues. Read more

Adding new components to existing business solutions is always a challenge. A new component added to some business solution can either replace some older version of the same component, or perform some new functions. In any of the two cases some common problems (typical for merchant services industry) can emerge, no matter who develops the new component: internal development team from within the company, or some independent software vendors. In most cases the problems are associated with strategic planning issues, faced by entities, trying to implement new payment systems. If a business solution is upgraded by some external software vendor, there is often misunderstanding between representatives of the company and the software providers (or developers), resulting in new problems, which come to light only at the implementation stage.

Successful Implementation

Logistical issues, associated with implementation of the new payment solution, PCI compliance, certification, also have to be resolved at the initial phase of the project in order to ensure its successful implementation.

Read more about the challenges of upgrading of an existing business solution in the respective article on Paylosophy.