Request and use Apple Pay Merchant Tokens (MPANs) to enable agents to initiate recurring or subscription payments without a present device

Steps

1. Configure your Apple Pay payment request to include a recurring payment configuration object; without one of Apple's recurring payment configurations in the request, Apple returns a DPAN (device-specific token) rather than an MPAN (merchant-specific token), which is device-locked and not suitable for agent-initiated recurring charges
2. Include a managementURL field in the recurring payment configuration pointing to a page on your site where the customer can view and revoke the recurring authorization; Apple requires this URL as part of MPAN issuance
3. Provide a tokenNotificationURL where Apple will POST lifecycle events affecting the MPAN (e.g., card update, suspension, revocation); your handler must update your stored token record in response to these events before the next billing cycle
4. Store the MPAN token (not the raw card number) in your vault alongside the associated cryptogram; when the agent initiates a charge, request a new cryptogram for each transaction using the MPAN — do not reuse cryptograms
5. Submit merchant-initiated transaction (MIT) indicators in your authorization request when the agent charges without the customer present; Apple Pay and the downstream card networks require MIT flagging for recurring charges that occur outside a customer session
6. Refer to the Apple Pay Merchant Integration Guide (March 2026 edition) for current field names and required parameters; Apple updates this guide with each major OS release and some field names differ from third-party documentation