Can I create a recurring subscription from Apple Pay?

[ryanpsloan]

Can I create a recurring subscription from Apple Pay? The API docs say the dataDescriptor value must be COMMON.ACCEPT.INAPP.PAYMENT. But Apple Pay uses a different dataDescriptor value. Does that mean that I can't create a subscription from Apple Pay? If not, how can I do it? Please show code examples in php.

Thanks,

[George911]

---

@myfedloan wrote:

"We have released this feature to support adding customer profiles with Apple Pay in prod ."

Does that mean that this feature is not available in the Sandbox?  When I try to create a customer profile in the Sandbox with an Apple Pay token I get this error:

"E00141 - Payment Profile creation with this opaqueData descriptor requires transactionmode to be set to liveMode".

---

I have hit an impasse on a project I'm currently working on for a client.  If we can't use Apple Pay for recurring payments, I fear they may have to abandon Authorize.NET entirely.

[ij_webhosting]

This doesn't work currently, I implemented this. I store the opaqueData with the corresponding COMMON.APPLE.INAPP.PAYMENT dataDescriptor in the CIM. We create an ARB for the customer. Howeber, the transaction made for the recurring payments decline each time. "Declined  (Card declined by issuer - Contact card issuer to determine reason.)". That is even though we did get the correct  recurring token from Apple (via preauthorized payments)/recurringPaymentRequest.

[ij_webhosting]

This does not appear to work. I created a CIM with the opaqueData, and a corresponding ARB. All recurring transactions decline, a one-time transaction for the token does go thru. So it doesn't seem that Authorize.net supports this, after all, in 2025. And we are getting a recurring transaction token from Apple (via preauthorized payments)/recurringPaymentRequest.

[zeyarpaing]

This is not working.

Created payment profile with opaqueData and liveMove validation -> charging it using the profile - Failed (Saying "declined")

Created customer profile -> create a transaction with opaqueData - success authorize -> create payment profile using transaction_id -> changing using payment profile - Failed same as above

Created customer profile -> create a transaction with opaqueData - success authorize -> creating the same transaction again with same opaqueData - Failed same as above

Is there anything we're missing? It's clear that the issuer does not decline since the first transaction always go through.