LINK_TOKEN_WRONG_IDENTIFIER

Cause

POST /v1/link-tokens returns two identifiers. The flow routes (submit-credentials, select-biller, submit-mfa, …) take the link_token VALUE — the capability Connect holds — but the request carried the link_token_id.

How to fix it

Pass the link_token value from the create response on flow routes. Keep link_token_id on your server for GET /v1/link-tokens/{link_token_id}/status.

Example response

{
  "error_code": "LINK_TOKEN_WRONG_IDENTIFIER",
  "error_type": "invalid_request",
  "error_message": "The path carries a link_token_id where the link_token value belongs.",
  "hint": "Pass the link_token value from the create response on flow routes. Keep link_token_id on your server for GET /v1/link-tokens/{link_token_id}/status.",
  "docs_url": "https://docs.billerapi.com/errors/LINK_TOKEN_WRONG_IDENTIFIER",
  "request_id": "d94f5e2a-8c3b-4f1e-9a7d-6b2c1e0f8a34"
}

Related

• Error handling — the error envelope shape and how to parse it
• Error code reference — every stable error code