Initiate a third-party crypto payment (approval-gated)
POST/payments/crypto
Initiates a third-party crypto payment for the selected entity. The beneficiary is either an
existing active address-book entry (beneficiaryId) or created inline (newBeneficiary) on the
entity primary; the payment may be funded from the primary or any of its sub-accounts.
The send is created marked for payment approval and debited into a hold (balance reserved, not send-requested) — it only proceeds once the approval is granted (approver MFA is the control). Reject/expire rolls back the reserved balance and cleans up an inline-created beneficiary.
Requires PAYMENTS_CREATE. Behind the paymentsWebEnabled feature flag (404 when off).
Request
Responses
- 202
- 400
- 401
- 403
- 404
- 409
Accepted — send created and held pending payment approval
Validation error, or neither/both beneficiary options supplied (PAYMENT_BENEFICIARY_DETAILS_REQUIRED)
Missing/invalid JWT or entity selection
Caller lacks PAYMENTS_CREATE, or the funding account is not in the entity (PAYMENT_SOURCE_ACCOUNT_NOT_IN_ENTITY)
Feature disabled (paymentsWebEnabled off), or beneficiary not found (PAYMENT_BENEFICIARY_NOT_FOUND)
Selected beneficiary is not active (PAYMENT_BENEFICIARY_NOT_ACTIVE)