Upgrade guide — v20 to v21 — Payments
On this page
Skip this section if you are not adopting a new payment gateway or changing payment configuration, and if you do not use CyberSource, Zippay, or Afterpay.
The guide assumes you are on the latest v20 website release. Changes that already shipped in v20 patch releases are not repeated here.
Existing gateway changes
Action required: CyberSource offers more card networks by default
This applies only if you use CyberSource. The default card networks offered on the CyberSource card form are Visa, Mastercard, American Express, Discover, Diners Club, and JCB. The list is a filter in the customer’s browser only. It does not control what your CyberSource account accepts, so if your account is not enabled for one of the networks, a customer can select that card and be declined at authorization instead of being blocked at entry.
- Check with CyberSource which networks your merchant account accepts.
- If it does not accept all six, set
allowed_card_networksin the CyberSource payment provider’s API options to the networks you accept.
See CyberSource payment provider.
Action required: ZippayAu replaces Zippay v1
The legacy Zippay v1 API integration has been replaced with ZippayAu. Existing Zippay v1 credentials will not work after upgrading.
- Contact your ZippayAu account manager to confirm your credentials are compatible with the ZippayAu API.
- In the StoreConnect Config app, navigate to your payment provider configuration and update your Zippay integration to use the ZippayAu provider.
- Test a Zippay transaction on your web store 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.
Review: Afterpay sends line items and guards against a changed cart
Afterpay checkouts send itemized product lines and discounts, Click and Collect orders send the pickup outlet’s address, and a customer who changes their cart in another tab after starting an Afterpay payment is stopped from being charged a stale amount and told why on the checkout page. Afterpay refund request errors are reported. No configuration is needed.
Review: Windcave credentials and PayWay errors
Windcave accepts an api_key and api_secret pair as an alternative to the username and password credentials; both formats keep working. PayWay error messages are shown on the checkout form instead of failing silently. No action is needed.
Refund support
Review: Refund support for more gateways
Refunds can be initiated from within StoreConnect for these additional providers:
| Gateway | Notes |
|---|---|
| Adyen | Full support, and Adyen ACH with item-level refunds |
| ZippayAu | Replaces legacy Zippay v1 |
| Windcave | Full support |
| Tyro | Full support |
| PayWay | Full support |
| CyberSource | Full support, including pre-authorization refunds |
| NMI | Full and partial refunds |
Web refunds can also be issued to a customer’s account credit balance or loyalty points, refunds can be set to require approval before they are processed, and releasing or voiding a pre-authorization now creates a refund record. Review your current refund process for each gateway you use. If you have manual steps or external processes for initiating refunds, assess whether those can be replaced with the StoreConnect refund flow. See Processing refunds for web orders.
Pre-authorization and saved cards
Review: Multi-capture, more gateways, and per-product capture
A pre-authorized payment can be captured in several partial installments, each recorded as a Payment_Installment__c record linked to the original payment, with Preauth_Amount_To_Capture__c on Payment__c holding the amount to take. The preauthorize-then-capture flow extends to Braintree, Square, Adyen, and Authorize.Net. Payment_Capture_Type__c on Product lets a product choose Charge Immediately, Preauthorize Only, or Save Payment Method Only.
Saved cards are stored as Payment_Method__c records linked from Payment__c and Subscription__c. See Payment methods and Payment Installment Object Reference.
Review: 3D Secure on the payment link and additional payments
3D Secure authentication applies to Stripe and Adyen on the payment link and other additional payment flows. Stripe wallet payments on a pay-balance link, with Apple Pay, Google Pay, Link, or PayPal, return to the correct page and record the payment. No configuration is needed.
New payment gateways and options
Review: NMI, Flywire, and StoreConnect Pay
NMI is a new web gateway with ACH, subscriptions, 3D Secure 2, a configurable endpoint for regional deployments, and ACH bank fields that build correctly when the form starts hidden. Flywire is a cross-border tuition and fee gateway with multi-currency support. StoreConnect Pay is a provider for stores using StoreConnect’s hosted gateway, with card and ACH payments, and uses the same checkout templates as NMI. See NMI payment provider, NMI ACH payment provider, and Flywire payment provider.
Review: Westpac Online Pay 3D Secure 2
Westpac Online Pay supports 3D Secure 2 as an opt-in, enabled with the three_d_secure and threeds_contract_id options in the provider configuration, with device fingerprinting, a 3DS lookup, and an in-page challenge covering purchases, additional payments, and subscription billing. If you enforce a Content Security Policy with your own policy, allow the Cardinal Commerce challenge frames before enabling it. See Westpac payment provider.
Review: Vii gift cards on web checkout
Vii gift cards are accepted as a payment method on web checkout for stores integrated with the Vii platform. No configuration changes are needed for other gateways.
Salesforce package changes
Review: New fields on Payment and Payment Provider
The new fields on Payment__c are listed in the E-commerce section: Linked_Payment_Id__c, Reason__c, Origin__c, Payment_Method_Id__c, Preauth_Amount_To_Capture__c, and Salesforce_User_Id__c. Payment_Provider__c gains Channels__c, which limits a provider to the web store or the POS; blank means both. Payment transactions can carry a General Ledger code resolved from the product or cart, with TouchNet the first gateway to send it.
The Provider__c picklist on Payment_Provider__c gains eleven values that a package upgrade does not add to your org. Apply them with the Console’s Manage picklist values tool, as described in the E-commerce section, before configuring any of those providers.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.