Skip to content
Help Center Guide · Certificates & CredentialsOnboarding Phase 3
3 min readVerified 2026-11-16

Apple Wallet Certificates

Create a Pass Type ID in Apple Developer, generate a CSR in Passinstance, upload the signed .cer/.p12, and bind your certificate.

In This Guide

Interactive UI Walkthroughs

Open in 6-Phase Onboarding Guide

Inspect exact dashboard panels, controls, and zoomed callouts related to this guide.

Zoomed UI focus
Key UI elements

Template Settings — Signing & External IDs (Zoomed)

Review Signing certificate status, Wallet sort order, Published template state, and External ID uniqueness rules in the Settings tab.

Overview: Why Apple Pass Type ID Certificates Are Required

Apple mandates that every production .pkpass archive be cryptographically signed using a Pass Type ID Certificate issued under your organization's Apple Developer Program account (Certificate Management API at /api/v1/certificates). The certificate serves two critical functions:

  1. 1
    Detached PKCS#7 Bundle Signing: Signs manifest.json inside every .pkpass archive (chaining to Apple's WWDR G4/G6 intermediate certificate) so iOS verifies authenticity and displays your verified Organization Name.
  2. 2
    APNs HTTP/2 Push Authentication: Authenticates TLS HTTP/2 connections to api.push.apple.com under the certificate's pass.com.<domain>.<name> topic so Passinstance can wake customer iPhones for live pass updates.
SYSTEM ARCHITECTURE FLOW
INTERACTIVE ARCHITECTURE
APPLE PASS TYPE CERTIFICATE PROVISIONING
STAGE 01 STEP 1: Generate Private Key & CSR inside Passinstance (Certificate Management API)
POST/api/v1/certificates/generate-csr
Generates 2048-bit RSA CertificatePkey (encrypted in encrypted storage)
Returns PEM-encoded .certSigningRequest (CSR)
STAGE 02 STEP 2: Apple Developer Portal (developer.apple.com)
1
Register IdentifierPass Type ID (pass.com.yourbrand.loyalty)
2
Create CertificateUpload Passinstance CSRDownload pass.cer
STAGE 03 STEP 3: Upload Signed .cer to Passinstance (POST/api/v1/certificates)
1
Parses X.509 .cer: Extracts passTypeIdentifier, teamIdentifier & expiry
2
Matches public key modulus against stored CertificatePkey
3
Validates trust chain against Apple WWDR G4 / G6 intermediate certificate
4
Bundles encrypted PKCS#12 (.p12) into encrypted storageStatus: VALID / ACTIVE

Prerequisites: You need an active Apple Developer Program membership (Account Holder or Admin role) to register Pass Type IDs and issue production Pass Type ID certificates. While Passinstance provides a managed sandbox certificate for initial onboarding demos, you must bind your own Pass Type ID certificate before distributing production passes to customers — Apple does not allow migrating already-installed passes to a different passTypeIdentifier or teamIdentifier after installation.

Step-by-Step Certificate Setup Workflow

  1. 1
    Generate a CSR in Passinstance: Navigate to Settings -> Wallet -> Apple Certificates (/settings/workspace/wallet) and click Generate CSR (calls POST /api/v1/certificates/generate-csr with optional passTypeId). Download the .certSigningRequest file. Passinstance stores the generated RSA private key (CertificatePkey) in encrypted storage.
  2. 2
    Register a Pass Type ID in Apple Developer: Sign in to Apple Developer Portal -> Certificates, Identifiers & Profiles -> Identifiers, click +, select Pass Type IDs, and register a reverse-DNS identifier such as pass.com.yourbrand.loyalty.
  3. 3
    Issue the Signed .cer in Apple Developer: Open your new Pass Type ID, click Create Certificate, upload the .certSigningRequest file downloaded from Passinstance, and download the resulting pass.cer file.
  4. 4
    Upload pass.cer to Passinstance: Upload pass.cer via POST /api/v1/certificates (multipart/form-data, optional teamIdentifier, passTypeId, demo, isNfcCertificate) or POST /api/v1/certificates/upsert (file + type: "TYPE_PASS" | "TYPE_NFC"). Passinstance links the .cer with the generated private key, verifies the Apple WWDR G4/G6 intermediate chain, and packages the encrypted .p12 signing bundle.
  5. 5
    Bind Certificate to Your Template: Open Template Settings and bind your verified Pass Type ID certificate.

Certificate Management API Reference (Certificate Management API)

MethodEndpoint PathPermission RequiredDescription
POST/api/v1/certificates/generate-csrcertificates:manageGenerates an RSA key pair (CertificatePkey) and returns a PEM Certificate Signing Request (.csr).
POST/api/v1/certificatescertificates:manageUploads an Apple-signed .cer file via multipart/form-data, verifies WWDR G4/G6 trust, and activates the certificate (CertificateType: `TYPE_PASS \TYPE_NFC`).
POST/api/v1/certificates/upsertcertificates:manageCreates or updates/renews an existing certificate from a signed .cer (multipart/form-data, optional pkeyId, type, intermediatePem).
GET/api/v1/certificatescertificates:readLists workspace certificates with passTypeIdentifier, teamIdentifier, validFrom, validTo, and status.
GET/api/v1/certificates/:idcertificates:readReturns X.509 metadata and details for a specific certificate ID.
DELETE/api/v1/certificates/:idcertificates:manageRemoves an unused or expired certificate.

Example: Generating a CSR & Uploading pass.cer

1. Generate CSR (POST /api/v1/certificates/generate-csr):

JSON
POST /api/v1/certificates/generate-csr
{
  "passTypeId": "pass.com.phenixroasters.loyalty"
}

Response (200 OK):

JSON
{
  "success": true,
  "data": {
    "csr": "-----BEGIN CERTIFICATE REQUEST-----\nMIICvDCCAaQCAQAwdzELMAkGA1UEBhMCREUx...\n-----END CERTIFICATE REQUEST-----"
  },
  "description": "CSR generated successfully",
  "errors": [],
  "statusCode": 200
}

2. Upload Signed .cer (POST /api/v1/certificates):

Submit as multipart/form-data with field file (pass.cer), optional passTypeId, teamIdentifier, and isNfcCertificate ("false" or "true"):

BASH
curl -X POST https://api.passinstance.com/api/v1/certificates \
  -H "X-API-Key: <API_KEY>" \
  -F "file=@./pass.cer" \
  -F "passTypeId=pass.com.phenixroasters.loyalty" \
  -F "isNfcCertificate=false"

Response (201 Created):

JSON
{
  "id": "cert_8841a9b0-2c3d-4e5f-8a9b-0c1d2e3f4a5b",
  "passTypeIdentifier": "pass.com.phenixroasters.loyalty",
  "teamIdentifier": "9A8B7C6D5E",
  "type": "TYPE_PASS",
  "validFrom": "2026-11-15T10:18:00.000Z",
  "validTo": "2027-12-15T10:17:59.000Z"
}

See Certificate Renewal & Management and Apple Wallet for lifecycle maintenance.

Ready to launch your first pass program?

Create your workspace, configure your pass template, and test a real pass in Apple Wallet and Google Wallet before you scale.