Why
The first reason for migrating is the access to new development. All fresh features and capabilities are exclusively released to Digital Payments, and will not be available when using payment methods v1.
Likewise, new payment method additions like Google Pay, Apple Pay and Click to
Pay are only available when using the paymentOrder API, and can’t be set up as
individual payment methods.
The second reason would be maintenance. With an integration made towards v1 and each individual method’s unique API, when new functionality, changes in behavior or new instruments are introduced, they both come with their own separate need for maintaining the existing integration.
By switching to Digital Payments v3.1, you will eliminate the need for maintenance on multiple integrations due to the design of v3.1 and its one-size fits all structure.
How
Migrating from individual payment methods to Digital Payments v3 does require a full new integration. The good news is that even if you are working with a new (paymentOrder) resource, the integration is very similar to what you are used to with payment method integrations.
We still have support for both Seamless View and Redirect, and the payment flow is similar to payment methods – with authorizations, captures, cancellations and reversals.
Check in with the setup team to find out what needs to be changed in the merchant setup at our end, then head over to Get Started, and we’ll walk the steps with you.