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 you need, how renewals process automatically, and why you must test the renewal not just the signup.
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.
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, 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