iPhone Apple Wallet fails to add payment cards after backup restore

Question

Level 1

8 points

iPhone Apple Wallet fails to add payment cards after backup restore

Hi all,

I’ve spent days on this. Apple Support says it’s the bank’s problem. The logs say otherwise, so I’m hoping someone here (or someone from Apple) can help.

Setup

iOS 27.2
Happens on both my iPhone 18 Pro Max and iPhone Duo
Region: Saudi Arabia (Apple ID is United States).
This isn’t a one-off. It happens every time I move from one iPhone to another using a backup. After each restore, I can’t add any payment card to Apple Wallet. Same failure, every time.

What happens

Adding a card from the bank’s app (or from Wallet) goes normally at first. The card is checked, it’s marked eligible, I accept the terms, and then it fails at the very last step.

What I’ve tested

Two different banks: D360 and SAB. Same failure at the same step with the same error.
Restarted the phone, tried adding from the bank app and from Wallet, and tried different networks. DNS and connectivity are fine; the logs show successful requests right up to the failure.
The same cards add to my wife’s iPhone with no problem. She uses a different Apple Account. So the cards, the banks and the network are all fine. The problem is tied to my iPhone or my Apple Account.

What the logs show

I captured live logs from Console on a Mac (filtered on passd and PassbookUIService) during each attempt. Both banks fail identically.

SAB attempt, 5 Nov 2026:

18:38:39 ProvisioningOperationComposer: starting step 'assessDevice()'
18:38:39 passd canAddPass: YES with maxCards: -1, passCount: 3 - seAvailable: YES
18:38:40 starting step 'eligibility(generateCryptographicMaterial)'
18:38:46 Received Status Code 412.
18:39:05 response_status=200
18:39:05 ProvisioningStepEligibility: received eligibility status: 1
18:39:06 ProvisioningStepTerms: terms required
18:39:10 Note Provisioning Did Begin.
18:39:10 starting step 'provision(generateCryptographicMaterial, eligibility, resolveEnableRequirements, assessDevice)'
18:39:13 response_status=403
18:39:13 Received Status Code 403.
18:39:13 error: Step failed with error Error Domain=PKProvisioningErrorDomain Code=5
18:39:13 Note Provisioning Did End.

D360 attempt, 5 Nov 2026:

18:31:22 canAddSecureElementPassWithConfiguration: returning result: YES
18:31:22 Notice: Can provision payment pass with primary account identifier <private>
18:31:31 Received Status Code 412.
18:31:49 ProvisioningStepEligibility: received eligibility status: 1
18:31:50 ProvisioningStepTerms: terms required
18:32:00 Note Provisioning Did Begin.
18:32:00 starting step 'provision(...)'
18:32:03 Received Status Code 403.
18:32:03 error: Step failed with error Error Domain=PKProvisioningErrorDomain Code=5
18:32:03 Note Provisioning Did End.

Other things in the logs that may be relevant:

passd  Needs Registration: NO (Has Previously Registered: YES, Has Certificates: YES, User Owns Secure Element: YES)
securityd  CKKS didn't find a current item for (com.apple.ProtectedCloudStorage, com.apple.wallet.paymentservices): Error Domain=securityd Code=-25300 "No current item pointer found"

To sum up: both banks approve the card as eligible. The final enable request gets 403 Forbidden from the server, and Wallet reports PKProvisioningErrorDomain Code 5. Two different issuers failing at the same point, while the same cards work on another Apple Account, points at my device or account, not the banks.

And because this happens after every device move, not just once, it looks like something tied to my Apple Account or how my Apple Pay registration carries over through backups. It doesn’t look like a fault in one phone.

My experience with Apple Support

