Consolidating what I've been able to establish on this, since I
think a few pieces here narrow the problem down beyond what's been
covered so far in this thread.
Setup: organization enrollment, D-U-N-S verified, checkout returns
"Your payment authorisation failed on card ••••XXXX."
FINDING 1 — the decline is upstream of the card network
I asked my bank to check their authorization logs for every attempt
across every card. There is no record of any authorization request
from Apple ever arriving. Not a decline — no request at all.
This matters because most troubleshooting in this thread assumes an
issuer-side decline, which leads people to keep trying new cards,
calling their bank, or checking billing addresses. If Apple's system
is failing before it submits the authorization, none of that can
work. If others here can confirm the same with their own banks, that
would establish the pattern properly.
FINDING 2 — Apple Pay is blocked on this specific order
The checkout shows Apple Pay greyed out with "Items in your order
are not eligible for this payment method." So the one path that
would bypass manual card entry is closed by an Apple-side eligibility
rule, not a card issue.
FINDING 3 — there is an open Apple engineering ticket
After escalation through four Developer Support advisors, this was
raised to Apple's engineering team under internal ticket
INC102862067. It has been open three weeks.
I'm posting the number because it may be useful to others here:
if you're hitting this same failure, referencing INC102862067 in
your own support case may help link your report to the existing
investigation rather than starting a fresh one.
CONTEXT
The same company is verified and currently publishing on Google
Play, including D-U-N-S verification and a successful developer
payment there. So entity legitimacy, D-U-N-S validity, and card
payment capability are all externally verified. The failure appears
specific to Apple's enrollment payment path.
Total elapsed: seven weeks.
If anyone here does get resolved, it would be worth posting what
specifically changed — as far as I can tell from reading back
through this thread and the related ones (818048, 819149, 767661,
821654), nobody has documented a confirmed fix.