- Overview
- Countries & currencies
- Integration
- Process flows
- Testing
- Additional information
- Consumer experience
- Reporting
- FAQ
FAQ
-
Show Hide
Does the MyCheckout hosted payment pages validate whether a consumer has added a card to the Apple Wallet?
On the payment product selection page of the MyCheckout hosted payment pages, we validate whether the consumer is using a device that supports Apple Pay, for which we use Apple's canMakePayments call.
As per the Apple Pay on the Web Acceptable Use Guidelines, we should use the aforementioned option to detect whether a consumer can pay with Apple Pay, as the alternative canMakePaymentsWithACtiveCard would requires us to set Apple Pay as the default or sole payment option.
-
Show Hide
How is our domain verified for Apple Pay in our test environment, which is not accessible from outside our network?
Depending on your integration type of Apple Pay, you will get a domain verification file, which you need to host at a specified location.
Testing of Apple Pay can be done in our staging/pre-production environment. The domain-verification file you obtain in the staging environment, can be used in your test environment.
Our staging/pre-production environment is pointing to the test/sandbox environment of Apple and in that environment Apple is not validating the domain verification file.
In production you will need to follow the same steps in the configuration center as you followed in staging and the domain verification file must be place in the right location for production use, as in production your domain will be verified by Apple.
-
Show Hide
Why does Apple Pay appear a split second later on the payment product selection page of the MyCheckout hosted payment pages?
Prior to showing the Apple Pay button on the payment product selection page of the MyCheckout hosted payment pages, we validate whether the consumer can make a payment with Apple Pay. Due to this validation, it takes a split second before your consumers can see Apple Pay as an option to pay with.
-
Show Hide
How does fraud checking work with Apple Pay?
AVS, 3D Secure and CVV are not used in the case of Apple Pay, as the risk is reduced due to the fact that the card data is tokenized. Normal fraud checking can be done with Apple Pay.
-
Show Hide
How can I see Apple Pay transactions in Insights or in the WebCollect Payment Console (WPC)?
You will see Apple Pay transactions under the payment product Apple Pay. Please note that for further processing you will be able to see the card scheme associated to the Apple Pay transaction and its associated payment product ID as well, which can be a different one than the payment product ID 302 which is used as the generic one.
The following payment products are used for further processing:
- Apple Pay Visa: payment product ID 302
- Apple Pay MasterCard: payment product ID 303
- Apple Pay American Express: payment product ID 304
- Apple Pay Discover: payment product ID 305
-
Show Hide
What is a DPAN?
A DPAN is a Device Primary Account Number, which is a device-specific tokenized card number. The DPAN is generated after a consumer added a debit or credit card to the Apple Pay app.
-
Show Hide
Why do I not see Apple Pay separately on my invoice?
Since Apple Pay transactions are processed in a similar way as credit and debit cards, with the same fees as credit and debit cards, they are accumulated under the Visa, MasterCard, American Express and/or Discover line (s) on your invoice.
-
Show Hide
Who is the merchant of record?
The merchant is the seller of record.
-
Show Hide
How are disputes handled?
Disputes are handled in the same way as disputes are handled for credit and debit cards.