I called Apple Support (case 30000006103008 and gave them all of the above, including the error codes, timestamps and the two-bank test. They checked my account, said it isn’t flagged or blocked, and told me to contact the bank.

Honestly, that’s frustrating. The banks aren’t the problem; two of them fail the same way, and the same cards work on my wife’s phone. Sending me to the bank just means I’ll get bounced back to Apple. I need someone who can look at why Apple’s provisioning server returns 403 for my device or account.

My questions

Has anyone seen a 403 / PKProvisioningErrorDomain Code 5 at the final provisioning step after a restore? What fixed it?
Is there a device-level hold (separate from the account) that Support can’t see from a normal account check?
Would signing out of my Apple Account and back in, or removing my old devices from the account, reset this?
Is there a way to get this escalated to Apple Pay engineering instead of going back to the bank?
Since this repeats with every restore, is something in my backup or account carrying over a bad Apple Pay state? Would setting up the phone as new (not from backup) avoid it?

iPhone Duo

Posted on Nov 9, 2026 12:42 AM

Reply

Answer 1

Nov 9, 2026 2:30 AM in response to kabuataya2

The bank’s or the entity the bank uses to provision payment methods both returned a 403 error and provisioning stopped. Ask the banks why their servers stopped provisioning their respective cards with a 403 error.

Ask the banks what the 403 error means.
‘Apple is not a bank and does not approve or decline cards for Apple Pay provisioning. The authority to block cards rests entirely with the bank or their designated provider.
Signing in an out won’t reset anything.
No, the above segment does not contain enough information for Apple engineering. The bank’s Apple Pay team would need to contact Apple. Apple engineering would need the logs from the bank’s servers and that’s never going to happen. The bank will never give you their logs.
It’s possible in the backup, but unlikely.

You’ve made some false assumptions. Neither bank approved the eligibility. What happens is you enter your card details, the Payment Network Operator ( Visa, MasterCard, American Express etc.) receives just the account number and expiration date, not the 3 or 4 digit security code. The PNO checks that the account is a valid account and returned your account is eligible. That allows Apple to download and send to your device the bank’s terms and conditions. You agree and your device sends the security code and the bank starts their fraud detection etc. and returned a 403 and declined provisioning. Your conclusion the banks sent eligible is false. The banks both stop provisioning and generate the same error code, 403.

Do you use a VPN? You say this happens every time. How have you resolved this in the past?

Reply

Answer 2

Nov 9, 2026 3:54 AM in response to kabuataya2

Apple documents that information contained on the device is sent to the banks for use in provisioning the card. The information is anonymous to Apple, so they don’t know any personal information. The information includes location of device, information about iPhone usage such as if texts are sent and received, are phone calls made and received and does the iPhone change locations. Apple doesn’t detail the exact information, but Apple Account information is also sent. For example information about App Store usage, iTunes Store usage etc. is sent to the banks. Banks use fraud detection algorithms (AI) to help determine if the device and account represent a risk and if so, is the risk acceptable. Apple doesn’t participate in decision making, but the data in encrypted format does pass through Apple servers.

Apple engineers would need the bank’s server logs to determine way the decline, but Apple is never informed as to the why or how to fix the issue. Banks don’t share customer information, server logs, fraud risk algorithms etc. This literally prevents Apple from knowing anything about why it’s being declined. But some associated with your Apple Account or device usage patterns etc. is an indicator for the banks involved.

Why won’t the banks tell you the real reasons. Banks see this as friction. They want to avoid this at all costs. They don’t want you using their products and services less. They especially don’t want to lose you as a customer. But they aren’t going to tell you that their algorithm determined you and your device are a fraud risk. So, blame Apple.

It’s not the first tier support people or their supervisors. They typically have no clue how Apple Pay works and have no access to any information that might be helpful to you.

That’s a lot to think over. So, please let me know what your thinking and together we can workout a plan to help you move forward.

Reply

Answer 3

kabuataya2 Author

Level 1

8 points

Nov 9, 2026 3:28 AM in response to Jeff Donald

Thanks, that’s a fair correction on how eligibility works. You’re right that the 403 is likely the bank’s decision at the final step.

One thing doesn’t fit, though: the same cards add without any issue to my wife’s iPhone (different Apple Account). If the banks were blocking the cards themselves, that wouldn’t work. As I understand it, Apple sends the issuer a device/account risk assessment with each provisioning request, so two unrelated banks declining my phone the same way suggests something in that assessment for my account or device.

To answer your questions: I dont use VPN.

in the past. how did I get it resolved is by trying over and over and over until it does, until then I get stuck not able to use apple Pay and have to rely on physical cards if I have them and banks provide them.

Reply