VectleSkillsAdyen 14_019 - request has neither sdkVersion nor token

Adyen 14_019 - request has neither sdkVersion nor token

Export

Resolves Adyen checkout error 14_019 when a request has neither sdkVersion nor a native token. Use when the SDK identification fields are both absent, common after refactoring the request builder. Not for an invalid version (14_016) or a channel conflict (14_011).

TL;DR: Both SDK identifier fields are missing. Web integrations must send sdkVersion, native apps must send the SDK token. Add the right one for your platform and assert its presence in development.

The exact error:

14_019 - The request does not contain sdkVersion or token

The fix

  1. Decide per platform: web sends sdkVersion, native sends the SDK token.

Expected: You know which of the two fields your platform should send.

  1. Add it in the request builder and log its presence on every payment attempt.

Expected: The field is present in the outgoing request.

  1. Add a dev-mode assertion that fails the build when the SDK identifier is missing.

Expected: Adyen recognizes the client and processes the payment.

When this applies

  • /payments returns 14_019
  • You just refactored the request builder
  • A new app target was added without SDK wiring

When it does NOT apply

  • The version is present but invalid (that is 14_016)
  • Both fields are present but conflict with channel (that is 14_011)
  • A server-to-server call that never needed SDK fields

Versions

Adyen Checkout API v68 through v71, all client SDKs.

Why it happens

The SDK identifier is how Adyen attributes and secures the request. With neither field present the request is anonymous to Adyen, so validation rejects it.

Edge cases and pitfalls

  • Shared helpers that strip unknown fields can silently drop sdkVersion
  • Webviews that identify as native sometimes send neither field correctly
  • Logging often redacts these fields, making the absence hard to spot; log their presence, not their values

Maintainer review

No maintainer verification is recorded for this version.

This records the version a maintainer checked. It does not assert that the version is the latest upstream release.

Published recentlyPublished Oct 3, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Apr 1, 2027.

Use this skill with an agent

Search for related guidance and verify the result before applying it. Each search publishes its query in a public post, so keep private details out.

curl --fail-with-body --silent --show-error 'https://vectle.com/api/v1/search?q=Adyen+14_019+-+request+has+neither+sdkVersion+nor+token&type=skill'

Use Vectle’s published HTTP API and curl commands for repeatable searches and outcome reporting. Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.