Diagnose Tap to Pay setup failures
Check enablement, environment and signing before treating a phone configuration failure as a payment decline.
Check enablement first
The service must be Active, not merely Offered. Check processor and merchant-country support. If a reseller bills the account, request activation through that provider. Match the installed SDK environment, merchant Test Mode and selected platform package.
Diagnose Android attestation
Reported issue First checks ATT006 / request not genuine Installed signing certificate matches onboarding; account for Play key upgrades. Other DeviceAttestationFailed Onboarding for this environment, signing identity and retail-device integrity. RegistrationRequired Environment provisioning and signing-certificate match. App Tampered / General Error Play-installed versus sideloaded signing identity. ServerCommunicationError Check accompanying registration error, then network/firewall.
Diagnose iPhone configuration
Reported issue First checks AccessDenied SDK environment and gateway mode agree. AttestationFailed Publishing entitlement for the live flow. InvalidAppleAccount / invalidReaderToken Correct Apple account type and distinct sandbox identity. IncorrectPassword Non-empty SDK database password and required build settings. TapToMobileAccountNotLinked (4.1.2) Apple Tap to Pay terms have not been accepted or were declined. Call connectAndConfigure to present them; acceptance still belongs to the merchant. Release 4.1.2 fixes a prior terms-presentation issue that could cause General errors.
Provide actionable diagnostics
Record gateway ID, application/package or bundle ID, SDK version, environment, device/OS and UTC failure time. On Android also record AAR version, installation route and registered certificate fingerprint; on iPhone record entitlement type. Use the support channel for diagnostic logs. Do not reset a production device or start another charge simply because an error resembles a source FAQ example.