Apple Pay

We are an acquirer/payment provider offering Apple Pay. Our merchants use our hosted checkout to accept payments. After a user pays with Apple Pay on our checkout, the Wallet transaction record shows our checkout domain as the payee. We would like it to display the merchant’s brand/name so users can recognize or contact the merchant. Is there any parameter or configuration that controls what Wallet shows as the payee? For example, can this be set via a specific field/parameter, or is it strictly derived from the Merchant ID’s display name (or other Apple Pay configuration)? What is the correct approach for a PSP/acquirer to have the merchant’s brand shown in Wallet transaction record?

Additional detail: The field in question is the merchant/payee name shown in the Apple Wallet receipt—directly under the transaction amount at the top of the receipt, and again beneath the “Total” line.

Answered by DTS Engineer in 893956022

Hi @ow-f,

You wrote:

[...] Is there any parameter or configuration that controls what Wallet shows as the payee? For example, can this be set via a specific field/parameter, or is it strictly derived from the Merchant ID’s display name (or other Apple Pay configuration)? What is the correct approach for a PSP/acquirer to have the merchant’s brand shown in Wallet transaction record? [...]

There are two completely independent UI surfaces that are frequently conflated:

  • Apple Pay payment sheet: Displays total.label from your payment request at runtime
  • Wallet transaction receipt: Displays merchant display name from the Apple Developer portal and card network clearing data.

Setting values in your ApplePayPaymentRequest at runtime doesn't affect the Wallet receipt. These are entirely separate mechanisms.

When you use a single shared Merchant ID for all your merchants, the display name registered against that Merchant ID in the Apple Developer portal is what Apple Pay and Wallet resolves at the moment of transaction. Since your Merchant ID is registered under your PSP's identity, your domain/brand appears for every transaction across all your merchants.

There is no API field to override the merchant display name or payee name in Wallet at runtime. However, there are two mechanisms to consider:

  • Developer portal display name. Resolved at the time of the merchant session validation (validateMerchant handshake). Immutable at runtime. Whatever display name is registered against the merchantIdentifier used in the request is what Apple records.
  • Card network clearing data (post-settlement enrichment). After settlement, issuing banks can retroactively update Wallet records based on enriched merchant data received through card network clearing messages. This is where a sub-merchant name can surface — but it is entirely outside of the Apple Pay API layer.

Important: This enrichment is highly issuer-dependent, not guaranteed, and not something you control through Apple's APIs. It depends on whether your acquiring bank populates the sub-merchant name correctly in clearing data, and whether the specific issuing bank has implemented Wallet record enrichment.

If you request and are granted approval for the Apple Pay Web Merchant Registration API you should consider registering a separate Merchant ID per sub-merchant under your PSP's developer account.

Then, at runtime, your hosted checkout selects the correct merchantIdentifier for the active merchant. You manage payment processing certificates centrally, but each merchant has their own display name registered.

Cheers,

Paris X Pinkney |  WWDR | DTS Engineer

Hi @ow-f,

You wrote:

[...] Is there any parameter or configuration that controls what Wallet shows as the payee? For example, can this be set via a specific field/parameter, or is it strictly derived from the Merchant ID’s display name (or other Apple Pay configuration)? What is the correct approach for a PSP/acquirer to have the merchant’s brand shown in Wallet transaction record? [...]

There are two completely independent UI surfaces that are frequently conflated:

  • Apple Pay payment sheet: Displays total.label from your payment request at runtime
  • Wallet transaction receipt: Displays merchant display name from the Apple Developer portal and card network clearing data.

Setting values in your ApplePayPaymentRequest at runtime doesn't affect the Wallet receipt. These are entirely separate mechanisms.

When you use a single shared Merchant ID for all your merchants, the display name registered against that Merchant ID in the Apple Developer portal is what Apple Pay and Wallet resolves at the moment of transaction. Since your Merchant ID is registered under your PSP's identity, your domain/brand appears for every transaction across all your merchants.

There is no API field to override the merchant display name or payee name in Wallet at runtime. However, there are two mechanisms to consider:

  • Developer portal display name. Resolved at the time of the merchant session validation (validateMerchant handshake). Immutable at runtime. Whatever display name is registered against the merchantIdentifier used in the request is what Apple records.
  • Card network clearing data (post-settlement enrichment). After settlement, issuing banks can retroactively update Wallet records based on enriched merchant data received through card network clearing messages. This is where a sub-merchant name can surface — but it is entirely outside of the Apple Pay API layer.

Important: This enrichment is highly issuer-dependent, not guaranteed, and not something you control through Apple's APIs. It depends on whether your acquiring bank populates the sub-merchant name correctly in clearing data, and whether the specific issuing bank has implemented Wallet record enrichment.

If you request and are granted approval for the Apple Pay Web Merchant Registration API you should consider registering a separate Merchant ID per sub-merchant under your PSP's developer account.

Then, at runtime, your hosted checkout selects the correct merchantIdentifier for the active merchant. You manage payment processing certificates centrally, but each merchant has their own display name registered.

Cheers,

Paris X Pinkney |  WWDR | DTS Engineer

Apple Pay
 
 
Q