We launched an iOS app today using the In-App Payments SDK (production). Every Apple Pay payment fails with GENERIC_DECLINE / PAYMENT_METHOD_ERROR at authorization, while keyed card entry through the same app, seller, and application works.
Evidence gathered so far:
- The wallet tokens decrypt correctly — failed payments show full card details and
payment_account_reference, andrisk_evaluationis NORMAL. - Same-day control: the same physical card (matching PAR) succeeded keyed and declined via Apple Pay 30 minutes apart. A second card from a different issuer declines identically, so it isn’t one bank.
- PKPaymentRequest uses countryCode US / currencyCode USD, matching the seller’s US/USD account. The identical flow works in sandbox.
- The seller already takes card-not-present payments daily via Square Online, but we found no wallet CNP payment has ever succeeded on this seller — these may be its first.
- The Apple Pay payment processing certificate (production,
merchant.ai.cratehq.corridorflow) was created 2026-07-08T04:37Z, a few hours before the first attempt.
Seller 7ADYFN4XM0MPG, location MBHQ85NZJT2RP, application sq0idp-W_--… (full ID on request). Failed payment IDs start 1wlBY1, n9Nsuj, ZWDjW6; successful keyed control starts d8fyH0 (full IDs on request).
Questions: (1) Can someone share the raw processor/issuer response behind these GENERIC_DECLINEs? (2) Is there a seller- or application-level flag that blocks digital-wallet CNP until enabled? (3) Does a newly-created Apple Pay certificate need propagation time before production authorizations succeed?