Upgrade guide — v20 to v21 — Payments

Skip this section if you are not adopting a new payment gateway or changing payment configuration, and if you do not use Zippay.

Refund support

Review: Multi-gateway refund support

v21 extends refund support to a wider range of payment gateways. Refunds can now be initiated from within StoreConnect for the following additional providers:

These gateways previously required refunds to be processed directly in the gateway’s own portal or back-office system.

Review your current refund process for each gateway your store uses. If you have manual steps or external processes for initiating refunds, assess whether those can now be replaced with the built-in StoreConnect refund flow.

Existing gateway changes

Review: CyberSource Message Level Encryption

CyberSource now supports Message Level Encryption (MLE), an additional layer of encryption for payment data in transit between StoreConnect and the CyberSource API.

If you use CyberSource, contact your CyberSource account manager to determine whether MLE is available for your account and what configuration changes are required on the gateway side before enabling it in StoreConnect.

See CyberSource Payment Provider for configuration documentation.

Action required: ZippayAu replaces Zippay v1

The legacy Zippay v1 API integration has been replaced with ZippayAu. This affects both web store and POS Zippay configurations. Existing Zippay v1 credentials will not work after upgrading to v21.

1. Contact your ZippayAu account manager to confirm your credentials are compatible with the ZippayAu API.
2. In the StoreConnect Config app, navigate to your payment provider configuration and update your Zippay integration to use the ZippayAu provider.
3. Test a Zippay transaction on your web store and, if applicable, at the POS to confirm the new integration is working before going live.

If you do not use Zippay, no action is needed. See Zip Pay Payment Provider for configuration documentation.