01Supported is not one answer
When a provider says it supports Apple Pay, the next question is: through which flow? Hosted checkout, server-to-server and redirect are separate implementations. A wallet that works on a provider's hosted page may not exist on its S2S API, and a white-label platform in the middle adds a third party whose support has to match.
I am leading an Apple Pay and Google Pay rollout across several providers behind a white-label processing platform. The first path to go live was Apple Pay through a checkout API, while other flows continued in development. Launching the path that is ready beats waiting for all of them.
02Questions to settle per provider
Who holds the wallet merchant registration and who decrypts the payment token: the merchant, the platform or the provider? This decides how much work lands on the merchant.
Is there a sandbox for wallets at all? Sometimes the only real test is a small live transaction, and the plan has to allow for that.
What are the transaction limits and country restrictions? They differ by provider, and for an iGaming merchant operating across markets they decide where the wallet can actually be offered.
How is the wallet configured on the platform: a separate endpoint or connector, and does routing treat it as its own method?
03Tell the merchant exactly one thing
Merchants do not need the provider landscape. They need one integration path, its limits, and the markets where it works. Everything behind that should be absorbed by the payments team, which is the point of having a platform.