Skip to main content
POST
Start an attachment (member token)
The member-token twin of Start a card attachment: same attachment rows, same hosted page, authenticated as the member instead of naming them with user_id. In sandbox this seeds an instantly-active test enrollment, so an agent can rehearse the whole add-then-create flow with no browser step.

Authorizations

Authorization
string
header
required

The user's connection access_token (user authentication), or an org-minted buy_token for org-owned accounts.

Response

A card is already attached.

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.