Send nxosnet transfer
Send an internal Nxosnet transfer from an account to an NXOSNET
beneficiary. Funds move directly between the two Nxosnet accounts as ledger
entries — there is no external rail — so the transfer settles instantly and
the response status is COMPLETED.
The beneficiary must be an NXOSNET type belonging to the source account
(create one via POST /v1/beneficiaries/nxosnet), and the target
organization must have Nxosnet transfers enabled.
Headers
Bearer token. Format: Bearer <api_key>
Unique key per logical operation. UUID v4 recommended. Max 255 characters.
Body
Request body for sending an internal Nxosnet transfer.
Source account to debit.
NXOSNET beneficiary to send to.
Transfer amount in major units (e.g. "100.00").
Asset code (e.g. USD, USDC).
Optional note, shown to the recipient.
Free-form tags (max 20 tags, each up to 100 characters).
Arbitrary metadata (max 50 keys, max 4 KB serialized).
Response
The request has succeeded.
A completed internal Nxosnet transfer.
Object type. Always transaction.
transaction Unique transaction identifier.
Transaction type. Always NXOSNET_TRANSFER.
NXOSNET_TRANSFER Transaction status. Always COMPLETED — internal transfers settle instantly.
COMPLETED Source account.
Target beneficiary.
Transfer amount in major units.
Asset code.
The recipient organization's nxosnet handle.
When the transaction was created.