US • USD corridor

This section provides the field-level data requirements for creating identityIDs in the US • USD corridor.

identityIDs represent originators (senders) and beneficiaries (recipients). The required fields depend on:

• Identity Type: Originator or Beneficiary

• Use Case: Individual or Business

• Payout Method: ACH, RTP, or Wire

Ripple provides JSON schemas (via the Payment Data Requirements Utility) and matching field reference tables that define:

• Which fields are required or optional

• How each field is described in plain language

• Any validations applied (length limits, regex patterns, enumerated values)

How to use this section

1. Select a payout method (ACH, RTP, or Wire).

2. Open the method page to view four tables, one for each combination of Identity Type and Use Case:

   • Originator • Individual

   • Originator • Business

   • Beneficiary • Individual

   • Beneficiary • Business

3. Use the field reference tables (or the corresponding JSON schemas from the Utility) when constructing your identityID.

Available payout methods in US • USD

ACH (Automated Clearing House)

• Use case: Payouts into domestic bank accounts in the U.S. via US ACH (NACHA).

• Reference: US • USD • ACH Field Reference

• Highlights: Requires routing number (ABA), account number, and account currency.

RTP (Real-Time Payments)

• Use case: Near real-time payouts into domestic bank accounts in the U.S. via RTP or FedNow, depending on the beneficiary bank’s capabilities.

• Reference: US • USD • RTP Field Reference

• Highlights: Requires account information and additional validations for RTP routing.

Wire (Fedwire)

• Use case: Payouts into domestic bank accounts in the U.S. via Fedwire, outside of ACH or RTP rails.

• Reference: US • USD • Wire Field Reference

• Highlights: Requires bank name and account details; field set differs slightly from ACH and RTP.