What does the operator have to renew over time?

Both certificates. The merchant identity certificate and the payment processing certificate expire and must be renewed before they do, and every new merchant domain must be verified. For one merchant this is a calendar reminder. For an operator with hundreds of merchants and several processors, it is a lifecycle to run, which is why it belongs at platform level.

Two certificates, many domains

Apple Pay on the web depends on a merchant identity certificate, used to validate each payment session with Apple, and a payment processing certificate, used to decrypt the payment token. Both expire, on different schedules, and both must be renewed before they do. Every merchant domain also has to be verified, and re-verified if it changes.

Why this is a lifecycle

• For one merchant, renewals are two calendar reminders a year.
• For an operator with hundreds of merchants and several processors, there are many certificates with different expiry dates and different key owners.
• Processors differ in who holds the processing certificate and how the token is decrypted.

What a platform does

Tracks every certificate and domain with its expiry, renews ahead of time, re-verifies domains automatically and alerts when something fails. An expired processing certificate stops every Apple Pay payment for every merchant on that processor, so the lifecycle belongs at platform level with monitoring, not in a shared calendar. The same logic applies to Google Pay credentials and to other wallets that use certificates or keys.