Initiate a third-party fiat payment (approval-gated)

POST 
/payments/fiat

Initiates a third-party fiat payment for the selected entity. The beneficiary is either an existing active one (beneficiaryId) or created inline (newBeneficiary) on the entity primary; the payment may be funded from the primary or any of its sub-accounts (the selected account).

The withdrawal is created marked for payment approval and debited into a hold — it only settles once the approval is granted (approver MFA is the control). Reject/expire reverses the debit and cleans up an inline-created beneficiary.

Requires PAYMENTS_CREATE. Behind the paymentsWebEnabled feature flag (404 when off).

Request

Responses

202

Accepted — withdrawal created and held pending payment approval

400

Validation error, or neither/both beneficiary options supplied (PAYMENT_BENEFICIARY_DETAILS_REQUIRED)

401

Missing/invalid JWT or entity selection

403

Caller lacks PAYMENTS_CREATE, or the funding account is not in the entity (PAYMENT_SOURCE_ACCOUNT_NOT_IN_ENTITY)

404

Feature disabled (paymentsWebEnabled off), or beneficiary not found (PAYMENT_BENEFICIARY_NOT_FOUND)

409

Selected beneficiary is not active (PAYMENT_BENEFICIARY_NOT_ACTIVE)