Skip to main content
POST

Authorizations

Authorization
string
header
required

Bearer token authentication, for client-server calls.

Send the access token issued by POST /v1/auth/token as Authorization: Bearer {token}. The token carries its own program and user context, so the X-Meridian-* headers are not required. See Authentication.

Headers

X-Meridian-Api-Key
string

Server-to-server (HMAC) requests only. Partner API key issued by Meridian during provisioning.

X-Meridian-Timestamp
string

Server-to-server (HMAC) requests only. Current time in milliseconds since the Unix epoch. Must be within 60 seconds of the request.

X-Meridian-Program-Id
string

Server-to-server (HMAC) requests only. Identifies the program context for the request.

X-Meridian-User-Id
string

Server-to-server (HMAC) requests only. Identifies the Meridian user targeted by the request. Required for MULTI_USER integrations; omit for SINGLE_USER.

Body

application/json

Beneficiary identity and first payout instrument

Create a person beneficiary together with its first instrument

firstName
string
required

First name

Example:

"Sherlock"

lastName
string
required

Last name

Example:

"Holmes"

address
Beneficiary Address · object
required

Address of the beneficiary's bank. Required by RouteFusion for non-US bank countries; a missing field is reported as a field-level validation error on submission.

instrument
Bank Account Instrument Request · object
required

Bank account instrument to create for a beneficiary

type
enum<string>
required

Beneficiary type discriminator

Available options:
PERSON,
BUSINESS
dateOfBirth
string<date> | null

Date of birth

Example:

"1854-01-06"

displayName
string | null

Human-readable display name for the beneficiary

Example:

"Sherlock Holmes"

email
string | null

Email address

phoneNumber
string | null

Phone number

phoneCountry
string | null

ISO 3166-1 alpha-2 country code of the phone number

Example:

"GB"

relationshipToUser
enum<string> | null

Beneficiary's relationship to the account owner

Available options:
SELF,
THIRD_PARTY,
null
Example:

"THIRD_PARTY"

Response

The newly created beneficiary

A person beneficiary

id
string
required

Unique identifier of the beneficiary

Example:

"uscp-01JMERBENEF001"

counterpartyId
string
required

Identifier of the underlying counterparty

Example:

"uscp-01JMERBENEF001"

createdAt
string<date-time>
required

Timestamp when the beneficiary was created

Example:

"2026-04-30T14:00:00Z"

updatedAt
string<date-time>
required

Timestamp when the beneficiary was last updated

Example:

"2026-04-30T14:00:00Z"

type
enum<string>
required

Beneficiary type discriminator

Available options:
PERSON,
BUSINESS
firstName
string | null

First name of the beneficiary

lastName
string | null

Last name of the beneficiary

dateOfBirth
string<date> | null

Date of birth of the beneficiary

displayName
string | null

Display name of the beneficiary

email
string | null

Email address of the beneficiary

phoneNumber
string | null

Phone number of the beneficiary

address
Beneficiary Address · object | null

Address of the beneficiary's bank. Required by RouteFusion for non-US bank countries; a missing field is reported as a field-level validation error on submission.

relationshipToUser
enum<string> | null

Beneficiary's relationship to the account owner

Available options:
SELF,
THIRD_PARTY,
null
Example:

"THIRD_PARTY"