cancel
Showing results for 
Search instead for 
Did you mean: 

How to setup Apple Pay and the options provided by A.Net for setting up Apple Pay

Support,

I'm trying to verify that I have completed the initial setup.
Enabled Apple Pay by providing Merchant Id in A.Net and downloading the CertificateRequest.csr file from A.Net. Then I uploaded this file in the apple developer account to create Certificate Type: Apple Pay Payment Processing.
With this I believe initial setup is complete. 
Is this correct?

Also, based on what I can see on A.Net site. A.Net does not provide any frontend apple pay support.

I see stuff for mobile SDK but that is not clear. I think it is meant for native moblie apps

The use case:
currently, we have a custom payment form for credit card processing on our website. So we are looking to adding apple pay as another payment option on our web app.
What are my options for adding apple pay with A.Net? My understanding is that there is nothing and I that have build the functionality myself. Is this correct?

astroubey
Member
1 REPLY 1

You're right to be cautious here — for COF (Card-on-File) compliance, it's strongly recommended to move away from the old 2013 PHP SDK. The createCustomerProfileTransaction method itself doesn't natively support the required COF indicators in those legacy libraries.

The current Authorize.Net SDKs (like the official PHP SDK on GitHub) support COF fields such as processingOptions, subsequentAuthInformation, and transaction type indicators, which are essential for compliance.

So yes, updating to the latest SDK is the best move — not just for COF, but also for ongoing security and API support. Make sure to handle initial vs. subsequent transactions properly to align with the COF framework. Let me know if you need help mapping the old CIM calls to the new structure!

johanmark1122
Member