Skip to content

United States (USD) Transaction Data Requirements

The following transaction-level fields apply to all USD payments to the United States, regardless of payment rail or use case.

Field Description RequiredTypeConstraints
purposeCodePurpose of paymentRequiredENUMSee valid values below
paymentMemoPayment memoOptionalSTRING0–500 chars.
Pattern: ^[\w #@!,.&()\/\\-]{0,500}$

Identity address field requirements

The following constraints apply to address fields on identities used in US USD payments. The payout partner enforces stricter formatting than the base identity schema allows, so values that pass identity creation may still cause payment failures if the format does not match.

Field Description RequiredTypeConstraints
stateOrProvinceState or territoryRequiredSTRINGUse 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}$

Purpose of payment codes

CodeDescription
ACCTAccount Management
EDUCEducation
FAMIFamily Support Related Payments
FEESPayment of Fees
GDDSPurchase or Sale of Goods
INSUInsurance Premium
IVPTInvoice Payment
ROYARoyalties
SALASalary Payment
SAVGSavings
SCVEPurchase or Sale of Services
UBILUtility Bill Payments