All Tools
Tools/Wallet Provisioning Inspector
👛
UtilitiesBeta

Wallet Provisioning Inspector

Identify and check the payloads behind adding a card to Apple Pay and Google Wallet from an issuer app: Apple's PKAddPaymentPassRequest, Mastercard IIDD / Opaque Payment Cards, push account receipts, Visa JWE fields, Google UAPP (OpenPGP) and app-to-app ID&V.

Follows Apple PassKit in-app provisioning · Mastercard MDES / Token Connect OpenAPI·verified Sep 2026— structural checks only; Visa and Google formats from their public samples and docs

Examples use the documented field shapes with test card numbers and random bytes. Nothing is decrypted or sent anywhere — these payloads are encrypted for the network token service.

How these fit together

The issuer's app never encrypts card data on the phone. Its backend (or processor, or the network) produces an encrypted card for the network token service — Apple's encryptedPassData, or an Opaque Payment Card for Google Wallet — plus an authentication value that lets the network approve on the green path. Step through both flows in the wallet provisioning guide, and see how the resulting tokens are used in token cryptograms.