POST/v2/payment-instrument/get-required-fields

Get Required Fields

Returns the dynamic field schema required to create a payment instrument for the given payment type. Call this before Create Payment Instrument.

Headers

Field	Type	Required	Possible values	Description
`Authorization`	string	Required	Bearer {SessionToken}	Session token from Get Session Token, sent as `Authorization: Bearer {SessionToken}`. Replace with the value from the `x-refresh-token` response header when present (typically within 2 minutes of expiry). Secured calls must use the same IP as the auth request.

Request body

Field	Type	Required	Possible values	Description
`PaymentType`	string	Required	BUS_USD_Account.Business_ACH \| BUS_USD_Account.Domestic_Wire_BUS \| BUS_USD_Account.BUS_International_Transfer (refer to Payment Types section)	Payment instrument type (e.g. ACH, domestic wire, international wire). See Payment Types in the API reference.

Example request

{
  "PaymentType": "BUS_USD_Account.Stablecoin_Withdraw"
}

Response

Field	Type	Possible values	Description
`ResponseCode`	integer	200 \| 201 \| 204 \| 400 \| 401 \| 403 \| 404 \| 410 \| 422 \| 500 \| 301 \| 503 \| 422	API result code in the response envelope. Indicates success or the error category (e.g. 200 success, 400 bad request, 401 unauthorized).
`ResponseMessage`	string	Success \| Created \| NoContent \| BadRequest \| Unauthorized \| Forbidden \| NotFound \| Gone \| UnprocessableContent \| ServerError \| ResourceMoved \| ServiceUnAvailable \| UnProcessableEntity	Human-readable label paired with ResponseCode (e.g. Success, BadRequest, Unauthorized). Use with ResponseCode to interpret the outcome.
`ResponseData`	object	Please refer to below example for response body	Dynamic field definitions required for Create Payment Instrument.

Example response

{
  "ResponseCode": 200,
  "ResponseMessage": "Success",
  "ResponseData": {
    "Fields": [
      {
        "Name": "BeneficiaryId",
        "Required": true,
        "Type": "Text"
      },
      {
        "Name": "Payment_Type",
  …

Requires `Authorization: Bearer {SessionToken}` from Get Session Token. Refresh via `x-refresh-token` when supplied; use the same client IP as authentication.