Post

Replies

Boosts

Views

Activity

ProximityReader framework — "Unexpected reader error (2016)" causing Tap to Pay session failures on iOS 26.x
Hi everyone! Our Tap to Pay on iPhone integration using the ProximityReader framework is experiencing widespread failures with error code 2016 ("Unexpected reader error") when attempting to prepare the reader for contactless payment sessions. The issue started on August 9, 2026 and is affecting multiple device models across iOS 26.x versions. Error Details: Framework: ProximityReader Error: "Unexpected reader error (2016)" Operation: Session activation during payment flow (ProximityReader.prepare()) Result: Reader cannot be prepared; payment sessions fail immediately Questions: What does ProximityReader error code 2016 specifically indicate? Is there a known issue with the ProximityReader framework on iOS 26.5.2 / 26.6 / 27.0? Many thanks Icaro.
0
0
25
9h
ProximityReader framework — "Unexpected reader error (2016)" causing Tap to Pay session failures on iOS 26.x
Hi everyone! Our Tap to Pay on iPhone integration using the ProximityReader framework is experiencing widespread failures with error code 2016 ("Unexpected reader error") when attempting to prepare the reader for contactless payment sessions. The issue started on August 9, 2026 and is affecting multiple device models across iOS 26.x versions. Error Details: Framework: ProximityReader Error: "Unexpected reader error (2016)" Operation: Session activation during payment flow (ProximityReader.prepare()) Result: Reader cannot be prepared; payment sessions fail immediately Questions: What does ProximityReader error code 2016 specifically indicate? Is there a known issue with the ProximityReader framework on iOS 26.5.2 / 26.6 / 27.0? Many thanks Icaro.
Replies
0
Boosts
0
Views
25
Activity
9h