Saved cards and tokenization

Tokenization lets a logged-in customer save their card at checkout and pay with one click next time. It is available on the Premium plan.

What is actually stored

Not the card number. When a customer chooses to save a card, Scotiabank stores it on their platform and returns a token, which is a reference with no value to anyone who steals it. Your site stores only that token, linked to the customer’s WordPress user account.

This means saved cards do not change your security position. Your database still holds no card data.

Enabling it

1. Confirm tokenization is permitted on your Scotiabank merchant account.
2. In the gateway settings, enable saved cards.
3. Test with a customer account, saving a card and then using it on a second order.

The requirement people miss

Saved cards need a customer account. The token is stored against a WordPress user, so a guest checking out has nowhere to attach it, and the save option will not appear.

If you want customers to use saved cards, you need account creation enabled at checkout. If your store is guest-checkout-only, tokenization will do nothing for you.

Where customers manage saved cards

Under My Account, then Payment Methods, customers can see their saved cards and delete them. Deleting removes the token from your site.

Block checkout

Saved cards work in both the classic checkout and the block checkout.