What Is Apple Value Added Services (VAS)?
Apple Value Added Services (VAS) is Apple's contactless NFC communication protocol built on ISO/IEC 14443 Type A/B (13.56 MHz). It enables an encrypted pass payload (nfc.message, up to 64 bytes) stored in Apple Wallet on an iPhone or Apple Watch to transmit wirelessly when held near an Apple-certified contactless reader — without waking the screen to display a barcode and without accidentally charging an Apple Pay credit or debit card.
Required Prerequisites (Strict Compliance)
Important: Apple VAS is not turned on automatically when creating a Passinstance workspace or toggling an NDEF link. Because Apple restricts contactless Secure Element / PassKit NFC transmission at the iOS kernel level, every production Apple VAS deployment requires three mandatory components:
-
1
Apple NFC / Enhanced PassKit Entitlement Approval: Your organization must apply for and receive Apple's NFC-Enabled Pass Entitlement from Apple on your Apple Developer account (
developer.apple.com/contact/passkit/). Standard Apple Pass Type ID certificates without the NFC entitlement flag cause iOS to ignore thenfcdictionary insidepass.json. -
2
Passinstance NFC Certificate Request Workflow (
NFC entitlement request): Submit and track your NFC activation (POST /api/v1/certificates/nfc-requests) and pair reader devices (NFC Settings API) so your public encryption key binds cleanly to your.pkpassnfcdictionary. -
3
Apple VAS-Certified Reader Hardware: Counter or turnstile terminals must implement the Apple VAS protocol configured with the SHA-256 hash of your
passTypeIdentifierand the matching ECDH P-256 private decryption key.
NFC entitlement request Lifecycle & Statuses (NfcCertificateRequestStatus)
Passinstance tracks your workspace's Apple VAS entitlement request through the NFC entitlement request model (NfcCertificateRequestStatus):
Status (NfcCertificateRequestStatus) | Operational Meaning |
|---|---|
PENDING | Workspace has submitted an Apple NFC/VAS request; awaiting entitlement review and approval. |
APPROVED | Entitlement request approved; ready to issue/upload the NFC-entitled TYPE_NFC Apple certificate. |
REJECTED | Request declined or submitted Apple Team / Pass Type ID verification was incomplete. |
PROVISIONED | NFC-entitled Pass Type Certificate (CertificateType.TYPE_NFC) and encryption keys are active in Passinstance. |
Apple VAS & NFC Request API Endpoints (NFC Request API)
| Method | Endpoint Path | Permission Required | Description |
|---|---|---|---|
| POST | /api/v1/certificates/nfc-requests | certificates:manage | Creates a new NFC entitlement request (status: PENDING) using request payload. |
| GET | /api/v1/certificates/nfc-requests | certificates:read | Lists all NFC entitlement request records for your workspace. |
| GET | /api/v1/certificates/nfc-requests/:id | certificates:read | Retrieves details and current review status for a specific NFC certificate request. |
| POST | /api/v1/certificates/nfc-requests/:id/review | Platform Admin | Reviews/transitions request status (APPROVED, REJECTED, PROVISIONED) via request payload. |
| POST | /api/v1/nfc/test | Authenticated | Executes an NFC pass payload/configuration test for a template. |
Example: Creating an NFC entitlement request (request payload)
POST /api/v1/certificates/nfc-requests
{
"organizationName": "Phenix Roasters GmbH",
"appleTeamId": "9A8B7C6D5E",
"passTypeId": "pass.com.phenixroasters.loyalty",
"websiteUrl": "https://phenixroasters.com",
"useCaseDescription": "In-store loyalty tap redemption on NFC Terminal readers across 45 cafes",
"contactEmail": "nfc-admin@phenixroasters.com"
}
Response (201 Created):
{
"id": "nfcreq_01J9Z8A2B4C6D8E0F2G4H6J8",
"organizationName": "Phenix Roasters GmbH",
"appleTeamId": "9A8B7C6D5E",
"passTypeId": "pass.com.phenixroasters.loyalty",
"status": "PENDING",
"createdAt": "2026-11-15T12:00:00.000Z"
}
Need assistance scoping Apple VAS for a multi-store or access-control rollout? Contact Support or review NFC Pass Configuration and Compatible NFC Readers.
