[BUG] [P1] STPPaymentCardTextField zip code field registers wrong key input on iOS 26 (iPad)

[marcin-mucha]

Summary

On iPads running iOS 26, the postal/ZIP code field inside STPPaymentCardTextField registers incorrect characters. For example, pressing the delete key appends "2" instead of deleting. The card number, expiry, and CVC fields are not affected — only the postal code field.
See the attached video.

The postal code field is the only sub-field using .numbersAndPunctuation keyboard type (line 860 in STPPaymentCardTextField.swift). All other fields use .asciiCapableNumberPad (line 1580 in STPPaymentCardTextField.swift). We suspect this is related to an iOS 26 keyboard regression affecting full keyboard layouts, but we're looking for a workaround on the Stripe SDK side.

What is blocked by this issue?

Users are unable to enter credit card details.

Code to reproduce

STPPaymentCardTextField wrapped in UIViewRepresentable for SwiftUI

1. Open a payment flow using STPPaymentCardTextField on an iPad running iOS 26
2. Enter a valid card number, expiry, and CVC
3. Tap the ZIP code field
4. Type digits or press delete on the keyboard
5. Observe that wrong characters appear (e.g., delete key inputs "2")

iOS version

26.2.1

Installation method

SPM via stripe-ios-spm

SDK version

Stripe iOS SDK: 25.3.1

Other information

IMG_5545.mov

[ilanahaddad]

Hello, we're experiencing the same issue.

Adding additional context from our investigation:
Environment: Physical iPad, iOS 26.3, SDK versions 25.5.0 and 25.6.3, presented in a .formSheet via UIHostingController.

Additional observations:

• The bug also affects STPCardFormView, not just STPPaymentCardTextField
• The issue only occurs when transitioning from another field (card number/expiry/CVC) to the postal code field. If you dismiss the keyboard and tap directly into the postal code field first, touches register correctly.

Two manual workarounds that fix it at runtime:

1. On the numbersAndPunctuation keyboard, tap "ABC" to switch to alphabetic, then tap ".?123" to switch back. Touches register correctly after this.
2. Dismiss the keyboard, then tap directly into the postal code field so numbersAndPunctuation is the first keyboard shown (no transition from numberPad)

Both workarounds force the keyboard to rebuild its internal key layout, confirming the root cause is the keyboard type transition from asciiCapableNumberPad → numbersAndPunctuation.

Recording

stripe-bug-STPCardFormView-short.mov

[yuki-stripe]

Thanks for the report. A quick test on an iOS 26 iPad simulator didn't repro for me, is this device-only or can you repro on simulator too?

It looks like we can make a tweak to STPPaymentCardTextField to use the same asciiCapableNumberPad for zip code, when country is US, which at least makes the problem go away for that particular scenario @marcin-mucha. But I'm not sure what we can do besides that if this is indeed an iOS bug, definitely open to ideas here!

[marcin-mucha]

@yuki-stripe I wasn't able to reproduce on simulator either, only on the real device.

Fixing the case for US is definitely a good idea. Alternatively, perhaps, some forced re-layout of the keyboard as per @ilanahaddad's findings?

[yuki-stripe]

@marcin-mucha @ilanahaddad I've tried reproducing on an iPad (A16) on 26.3.1, for both STPPaymentCardTextField and STPCardFormView + Canada country code without success. I see the same keyboard type switch in the videos but don't experience an issue.

Maybe 26.3.1 (released yesterday) fixed the issue - could you try updating and see?

[lisional]

Hey, I'm working with @ilanahaddad 👋
I upgraded to 26.3.1 on my physical iPad (10th gen, 10.9) and I'm still reproducing the issue there unfortunately

[ilanahaddad]

Hi team, it seems like the iPadOS 26.4 upgrade seems to have resolved this issue. I believe this is what is mentioned here in the release notes. For this Stripe component specifically, we no longer see the new number keypad so there is no issue when switching from the numeral keypad to regular keyboard for the zip code/ postal code field.

Fixed: KeyboardNotification might not send. (165479264)