Skip to main content
POST

Authorizations

Authorization
string
header
required

An access token (at_test_… or at_live_…) from POST https://idp.talescria.com/oauth/token.

Headers

Idempotency-Key
string
required

A unique key for this operation. Send the same key when you retry it. Kept for 24 hours.

Required string length: 8 - 255
Pattern: ^[A-Za-z0-9_\-:.]+$

Path Parameters

recipientId
string
required

Body

application/json
method
enum<string>
required
Available options:
bank_transfer,
mobile_money,
stablecoin,
internal_transfer
currency
string
required

ISO 4217, or USDC. Upper-cased for you.

accountHolderName
string
required

Whose name is on the account, which is not always the recipient's.

Maximum string length: 200
fields
object
required

The rail's own fields, keyed exactly as GET /v1/destination-requirements declares them. Open on purpose: a new corridor adds keys without a change to this schema.

Example:
country
string

ISO 3166-1 alpha-2. Required for every rail but stablecoin.

Required string length: 2
scheme
string

The rail. Required where a corridor offers more than one (ach/wire/rtp over USD); for a stablecoin destination this is the chain. GET /v1/destination-requirements lists the choices.

bankId
string

A bank from GET /v1/banks, instead of fields.bank_code. Talescria resolves it and fills whatever the corridor needs, the code, and the bank name where the rail demands one, so a form offering a picker collects neither. Sending both this and fields.bank_code is a 422 rather than one silently winning.

Example:

"bk:NG:058"

Response

Created and attached to the recipient.

destination
object