Hi, I believe App Clip provisioning is supported for Keys in Wallet, but it is best to just ask your Credential Manager if they support it.

Hi, I can’t help consolidate internal cases, but I’ve found the strongest chance of success comes when applicants engage directly with their VAS provider or reader provider to present a clear business plan to Apple. This should include launch and marketing strategy, rollout details, and alignment with VAS criteria, such as loyalty, store services, or basic membership use cases. Physical access isn’t part of VAS, and falls under a separate entitlement category.

Hi, Some features may require specific entitlements, such as an enhanced Passbook certificate (NFC Entitlement). If you do not see any information about it in the public developer documentation, it may not be available for general use.

Hi, I can’t help consolidate internal cases, but I’ve found the strongest chance of success comes when applicants engage directly with their VAS provider or reader provider to present a clear business plan to Apple. This should include launch and marketing strategy, rollout details, and alignment with VAS criteria, such as loyalty, store services, or basic membership use cases. Physical access isn’t part of VAS, and falls under a separate entitlement category.

Hi, passkit-generator is an external, third-party library and has no affiliation with Apple. If you’d like complete control over Wallet passes, I suggest generating the pass JSON and signing the manifest directly in your own implementation.

Hi, Some features may require specific entitlements, such as an enhanced Passbook certificate (NFC Entitlement). If you do not see any information about it in the public developer documentation, it may not be available for general use. Best regards!