Get the attachment status
The connected user’s latest attachment: pending while the user hasn’t finished the link, active with card details once attached, or ineligible with a reason when the card cannot be attached (fall back to wallet funding + create_card).
Statuses
pending— the user hasn’t finished the attach link. Nudge them to complete it; poll again after.active— attached.cardcarries the display details (brand, last4 — never the full number). Cards created over MCP now charge this card directly.ineligible— this card can’t be attached;reasonsays why (for exampleissuer_excluded,commercial_card). Fall back to wallet funding andcreate_card.
404 no_attachment means nothing was ever started for that user — begin
with Start a card attachment.Authorizations
A platform access token. Get one on the Create an access token endpoint by exchanging your client_id + client_secret, then send it as Authorization: Bearer <token>. Tokens live one hour.
Query Parameters
The connected user's id.
Response
The attachment.
card_attachment The attachment id.
pending — the user has not finished the attach link. active — attached; create_card now mints against this card. ineligible — this card cannot be attached; fall back to wallet funding + create_card.
pending, active, ineligible The hosted link the user opens to add their card. Present only on the start response.
When the attach link expires (48 hours). Present only on the start response.
Display details of the attached card. Present when status is active.
Why the card cannot be attached (e.g. issuer_excluded, commercial_card). Present when status is ineligible.
Human-readable guidance. Present when status is ineligible.