What does scheme readiness cover for wallets?
Apple Pay certificates live at company level, so every merchant account under that company enabling Apple Pay picks them up, and one renewal covers the whole set. Google Pay works from the contract itself: a gateway merchant ID and a merchant name, entered when the method is activated, with the fields appearing at that exact moment. The activation checklist catches a missing value ahead of your merchant.
In detail
Scheme readiness for wallets covers the configuration each wallet requires, placed where it is easiest to maintain.
Apple Pay
Apple Pay certificates live at company level. Every merchant account under that company that enables Apple Pay picks them up, and one renewal covers the whole set. For a merchant running several brands or markets as separate merchant accounts, that avoids managing certificates account by account and missing an expiry on one of them.
Google Pay
Google Pay works from the contract itself. It needs a gateway merchant ID and a merchant name, entered when the method is activated. The fields appear at that exact moment, so the person configuring the contract is asked for the values when they are relevant.
The activation checklist
The activation checklist catches a missing value before your merchant does. A wallet that is not fully configured does not reach checkout half working, which avoids a payment button that appears but fails.
Why it matters
Wallet payments depend on details that are easy to overlook: certificates that expire, identifiers that differ between environments, settings that must match the provider. Placing each at the right level and checking it at activation keeps wallets available at checkout without your team tracking them by hand.