Skip to main content

Overview

Link a payout destination (debit card) for an entity using an application token. The token is passed in the URL; no Bearer auth is required for this endpoint. Typical flow:
  1. Obtain an application token (e.g. account-widget token).
  2. Call this endpoint with the token, currency, option CARD, step (e.g. 1), and the required body.
  3. On success, use the returned data.id for payouts (e.g. Withdraw to Linked Account).
Supported (USD): CARD – Debit card (push-to-card).

Endpoint

  • POST {{LIQUIDITY_URL}}/v1/ext/application-token/:token/linked-accounts/:currency/link/:option/:step
  • Auth: None (token is in the URL). Do not send Authorization header.
  • Headers: Content-Type: application/json required.

Path Parameters

Request Body

Every request must include:

CARD – data fields

Request Example

Personal card

Response

Success (200)

  • Use data.id when calling the withdrawal endpoint:
    POST /v1/ext/linked-accounts/{currency}/{linkedAccountId}/withdrawal

Error (4xx / 5xx)

Typical Error Cases

Validation Summary

  • label – Required, any non-empty string.
  • option – Required, CARD (must match path).
  • data – Required; structure as above.
  • recipientType – Required; personal or business.
  • cardNumber – Exactly 16 digits.
  • cardExpirationDateYYYY-MM.

Notes for Integrators

  • Obtain a valid application token (account-widget type) before calling this endpoint.
  • Use the returned data.id when calling the external withdrawal API.
  • For CARD, payouts are push-to-card regardless of routing.
  • Do not send card number in logs or client-side storage; treat as sensitive.
  • Same endpoint is used for non-external path with token in URL; external path is POST /v1/ext/application-token/{token}/linked-accounts/{currency}/link/{option}/{step}.