Adyen 14_005 - Invalid payment method details

TL;DR: The recurring contract on the stored token does not match the contract in your request. Check the token's contract in the Customer Area, request the matching contract, or re-tokenize the card with the contract you need.

The exact error:

14_005 - Invalid payment method details

The fix

1. Look up the stored payment method in the Adyen Customer Area and note its recurring contract. Expected: You see whether the token is RECURRING, ONECLICK, or both.

2. Set recurringProcessingModel and shopperInteraction in /payments to match the token's contract. Expected: The requested contract matches what the token supports.

3. If the contracts cannot be reconciled, re-tokenize the card with the contract you need and retry. Expected: The payment proceeds past validation to authorization.

When this applies

• /payments with a stored card returns 14_005
• You recently changed between one-click and subscription flows
• Tokens came from a migration and now fail validation

When it does NOT apply

• A first-time card payment with fresh details (look at 14004 or 14007 instead)
• The token itself is missing or expired
• A 3D Secure failure after the payment was accepted for processing

Versions

Adyen Checkout API v68 through v71. Applies to stored payment methods and tokens.

Why it happens

The stored payment method carries a fixed recurring contract. Adyen compares the contract in your request against the token's contract during validation, and a mismatch is rejected as invalid payment method details.

Edge cases and pitfalls

• A token created with a RECURRING contract cannot be used for a ONECLICK payment and vice versa
• Migrated tokens from another processor may carry a contract type your Adyen config does not allow
• The shopperReference must match the one the token was stored under

Adyen documents 14005 with one concrete cause: the recurring contract on the token does not match the contract you are asking for. A stored payment method remembers whether it was created for RECURRING, ONECLICK, or both. If your /payments request asks for a contract the token does not support, validation fails with 14005. This shows up when you change your tokenization flow (for example moving from one-click to subscriptions) without re-tokenizing, or when the stored details came from a migration. The fix is to check the contract on the stored payment method in the Customer Area, then either request the matching contract or store the card again with the contract you need. Also confirm shopperReference and shopperInteraction line up with how the token was created.