Upgrade guide — v20 to v21 — Subscriptions and vouchers

Skip this section if you do not use StoreConnect subscriptions or vouchers.

Salesforce package changes

Review: Payment Method field on Subscription__c

Payment_Method_Id__c is a lookup to Payment_Method__c on Subscription__c. It is an alternative to the existing Payment_Token__c field, which stores the gateway token as plain text directly on the subscription record.

When Payment_Method_Id__c is populated, renewals use the token stored on the linked Payment_Method__c record instead of Payment_Token__c. This indirection means the token can be updated on the Payment_Method__c record without modifying the subscription itself, which is what enables features such as eWay 3DS token rotation.

Payment_Method_Id__c is populated at subscription creation when the gateway supports saving a payment method as a dedicated record. Subscriptions created through gateways that do not support this will continue to use Payment_Token__c and will leave Payment_Method_Id__c blank.

Review whether Payment_Method_Id__c should be added to your Subscription__c page layouts.

See Subscription Object Reference for full field documentation.

Action required: Voucher Log field changes

Two fields on Voucher_Log__c have been renamed or replaced in v21. Both old fields remain temporarily but must be migrated before they are removed in a future release.

Old field	New field	Notes
Event_Result__c	Success__c	Replaced by a boolean field
Reason_Code__c	Reason__c	Renamed to a picklist field

1. Salesforce reports and list views — search for any reports filtered or grouped on Voucher Log: Event Result or Voucher Log: Reason Code and update them to use Success and Reason respectively.
2. Flows and Process Builder — search for any automations that read or write Event_Result__c or Reason_Code__c on Voucher_Log__c records and update the field references.
3. Apex or API integrations — update any code querying or updating these fields by API name.
4. Liquid templates — if your theme or POS layouts reference voucher log fields, update to success and reason.

See Voucher Log Object Reference for full field documentation.

Review: Voucher activation deadline field

A new Activate_Before_Datetime__c date-time field on Voucher__c allows you to enforce a deadline by which a voucher must be activated. Vouchers not activated before this date and time cannot be redeemed.

Review whether Activate_Before_Datetime__c should be added to your Voucher__c page layouts. If your business requires voucher activation windows, assess which existing vouchers should have a deadline set.

See Voucher Object Reference for full field documentation.

Review: Plan Change Mode field on Product2

Subscription_Plan_Change_Mode__c (label: Plan Change Mode) is a new field on Product2 that controls how proration is handled when a customer changes subscription plan. Available options are:

• Prorate Immediately (default): charges the pro-rata difference at the time of the plan change
• Prorate on Renewal: adds the pro-rata difference to the next invoice
• No Proration: charges the full new price at the next renewal with no mid-cycle adjustment

Review whether this field should be added to your Product2 page layouts and whether any subscription products should use a non-default plan change mode.

Behavior changes

Review: Subscription delinquency tracking

v21 adds new fields to Subscription__c to track delinquency status. A subscription is marked as delinquent when it has missed one or more payment cycles. These fields are populated automatically and require no configuration.

Review your existing subscription reports and list views to determine whether delinquency data should be incorporated. If you have existing manual processes for identifying missed payments, assess whether the new fields can replace or supplement them.

See Manage Delinquent Subscription Payments for guidance on handling delinquent subscriptions.

Review: Voucher audit logging

StoreConnect now records changes to voucher records, capturing who made each change and when. This audit trail is available via the new Voucher_Log__c object and requires no configuration to activate.

If you have existing custom processes for tracking voucher changes, review whether they are still needed alongside the built-in logging.

See Voucher Log Object Reference for full field documentation.

Review: eWay 3DS subscription token rotation

eWay v2 subscription payments now support 3DS token rotation, allowing the stored payment token for a subscription to be updated as part of the 3DS authentication flow.

If you use eWay v2 for subscription billing, test your subscription renewal flow after upgrading to confirm tokens are being handled correctly.

See eWay Payment Provider for eWay configuration documentation.