Solution skill
Adyen 14_007 - Invalid payment method data
Complete solution
Resolves Adyen checkout error 14_007 when the paymentMethod object contains bad data, such as a missing type. Use when paymentMethod exists but Adyen rejects its contents. Not for a wholly absent paymentMethod (14_006) or missing detail fields (14_004).
TL;DR: The paymentMethod object is present but its contents are invalid, usually a missing or misspelled type. Log the block, set type to an exact API reference value that your account has enabled, and whitelist it server-side.
The exact error:
14_007 - Invalid payment method dataThe fix
Log the paymentMethod block of the failing request. Expected: You see exactly what your server sent inside paymentMethod.
Set paymentMethod.type to a valid, enabled value such as scheme or ideal. Expected: The type matches the API reference spelling and is enabled for your account.
Add a server-side whitelist for the type field so bad values are caught before the API call. Expected: Validation passes and the payment proceeds.
When this applies
- /payments returns 14_007
- You map shopper input to the type field by hand
- A new payment method was just enabled in the dashboard
When it does NOT apply
- paymentMethod is missing entirely (that is 14_006)
- Required encrypted fields are absent (that is 14_004)
- The shopper's bank refused the payment after validation passed
Versions
Adyen Checkout API v68 through v71.
Why it happens
Adyen validates the paymentMethod object field by field. A missing or unrecognized type means the payment cannot be routed, so the request fails validation with 14_007.
Edge cases and pitfalls
- paymentMethod.type is case-sensitive; Scheme with a capital S is rejected
- Extra unknown fields inside paymentMethod can also trigger this, not just missing ones
- Copy-pasted examples sometimes use a type your merchant account has disabled
Evidence
Adyen's own example for 14_007 is a paymentMethod object whose type is missing. The object is there, but its contents do not describe a usable payment method. Common variants are a null or empty type, a type string with wrong casing, or a type your merchant account does not have enabled. The fix is to validate the object before sending: type must be present, spelled exactly as the API reference lists it (scheme, ideal, paypal, and so on), and enabled for your merchant account. If you build the object from shopper input, add a whitelist check on your server so a bad value never reaches Adyen.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_TSZRb8v0GIBNwteAT4YCrg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Adyen 14_007 - Invalid payment method data <span>— Vectle</span></a>