How are you getting around this?<p>(<a href="https://developer.apple.com/passbook/getting_started_with_passbook.pdf" rel="nofollow">https://developer.apple.com/passbook/getting_started_with_pa...</a>)
Use of Apple-issued Certificates<p>All passes need to be signed with an Apple-issued certificate to be recognized by Passbook. Passes should only be signed by the entity that will be distributing the pass under its own name, trademark, or brand, and that entity’s information should match the information on the back of the pass. It should be obvious to users who the originator of the pass is based on the branding on the front of the pass, and that branding should be consistent with the contact information on the back of the pass.<p>If you want to hire a contractor to assist you in developing a pass, then you will need to add the contractor to your development team and the pass must still be signed by the entity that is distributing the pass under its name, trademark, or brand. Keep in mind that passes can only be accessed by apps developed using the same team account, and that have the appropriate entitlements. So if you intend to use a companion app in conjunction with your passes, be sure to use the same development team.
Just a heads up guys, you haven't changed the default URL for user activation - it currently points to <a href="http://localhost:3000/user/pM33mHzATCP8JiBA2cUL/activate" rel="nofollow">http://localhost:3000/user/pM33mHzATCP8JiBA2cUL/activate</a>
while it should be <a href="http://coupono.us/user/pM33mHzATCP8JiBA2cUL/activate" rel="nofollow">http://coupono.us/user/pM33mHzATCP8JiBA2cUL/activate</a>.<p>Hope this helps! :D<p>Also, great work.
Will do a followup blog post soon to explain the use cases and outline some known-glitches.<p>We are going to make this product even more awesome-er! (If that's the word! :) )