Every new account starts on Pro for 30 days: all features, all image slots, lifecycle updates, and 100,000 passes a month. After that, keep Pro at the $39/month standard rate or stay free under 1,000 passes/month. No card up front, no auto-charge.

Yes, fully. One API call lands a pass in both wallets: Apple installs the signed .pkpass, and Google installs from a Save to Google Wallet link we generate for the same pass. Live updates and push work on both too. We re-sign and push to Apple over APNs, and update the Google object and push directly. One honest difference: Apple shows your custom message on the lock screen, while Google's update banner is generic and your text lives inside the pass.

No. One pass generation covers both platforms. A single POST /api/passes returns the signed Apple .pkpass and a Save to Google Wallet link for the same pass, and it counts as one pass against your plan, not one per wallet. Updates and push to both wallets are included in that same pass, so there are no per-platform fees.

Two things count: each pass you create with POST /api/passes, and each update that changes a pass with PUT /api/passes/<serial>. A card you issue once and refresh a few times over its life is the create plus each content change, not a new pass every month. Revoking a pass does not count.

Yes. Every pass gets a unique serial, returned as serialNumber in the JSON response and embedded inside the .pkpass file. PUT a new body to /api/passes/<serial> and the pass refreshes on every device it was added to, iPhone, iPad, Apple Watch, and Android. Identical bodies don't trigger a push and don't count against your quota.

The API response carries the signed .pkpass (base64 applePass) and a Save to Google Wallet link for the same pass. Forward them however you already reach your user: email, an "Add to Wallet" button on a confirmation page, SMS, or in-app. Or share the hosted pass page we host at /p/<serial>, which shows the right Add button for the visitor's phone, Apple on iPhone, Google on Android.