422

API problem detail

Money-Movement Refusal

Description

This problem happens when $Verify, $Send, or $VerifyAndSend is refused by a compliance or payment-policy check. Most of these refusals are a raw 422 JSON body (not Problem Details) with errorCode and message, plus resolution and traceId. Some carry extra context fields: companyId for KYB/KYC, nextWindowEasternTime and retryAtUtc for the Same Day ACH cutoff, and amount and limit for the Same Day ACH limit. errorCode is stable and safe to branch on; message is human-readable and may change. No money moves.

Unresolved sanctions screening returns 409 Problem Details with errorCode and detail, plus payout-specific nextAction. Unverified payouts and pending consumer funding also return 409 through their own problem types.

errorCodeMeaning
KYB_KYC_NOT_PASSEDThe company's KYB/KYC verification is not confirmed.
BILLING_PAYMENT_METHOD_REQUIREDThe company has no chargeable billing payment method on file. Unlike the others, this refusal is a Problem Details body; see A payment method is required.
SAME_DAY_ACH_AFTER_CUTOFFSubmitted after the Same Day ACH window. retryAtUtc and nextWindowEasternTime give the next eligible time.
SAME_DAY_ACH_AMOUNT_LIMITAbove the per-transaction Same Day ACH limit.
SAME_DAY_ACH_PROVIDER_CONFIGURATIONSame Day ACH is not configured for the provider.
FUNDING_COMPANY_REQUIREDFunding must resolve to a company.
FUNDING_HOLDING_ACCOUNT_MISSINGNo eligible holding account exists.
FUNDING_HOLDING_ACCOUNT_AMBIGUOUSMultiple holding accounts require deliberate configuration.
FUNDING_HOLDING_ACCOUNT_INVALIDThe configured holding account is invalid.

Experience API error bodies also carry errorCode, resolution, and traceId. Branch on errorCode, not on title or detail; see fields on every error.

How to resolve

Resolve the named condition first: resolve company verification with DirecFunds, have a company administrator add a billing payment method, wait for the next Same Day ACH window (use retryAtUtc), lower the amount, or deliberately choose another rail. Then repeat the action with a new idempotency key. Do not retry the identical request unchanged; the refusal is deterministic until the condition changes.
Back to all problem details