Have you already tried including it with your request to http://developer.apple.com/contact/passkit ?

What you actually need, may be what’s known as a „personalized pass“:https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/PassKit_PG/PassPersonalization.html#//apple_ref/doc/uid/TP40012195-CH12-SW2To enable the rewards enrollment, however, an NFC permit is required…https://developer.apple.com/contact/passkit/

Is there a reason you don't provide a string-dictionary with your pass which adapts the labels to the users language ?

We are talking about the logo on the upper left of your pass, right ?Then your logo.png is way too large. It’s supposed to be a max. width of 160px (won’t work on the watch otherwise…) and a height of 50px – with the double and triple scales respectively at max. 320 by 100 and max. 480 by 150 for 3x. This should nomally get you appropriate display across devices.To make sure you don't exceed the permitted file size for the pass as a whole, it may be helpful to run the resulting files through a lossless PNG-minifier like ImageOptim as well.

You, ahem, obviosly lack some documentation… ;-)https://developer.apple.com/library/archive/documentation/UserExperience/Reference/PassKit_Bundle/Chapters/Introduction.html#//apple_ref/doc/uid/TP40012026-CH0-SW1Here you shall find all required information on how to display various barcode fomats on al pass.

You will need to provide some metadata for wallet, so it can determine the right context to show your pass. The „foreseen“ way to do this, is to set up a personalized pass as rewards card:https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/PassKit_PG/PassPersonalization.html#//apple_ref/doc/uid/TP40012195-CH12-SW2for which you will require an NFC-approval by Apple: https://developer.apple.com/contact/passkit/This way it can automagically used with elegible NFC payments.Or – the easy way – you continue your approach, but will then need to provide some location context, such as a low-range bluetooth beacon at the cashier's desk.

I'm not exacly sure how the logged requests are supposed to match the defined webservice endpoints. Did you already set up a log endpoint for your web service ? It's really helpful to set this up FIRST !! (Though it is only described at the end of the documentation.) And: Try using millies as "tag". Our observation is, this tag may not be considered as "opaque" by wallets as described inside the docs…

What kind of notification did you define ?

Not sure if this can be done with Wallet alone; the scenarios I read about this far, all required transactional NFC (known as the Apple Value Added Services protocol). You may need to write an app to achieve this. (Or find someone who knows better…)

Passcodes are always generated by the respective wallet app at the time of displaying the pass. You can include your own string content with the pass file (and specify the type of code you want to have generated from it) for wallet to then display the appropriate grid code for your data – though you cannot include a pre-generated code graphic.Apart from that, you might be able to include your QR code with the strip pic – though this would likely mean violating most any compatibility and design requirements.

Assumed, there is an opening "{" as well at the beginning of the original document, I don't think it’s the JSON.Apart from guessing:- try a different barcode message- include the old "barcode"-field as a secure fallback on older phones (in addition to the array)If the pass is generated, but simply not added to Wallet: Check if your images may have exceeded the maximum file sizes.Hint: If you happen to run the complimentary web service as well, start by implementing the log endpoint. This usually delivers the most usable results (as Apple, in recent years, significantly reduced the details you can get from Console).

Wallet on iPhone validates a pass much stricter than Pass Viewer on Mac OS. Check you have a valid signature, no syntax error in the JSON and your image files don’t exceed maximum sizes (both in px and kb…). If you provide a PassKit Web Service as well, I highly recommend implementing the logger endpoint first – despite it’s described last in the docs.

There is a hidden field for user specific information inside a pass which can be read from iOS apps. But I’m not sure if its contents are among the data made available via NFC.