Overview
When you send an activate, suspend, or terminate request for a digital wallet token (DWT), Marqeta forwards the request to the token service provider (TSP). If the TSP’s response is ambiguous — for example, it reports the token as not found or the request data as invalid — Marqeta checks with the TSP directly for the token’s actual state before responding to you. This check can surface a mismatch between the token’s state on record with Marqeta and its actual state with the TSP, which Marqeta reports using the422003 and 422004 error codes on POST /digitalwallettokentransitions.
This article explains why that mismatch can occur and what to do about it.
For the field-level error reference and sample response bodies, see Digital Wallets Management.
Why the Marqeta and TSP states can differ
A token’s state on record with Marqeta can fall out of sync with its actual state on the TSP. This can happen if a TSP notification confirming a change is delayed or never reaches Marqeta, if a request to the TSP times out and Marqeta can’t confirm whether it was processed, or if the token’s state changes directly on the TSP outside of a Marqeta-initiated call.Resolution by scenario
The following tables summarize each scenario, the response you receive, and what you need to do.Terminate
Activate
Suspend
- For any other
422003error not covered by the scenarios above, the failure is a generic TSP error. Retry the request later; if the error persists, contact Marqeta support. - Marqeta blocks any state transition request (activate, suspend, or terminate) against a token that’s already
TERMINATED. This guidance covers TSP-related errors (422003/422004) only — a request against an already-terminated token returns a separate validation error.