Skip to main content
POST
Create a Withdrawal
Legacy endpoint. This is part of the legacy withdrawal flow and will be deprecated. An upcoming Transactions Intent API will replace it. Avoid building new integrations against this endpoint — contact your Solutions Engineer for migration guidance.

Authorizations

X-Meridian-Signature
string
header
required

Meridian HMAC header authentication.

Required headers:

  • X-Meridian-Api-Key
  • X-Meridian-Timestamp
  • X-Meridian-Signature

X-Meridian-Signature is the HMAC SHA-256 signature of the canonical request string, computed per request as HMAC-SHA256(apiKey + timestamp + method + path + body). See Authentication for how to construct it.

Headers

X-Meridian-Api-Key
string
required

API key issued by Meridian during provisioning.

X-Meridian-Timestamp
string
required

Current time in milliseconds since the Unix epoch. Must be within 10 seconds of the request.

Path Parameters

userId
string
required

ID of the user initiating the withdrawal

accountId
string
required

ID of the virtual account to withdraw from

Body

application/json

Request body for creating a virtual account withdrawal transaction

amount
number
required

Amount to withdraw from the virtual account

Example:

50

quoteId
string
required

Quote ID for the withdrawal

Example:

"quote_01HT2P6W9PC2QV4W0Q63QMFJ44"

externalRef
null | string

A unique reference from your own systems used to identify and reconcile this transaction, such as a contract number, order ID, or internal transaction reference.

Example:

"order-2026-00142"

Response

The withdrawal was already processed for this quote; the existing transaction is returned (idempotent replay)

Response returned after creating a withdrawal transaction.

transaction
VirtualAccountTransactionDto · object | null

The created withdrawal transaction