The Recurly + PassKit integration makes it possible to issue and manage digital wallet passes based on subscription activity. Whether you want to deliver membership cards, digital perks, or customer loyalty passes, you can automate this process using Recurly events such as signups, renewals, or cancellations to trigger pass actions in PassKit.

Setting Up The Integration

To integrate Recurly with PassKit:

  1. First, create and publish your digital pass project in PassKit (e.g., membership, coupon, or loyalty card).
  2. Go to Settings > Developer Tools in PassKit to retrieve your API region, SDK host, port, and API prefix.
  3. Generate your API credentials to enable secure pass issuance and updates.
  4. In Recurly, use webhooks to monitor subscription events such as new subscriptions, renewals, cancellations, or failed payments.
  5. Use an automation tool (e.g. Zapier, Make) or your backend to receive the webhook data and forward it to PassKit’s API.
  6. Map subscription data (e.g., customer name, email, plan level, status) to the fields in your PassKit pass template.
  7. Optionally, configure PassKit webhooks to track pass activity (install, update, uninstall) and reflect this back into Recurly, your CRM, or internal tools.

This connection keeps your digital passes in sync with customer billing status without needing to manage it manually.

Common Use Cases

The Recurly + PassKit integration is great for subscription businesses that want a customer-facing digital layer.

  • Issue a digital membership pass when a new subscription is created
  • Upgrade or change the pass tier when a customer upgrades their plan
  • Update expiry dates or perks on the pass when a subscription renews
  • Revoke or mark the pass as inactive when a subscription is canceled or payment fails
  • Use Recurly data to trigger personalized welcome emails with pass links

This helps bridge your billing platform with a mobile-first customer experience.

Requirements

To use this integration, you’ll need:

  • A PassKit account with an active, published pass
  • A Recurly account with webhook access enabled
  • API credentials from the PassKit Developer Tools section
  • A way to handle webhook-to-API communication (e.g., Zapier, Make, or your own backend)
  • Matching data fields between your Recurly payload and PassKit template

You can start simple with one pass type or scale across multiple subscription tiers.

Support And Documentation

Helpful links for setup:

SDK and API Configuration Settings

Subscribe to PassKit Webhooks

Using Long-Lived API Tokens

Use these resources to map data and test end-to-end delivery.

Frequently Asked Questions

Can I Issue A Pass When A Customer Subscribes?

Yes. You can use Recurly’s new_subscription_notification webhook to trigger a pass creation.

What Happens If A Subscription Is Cancelled Or Fails?

You can automatically revoke or update the pass using Recurly’s cancellation or failed payment webhooks.

Can I Customize The Pass Based On Subscription Plan?

Absolutely. You can use the plan code or tier to assign different designs, perks, or pass types.

Can I Track If A Customer Installed Their Pass?

Yes. PassKit webhooks can track installs, updates, and removals and you can sync that data back into your system.

Can PassKit Update The Pass On Each Renewal?

Yes. You can use renewal events in Recurly to trigger an update to the pass like extending an expiry date or showing new balance info.