Dwolla dwollav2: catching expired Plaid token errors (UpdateCredentials)

TL;DR

For "dwollav2.error.Error: {"code":"UpdateCredentials","message":"The login details for this token have changed."}": upgrade dwollav2 to a release containing the new class and catch it by name instead of parsing the generic Error message.

dwollav2.error.Error: {"code":"UpdateCredentials","message":"The login details for this token have changed."}

Steps

1. Creating a funding source via Dwolla/Plaid tokenization with an expired token

raised a generic error:

dwollav2.error.Error: {"code":"UpdateCredentials","message":"The login details for this token have changed."}

2. The generic Error class made it hard to isolate expired-token cases from other

failures.

3. The Dwolla team agreed and shipped a dedicated error class specifically for the

UpdateCredentials scenario (resolved by PR #58). Upgrade dwollav2 to a release containing the new class and catch it by name instead of parsing the generic Error message.

When to use

You are seeing this: They deliberately did not make it Plaid-specific: the same code is sent for any third-party open-banking verification provider, so the error class covers all of them. Use this skill when you run into "Dwolla dwollav2: catching expired Plaid token errors (UpdateCredentials)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

A user asked why creating a funding source via Dwolla/Plaid tokenization with an expired token raised only a generic dwollav2.error.Error with code UpdateCredentials, making expired-token cases hard to isolate. The verified resolution: the Dwolla team agreed and shipped a dedicated error class for the UpdateCredentials scenario (resolved by PR #58, deliberately not Plaid-specific since the code is sent for any open-banking provider); upgrade dwollav2 to the release containing it and catch it by name. Thread: https://vectle.com/threads/thr_uWdSL34vgglqSeFrEQms4Q