United States: USD

Supported payment rails

Rail	Description	Settlement	Limit
`RTP`	Real-Time Payments. 24/7/365 availability.	Under 5 minutes	$5,000,000
`ACH`	Automated Clearing House. Business days only. Cut-off 3:00 PM EST.	Same-day	$1,000,000
`FEDWIRE`	Fedwire Funds Service. U.S. business days and operating hours. Cut-off 5:00 PM ET.	Real-time gross settlement	No limit

Routing order between RTP and ACH: RTP is used when the beneficiary account is RTP-addressable and the amount is at or below $5,000,000; otherwise ACH applies. Use US_FEDWIRE as a separate financial instrument when Fedwire is required for high-value transfers.

For details on rail selection, see Payment rail reference.

Identity address field constraints (USD-specific)

The payout partner enforces stricter formatting on identity address fields than the base identity schema requires. Values that pass identity creation may still cause payment failures if the format does not match.

Field	Constraint
`address.stateOrProvince`	Use the 2-letter USPS state abbreviation (for example, `NY`, `CA`, `TX`). Full state names such as `New York` are not accepted. For Puerto Rico, use `Puerto Rico` (not `PR`). Pattern: `^[A-Za-z]{2,25}$`

These constraints apply to all identity address fields used in USD payments (beneficiary and originator).

Beneficiary identity

When creating a beneficiary identity for USD payments, provide the following fields. See Create and manage identities for the API workflow.

The required fields depend on whether the beneficiary is a business or an individual.

Business beneficiary

Applies to B2B, B2B2B, and C2B2B use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	See USD-specific constraints above.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Individual beneficiary

Applies to B2C, B2B2C, and C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	1–140 characters.
`lastName`	Required	STRING	1–140 characters.
`dateOfBirth`	Required for `US_ACH`; optional for `US_FEDWIRE`	DATE	ISO 8601 date (YYYY-MM-DD).
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	See USD-specific constraints above.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Beneficiary financial instrument

When creating a financial instrument for USD payouts, set currency: USD and select the financial instrument type based on the rail. See Create and manage financial instruments for the API workflow.

ACH and RTP

Set financialInstrumentType: US_ACH. The system selects between RTP and ACH at payment time based on the routing order. Provide the following fields in the usAch payment rail object.

Field	Required	Type	Constraints
`bankName`	Required	STRING	2–140 characters.
`bankRoutingNumber`	Required	STRING	Exactly 9 digits (ABA Routing Transit Number).
`accountNumber`	Required	STRING	4–21 digits.
`accountType`	Required	ENUM	One of: `CHECKING`, `SAVINGS`.

Fedwire

Set financialInstrumentType: US_FEDWIRE. Provide the following fields in the usFedwire payment rail object.

Field	Required	Type	Constraints
`bankName`	Required	STRING	2–140 characters.
`bankRoutingNumber`	Required	STRING	Exactly 9 digits (ABA Routing Transit Number).
`accountNumber`	Required	STRING	4–21 digits.

Originator identity

When creating an originator identity for USD payments, provide the following fields. The required fields depend on whether the originator is a business or an individual.

Business originator

Applies to B2B, B2B2B, B2B2C, and B2C use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	See USD-specific constraints above.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Individual originator

Applies to C2B2B and C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	1–140 characters.
`lastName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	See USD-specific constraints above.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Transaction fields

When creating a payment, provide the following fields. See Create a payment for the API workflow.

Field	Required	Type	Constraints
`purposeCode`	Required	ENUM	See Purpose of payment codes below.
`paymentMemo`	Optional	STRING	0–500 characters. Pattern: `^[\w #@!,.&()\/\\-]{0,500}$`

Purpose of payment codes

Code	Description
`ACCT`	Account management
`EDUC`	Education
`FAMI`	Family support related payments
`FEES`	Payment of fees
`GDDS`	Purchase or sale of goods
`INSU`	Insurance premium
`IVPT`	Invoice payment
`ROYA`	Royalties
`SALA`	Salary payment
`SAVG`	Savings
`SCVE`	Purchase or sale of services
`UBIL`	Utility bill payments

Verifying requirements for your scenario

For the exact fields required for your specific use case and payment rail, use the Payload Schema Utility.