Skip to main content
GET
Get the attachment status

Statuses

  • pending — the user hasn’t finished the attach link. Nudge them to complete it; poll again after.
  • active — attached. card carries 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; reason says why (for example issuer_excluded, commercial_card). Fall back to wallet funding and create_card.
A 404 no_attachment means nothing was ever started for that user — begin with Start a card attachment.

Authorizations

Authorization
string
header
required

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

user_id
string
required

The connected user's id.

Response

The attachment.

object
enum<string>
required
Available options:
card_attachment
id
string
required

The attachment id.

user_id
string
required
status
enum<string>
required

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.

Available options:
pending,
active,
ineligible
attach_url
string

The hosted link the user opens to add their card. Present only on the start response.

expires_at
string<date-time>

When the attach link expires (48 hours). Present only on the start response.

card
object

Display details of the attached card. Present when status is active.

reason
string

Why the card cannot be attached (e.g. issuer_excluded, commercial_card). Present when status is ineligible.

message
string

Human-readable guidance. Present when status is ineligible.