USD Remote Bank Account — ACH and Wire Transfer Methods Documented

What changed

The account_details schema for the USD variant on POST /stablecoin/user/bank-account/remote has been corrected to match the REST API contract. The previous schema was missing the transfer_method field and used the wrong field name for the routing number, so consumers could not request a wire transfer through the documented payload.

Before

{
  "account_details": {
    "currency": "USD",
    "account_number": "12365498",
    "bank_code": "026009593",
    "bank_name": "Bank of America"
  }
}

After

{
  "account_details": {
    "currency": "USD",
    "transfer_method": "WIRE",
    "account_number": "12365498",
    "routing_number": "026009593"
  },
  "recipient_type": "THIRD_PARTY",
  "third_party_details": {
    "recipient_first_name": "John",
    "recipient_last_name": "Doe",
    "recipient_address_line": "123 Main St",
    "recipient_country": "US",
    "recipient_state": "NY",
    "recipient_postal_code": "10001",
    "recipient_city": "New York"
  }
}

Field changes

Field	Before	After
`transfer_method`	missing from spec	required, `"ACH"` or `"WIRE"`
Routing field name	`bank_code`	`routing_number` (9 digits, ABA)
`account_number`	no length constraint	digits only, 8–12 characters
`bank_name`	required	removed (not used by the API)
`third_party_details`	missing from spec	required when `recipient_type` is `THIRD_PARTY` and `transfer_method` is `WIRE`

Behaviour notes

ACH transfers require only currency, transfer_method: "ACH", account_number, and routing_number.
Wire transfers require transfer_method: "WIRE". When the recipient is a third party, the wire rail also requires third_party_details (recipient name and full US address).
The underlying REST API contract has not changed; this is a documentation fix so the OpenAPI spec accurately describes the existing endpoint.