---
title: "Fetch activation payload for Apple Pay in-app verification"
method: POST
path: "/v1/cards/{card_id}/tokens/apple/verify"
tags: ["Push provisioning"]
---

# Fetch activation payload for Apple Pay in-app verification

`POST /v1/cards/{card_id}/tokens/apple/verify`

Call this endpoint to initiate an in-app verification for activating a token on Apple Pay.<br> **Note:** This endpoint follows the **Method A: Cryptographic OTP** process according to the Apple Pay developer documentation.  It will also trigger the change request process. The customer will receive a 2FA challenge to confirm the request.<br> The successfully completed Change Request will return an `activation_data` payload in the API response. You must then submit this payload in a separate request to the Apple Wallet. Please check the Apple Pay developer documentation for more details.

## Path parameters

- `card_id` string, required

## Response `200`

Redirect to Change Request

- PushProvisionChangeRequestResponse
  - `id` string — ID of the change request.
  - `status` 'ACCEPTED' | 'AUTHORIZATION_REQUIRED' | 'CONFIRMATION_REQUIRED' | 'COMPLETED' | 'FAILED' — The current status of the change request.
  - `updated_at` string, date-time — UTC timestamp from the last time the change request was updated.
  - `url` string — URL to use to authorize the change request.

## Other responses

- `201` — Successful result of the operation.
- `401` — Unauthorized. Authentication is missing or invalid.
- `403` — Forbidden
- `404` — The card could not be found.
- `500` — Internal server error.

---

[API](https://skmtc.net/solarisgroup/apis/cards-tokenization.md) · [All operations](https://skmtc.net/solarisgroup/apis/cards-tokenization/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/solarisgroup/cards-tokenization/revisions/15f03804be72/schema)