Migrate > Take the first steps after WebSphere Commerce migration
Migrate from a previous payment implementation
If you are migrating from a previous version of WebSphere Commerce, you can continue to use WebSphere Commerce Payments Multipayment Framework with cassettes. However, the recommended approach is to use payment plug-ins. Alternately, you can use WCPayments plug-in with cassettes.
The following table lists the methods to move from WebSphere Commerce Payments Multipayment Framework version 5.x to WebSphere Commerce Payments plug-ins. The recommended method is listed first.
Procedure
Choose a payment plug-in based on the previous implementation.
If you did not use the WebSphere Commerce Payments Multipayment Framework version 5.x , but you customized task commands (DoPaymentxxx) to communicate with a payment system, then you should write a custom plug-in. By default, payment policies used in previous versions of WebSphere Commerce are migrated to WebSphere Commerce version 6.x in compatible mode. For more information see, Convert custom V5.x payment task or policy command implementations to a payment plug-in.
- Migrate WebSphere Commerce Payments Multipayment Framework to v7 (compatibility mode)
Use WebSphere Commerce Payments Multipayment Framework in compatibility mode. By using compatibility mode, you can continue to use cassettes; however, we will not use the Payments subsystem. Consider using the WCPayments plug-in with cassettes instead of using the WebSphere Commerce Payments Multipayment Framework in compatibility mode.
- Migrate to the WCPayments plug-in
To use the Payment subsystem while maintaining the ability to use cassettes, you can migrate to the WCPayments plug-in.
Related concepts
Payments subsystem architecture