Use case for each PKMerchantCapability

App & System Services Apple Pay
mmm OP
Created Jun ’15
Replies 2
Boosts 0
Views 788
Participants 2

I'm curious about the exact use case for each of the values for PKMerchantCapability.

I'm especially confused with the introduction of the new .CapabilityCredit and .CapabilityDebit values.


Here's what I've got so far:


.Capability3DS => Apple Pay for credit or debit cards where the issuer has collaborated with Apple and a 3D Secure cryptogram is passed to the processor

.CapabilityEMV => Apple Pay for in store purchases (I'm not sure how this is used in a PKPaymentRequest)

.CapabilityCredit => Apple Pay with credit cards, sans 3D Secure verification

.CapabilityDebit => Apple Pay with debit cards, sans 3D Secure verification


Thanks!

Replies  2
Boosts  0
Views  788
Participants  2
OP
Apple
Jun ’15

There are certain use cases where a merchant may only want to accept credit or debit cards. Capabilities are a bit field and credit/debit are independant of EMV/3DS.

1
mmm OP
Jun ’15

Thanks for the clearification.


If credit or debit cards is specified, will that filter the list of cards that is presented to the user accordingly?

0
Use case for each PKMerchantCapability
First post date Last post date
 
 
Q