Payment Scheme Choice: EEA Checkout Rules
A co-badged EEA card means your checkout must let the cardholder pick the scheme, explain why on the page, and remember the choice on saved cards.
By Jeffrey Anderson

- Section 5.8.4.5 (ID# 0031057) applies to an electronic commerce merchant in the Europe Region accepting a card issued inside the EEA that supports more than one payment scheme, or more than one application of the same scheme. Co-badged cards are the obvious case.
- The checkout must present a clear and obvious choice of all payment methods, with supported cards, applications and wallets displayed consistently by name, product category and logo at the same visual quality, sizing and clarity.
- The selection mechanism must be clear. The rule names checkboxes and radio buttons as examples rather than requiring either.
- The checkout must explain why the cardholder is being asked to choose, on the same page as the payment details, in a size, font and style consistent with the rest of the page.
- Pre-selecting a preferred scheme is permitted, provided it is shown clearly as pre-selected and the cardholder can override it.
- That is the opposite of the dynamic currency conversion rule, where pre-selecting the DCC option is named as a prohibited procedure. Two adjacent settings, two different answers.
- Wallets get no exemption. Where card details are populated from a wallet application, a clear and obvious choice of scheme or application must still be presented.
- Saved cards carry four more obligations: save the selected scheme with the card, show it clearly, make it editable, and let the cardholder save the choice when paying or on a later transaction.
- Tokenization does not remove the display requirement. Where card details have been tokenized, the underlying scheme name and logo must still be shown, which makes scheme choice a stored attribute of the credential rather than a checkout-time decision.
Payment scheme choice is a checkout requirement most merchants selling into Europe have never built. If you accept a card issued inside the EEA that carries more than one scheme, your checkout has to let the cardholder pick which one to use, and the rule is specific about how.
Section 5.8.4.5 (ID# 0031057) of the Visa Core Rules and Visa Product and Service Rules applies in the Europe Region, specifically the European Economic Area. It is one of the more prescriptive interface rules in the book, and almost all of it is about not quietly making the choice for the customer.
When It Applies
The trigger is narrow and worth getting right before you build anything.
It applies to an electronic commerce merchant that accepts a card issued inside the EEA which supports more than one payment scheme, or more than one payment application of the same scheme. A co-badged card is the obvious case.
If no card you accept carries a second scheme, this does not reach you. If any does, your website, application or wallet has to comply in full.
The Checkout Has to Show the Choice
Four requirements govern the payment page itself.
The checkout interface "must present a clear and obvious choice of all payment methods", covering supported payment cards, payment applications and digital wallets.
On all payment pages, those methods must be "displayed consistently by payment scheme name, Product Category, and/or logo(s) with the same visual quality, sizing, and clarity". Equal billing, in other words. One scheme rendered small and grey next to another in full colour is the thing this forbids.
The selection mechanism "must be clear", and the rule names checkboxes and radio buttons as examples rather than mandating either.
And the checkout must explain itself. It has to present information on why the cardholder is being asked to choose, on the same page as the payment details, in a size, font and style consistent with the rest of the page. Burying the explanation in a tooltip or a separate help page does not meet that.
You May Pre-Select, but Not Decide
This is where the rule differs from its closest neighbour, and the difference matters.
A merchant with a preferred scheme may pre-select it. The rule says that preference "must be reflected clearly by showing that payment scheme or payment application as being pre-selected, but a Cardholder must be able to override this choice".
So pre-selection is permitted here, provided it is visible and reversible. Compare that with dynamic currency conversion, where pre-selecting the DCC option is named in the rules as exactly the kind of procedure that is prohibited. Same anti-default instinct, two different settings: currency conversion cannot be defaulted at all, scheme choice can be, as long as the customer can change it.
Getting those two confused in one checkout is easy, and they pull in opposite directions.
Wallets Do Not Get an Exemption
If the card details are populated from a wallet application, "a clear and obvious choice of payment scheme or payment application must be presented to the Cardholder".
That closes the obvious gap. A wallet that autofills a co-badged card and silently picks a scheme has made the choice on the cardholder's behalf, which is the behaviour the whole section exists to prevent. Whether the wallet is pass-through or staged does not change the obligation on the merchant.
Stored Cards Carry Four More Rules
The part most likely to be missed sits at the end, and it applies to any interface that lets a cardholder save a card for later.
When the card is added, the scheme the cardholder selected must be saved at the same time. The selection on the saved credential must be clearly shown and must be editable by the cardholder. The cardholder must be allowed to save their choice when paying or on a subsequent transaction. And if the card details have been tokenized, the underlying scheme name and logo must still be displayed.
That last one is the trap. Tokenization removes the card number from your systems, and it is tempting to let the scheme identity go with it. The rule says the opposite. A saved token still has to show the cardholder which scheme they chose.
Taken together these four turn scheme choice into a stored attribute of the credential rather than a one-time decision at checkout, which is a different piece of engineering from showing two logos on a payment page. It sits alongside the wider stored credential rules rather than inside them.
What to Check If You Sell into the EEA
Three things, in the order they are usually wrong.
Does the checkout present the choice at all when a co-badged card is entered, or does your gateway route silently. Silent routing is the default behaviour of most integrations and it is the thing the rule is aimed at.
Is there an on-page explanation of why the customer is being asked. The requirement is explicit about placement and about matching the rest of the page.
Does a saved card remember and display the scheme, and can the customer change it. If your vault stores a token and nothing else, that is a build, not a setting.
Merchants running cross-border acceptance often discover this rule during an acquirer review rather than before one.
FAQ
Who does this rule apply to?
An electronic commerce merchant in the Europe Region that accepts a card issued inside the EEA supporting more than one payment scheme, or more than one payment application of the same scheme.
Can I pre-select my preferred scheme?
Yes. The preference must be shown clearly as pre-selected, and the cardholder must be able to override it.
Is that not the same as the DCC pre-selection ban?
No, and the contrast is worth holding. Pre-selecting the dynamic currency conversion option is prohibited outright. Pre-selecting a payment scheme is allowed provided it is visible and the cardholder can change it.
Do the logos have to be the same size?
The methods must be displayed consistently by scheme name, product category and/or logo, with the same visual quality, sizing and clarity. Equal treatment is the standard.
Does a digital wallet checkout have to show the choice?
Yes. Where card details are populated from a wallet application, a clear and obvious choice of scheme or application must still be presented.
What happens to the choice when a customer saves a card?
It must be saved with the card, shown clearly on the saved credential, and be editable by the cardholder.
Does tokenization remove the display requirement?
No. If card details have been tokenized, the underlying payment scheme or application name and logo must still be displayed.
Where does the explanation of the choice have to appear?
On the same checkout page as the payment details, in a size, font and style consistent with the rest of the page.
Jeffrey Anderson, Merchant Placement Specialist
Merchant placement specialist at Gray Merchants. Jeffrey works directly with acquiring-bank underwriting teams across the firm’s 70+ banking relationships to place high-risk and hard-to-place businesses, structure multi-MID accounts, and keep flagged merchants processing. His writing draws on the placement files he works every week: what underwriters ask for, why accounts get declined, and what keeps an approved account open.