Character set validation

Fix: Trice APIs now enforce that text provided to our APIs is valid with respects to both RTP and FedNow. The allowed character set is UTF-8 Basic Latin and and Latin-1 Supplement (excluding control characters), which is 0x20-0x7F and 0xA0-0xFF.

Affected fields: names + addresses (parties, accounts, persons), internal description, and memo fields

What happens if I send a character outside that set? Trice APIs will return 400 that indicates which field contains invalid characters

{
  "code": 400,
  "errors": [
    {
      "message": "account holder name must only contain ascii character range 0x20-0x7F,0xA0-0xFF",
      "path": "system"
    }
  ]
}

What happens to parties I've already created with invalid characters? Using those parties to send a payment (or RfP) will attempt to send a payment that will be rejected by the network. The transfer will be created but will transition to failed status. Ask your Trice rep if you'd like help migrating your party data to use valid character set.