Saved cards and tokenization
How one-click repeat checkout works, what is actually stored, and the customer account requirement people miss.
Sell memberships and recurring products. What the bank must enable, how renewals process, how to find them in Merchant Admin, and what happens when one does not go through.
From version 2.6 the plugin works with WooCommerce Subscriptions, so you can sell memberships, subscription boxes, service retainers or anything else billed on a recurring cycle. This is a Premium plan feature.
When a subscription product is in the cart, the plugin saves the customer’s payment method automatically at checkout. There is no box for the customer to remember to tick.
The first payment goes through like any other. Every renewal after that processes on schedule in the background, with no customer interaction at all.
This matters more than it sounds. The common failure in recurring billing is discovering at renewal time that no payment method was stored, which means chasing the customer for card details and losing the subscription if they do not respond.
The signup is the easy part. Before going live, use the renewal tools in WooCommerce Subscriptions to trigger a renewal payment in sandbox and confirm it processes without customer interaction. A subscription that signs up cleanly but fails silently at renewal is worse than one that never worked.
From version 2.8, each renewal is sent to Scotiabank with its WooCommerce order ID, so you can find it under that order in Scotia Merchant Admin. The renewal order’s note in WooCommerce names the Scotiabank order ID as well. If you use an Order ID Prefix, it is applied to renewals too.
Two things can happen, and the plugin treats them differently.
Scotiabank declined it. The renewal order is marked failed and the order note shows the reason Scotiabank gave. WooCommerce Subscriptions then follows its own retry and customer notification rules, which you can configure in its settings.
Scotiabank did not answer in time. The renewal order is placed on hold, not failed, with instructions in the order note. This is deliberate. A renewal with no answer may or may not have been charged, and if it were marked failed, WooCommerce Subscriptions would retry it and could charge the card a second time. Check Merchant Admin for the transaction, then either mark the order as paid if the charge went through, or set it to failed so WooCommerce Subscriptions retries it if it did not.
Existing subscriptions keep renewing after a Premium licence expires. What stops is new subscriptions and new saved cards, which need an active Premium plan. Renewals also always run in the environment the original subscription was paid in, sandbox or live, regardless of the plugin’s current setting.
Recurring billing runs on the Fiserv primary token payment API, support for which shipped in version 2.5. Your site stores only a token reference; the card itself stays with Scotiabank.
How one-click repeat checkout works, what is actually stored, and the customer account requirement people miss.
What works on classic and block checkouts, and what to retest if you switch between them.
Every setting on the gateway configuration screen, section by section, what it does, and which plan it needs.
Still stuck? Professional and Premium licence holders get priority support, answered from Trinidad and Tobago.
Contact support