My understanding is that MPAN is provided for any of the payment request types that support the tokenNotificationURL (deferred/recurring). If you omit the tokenNotificationURL from the request do you still get an MPAN (when supported by the banking network)? Or is it only if that property has a value? Is there a different way you are supposed to trigger an MPAN?
Hi @Jalley316,
You wrote:
If you omit the tokenNotificationURL from the request do you still get an MPAN (when supported by the banking network)? Or is it only if that property has a value? Is there a different way you are supposed to trigger an MPAN?
Omitting the tokenNotificationURL from an Apple Pay request does not prevent the generation of a Merchant Payment Account Number (MPAN), provided the banking network supports it. The tokenNotificationURL is an optional property used to receive life-cycle notifications about the merchant token, such as when the card issuer or user deletes it. It is not a prerequisite for the MPAN's creation.
To trigger an MPAN, you must include one of the following payment request types in your Apple Pay transaction:
- PKRecurringPaymentRequest (or ApplePayRecurringPaymentRequest for web)
- PKAutomaticReloadPaymentRequest (or ApplePayAutomaticReloadPaymentRequest for web)
- PKDeferredPaymentRequest (or ApplePayDeferredPaymentRequest for web)
When any of these request types are used, a merchant token is automatically requested by Apple and returned in the Apple Pay payload if supported by the issuer. If the issuer does not support merchant tokens, Apple Pay defaults to returning a Device Payment Account Number (DPAN).
To test any of these request types, use Apple Pay on the Web Interactive Demo.
Cheers,
Paris X Pinkney | WWDR | DTS Engineer
