# Upgrade guide โ€” v20 to v21 โ€” Payments Source: https://support.storeconnect.com/articles/upgrade-guide-v20-to-v21-payments ยท Last modified 21 August 2026 Skip this section if you are not adopting a new payment gateway or changing payment configuration, and if you do not use Zippay or eWay. ## 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: | Gateway | Notes | |---|---| | Adyen | Full refund support added | | ZippayAu | Replaces legacy Zippay v1 (see below) | | Windcave | Full refund support added | | Tyro | Full refund support added | | PayWay | Full refund support added | | CyberSource | Full refund support added, including pre-auth refunds | 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. ## Salesforce package changes ### Review: New fields on Payment__c Two new fields on `Payment__c` support the refund workflows added in this release. | New field | Purpose | |---|---| | `Linked_Payment_Id__c` | Lookup to a related `Payment__c` record, linking a refund payment to its original payment | | `Reason__c` | Text field recording the reason for the payment action, such as a refund reason | These fields are populated automatically when a refund is processed through StoreConnect. Review whether they should be added to your `Payment__c` page layouts. ## Existing gateway changes ### Action required: eWay API Mode value must be lowercase v21 replaces the eWay integration with a new implementation that adds 3DS2 support, subscription payments, wallet payments (Apple Pay and Google Pay), and express checkout. The new integration only sends payments to the live eWay environment when the Payment Provider **API Mode** field contains exactly the lowercase value `production`. Any other value, including `Production` with a capital P, causes every eWay payment to be sent to the eWay sandbox after the upgrade. When this happens, card payments fail at checkout with the message "We were unable to verify your payment!", and no transactions appear in your live eWay dashboard. Earlier versions accepted the value regardless of capitalisation, so a store that worked on v20 can break on v21 without any configuration change. Before upgrading: 1. Open each eWay Payment Provider record in the Web Console. 2. Check the **API Mode** field. 3. If the value is not exactly `production` in lowercase, change it to `production`. 4. Repeat for every eWay Payment Provider record, including inactive ones. After upgrading, place a test card payment and confirm it appears in your live eWay dashboard. See [Eway Payment Provider](eway-payment-provider) for configuration documentation. ### 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](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](zip-pay-payment-provider) for configuration documentation. --- ## Follow StoreConnect - [Email Newsletter](https://getstoreconnect.com/c/lp-newsletter) - [LinkedIn Newsletter](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7444956928444862464) - [YouTube](https://www.youtube.com/channel/UCngKdP2x8l1wcbAKW3tvU8g) - [LinkedIn](https://www.linkedin.com/company/storeconnect) - [X / Twitter](https://x.com/storeconnecthq) ## Popular Links - [Partners](https://getstoreconnect.com/partners) - [News](https://getstoreconnect.com/articles/news) - [Events](https://getstoreconnect.com/articles/events) - [Feature Comparison](https://getstoreconnect.com/how-we-compare) - [Download a free trial](https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FMkeKUAT) - [Book a Demo](https://getstoreconnect.com/contact) ## Documentation - [Help documentation](https://support.storeconnect.com/help-documentation) - [AI agents](https://support.storeconnect.com/ai) - [Videos & tutorials](https://support.storeconnect.com/videos-tutorials) - [Developer reference](https://support.storeconnect.com/developer-reference) - [Release notes](https://support.storeconnect.com/release-notes) - [Troubleshooting](https://support.storeconnect.com/troubleshooting) - [Trust Center](https://trust.getstoreconnect.com/) - [Status Page](https://status.storeconnect.com/) ## Contact - info@getstoreconnect.com - US +1 415 745 3230 - AUS +61 2 8365 2308 100 S Ashley Dr, Suite 600-2461 Tampa FL 33602-600 USA Level 22, Sydney Place 180 George Street Sydney, NSW, 2000, AUS --- StoreConnect Support โ€” https://support.storeconnect.com/articles/upgrade-guide-v20-to-v21-payments