
The weekly produce order
Six in the morning, the same crates as last week. The chef taps reorder on the pass and the saved card does the rest before service starts.
Saved cards & 3DS2
A head chef reorders the same produce every week at six in the morning. With saved cards, the second order is one tap: the card was tokenised with the provider at the first order and only the token reaches Magento. Strong customer authentication runs when the rules say it must, and stays out of the way when they do not.
Why it matters
Returning customers pay in one tap. For consumables, B2B replenishment and subscriptions, that is where the margin lives.
No card number is stored, displayed or transmitted by your systems. That keeps you on the lightest self-assessment questionnaire instead of a full audit.
Staff charge a customer's saved card for a MOTO order with consent, so nobody writes a card number on a pad by the phone.
3DS2 challenges appear when regulation requires them and are exempted where it allows: low value, trusted beneficiary, merchant-initiated. Returning customers are not challenged for the sake of it.
How it works
When a customer pays and chooses to save the card, the provider vaults it and returns a token. Magento stores the token and the last four digits for display, nothing else.
The saved card lives on the customer account, available in the checkout, in the admin for MOTO orders, and for subscriptions or merchant-initiated charges the customer agreed to.
On the next payment the suite requests 3DS2 where required and applies the exemptions the acquirer allows, so most repeat orders complete without a challenge.
Customers see and remove their saved cards from their account; you can expire tokens and see which cards are on file from the admin.
Ways merchants use it
B2B buyers who order weekly, consumables and subscriptions, and any store where the second purchase matters as much as the first.

Six in the morning, the same crates as last week. The chef taps reorder on the pass and the saved card does the rest before service starts.

By eight the crates are at the back door. The order she tapped at six was paid on the saved card, invoiced to the restaurant's account and picked before the supplier's van left the yard.

What the saved card really buys is the evening: no phone call to the supplier, no card read out over the pass, no reorder left until tomorrow. The kitchen runs the service and the order runs itself.
What you need
Also in Payments Suite
Questions
With the payment provider, as a token. Magento holds only the token and the last four digits for display.
Yes. A MOTO order from the admin can be charged to the customer's saved card with their consent, without asking for the number again.
Yes. Because no card data touches your systems, you qualify for the lightest self-assessment questionnaire rather than a full audit.
Yes, from their account on the website. Deleting it removes the token; there is no card number anywhere to remove.
Yes. Merchant-initiated payments the customer agreed to, such as subscriptions or instalments, run on the saved token with the appropriate 3DS2 exemption.
The payments team will tell you plainly what switching this on involves for your store, and what it costs.