charset

charset

HTTP 422 Unprocessable Content
Content-Type: application/problem+json

{
  "type": "https://docs.transmute.403fin.io/errors/charset",
  "title": "...",
  "status": 422,
  "detail": "...",
  "requestId": "req_01J..."
}

The message contains characters that cannot be represented — or transliterated under the selected profile — in the target format's character set (the SWIFT X charset for MT targets).

Common causes

• Non-Latin script or unusual symbols in party names/remittance heading to an MT target
• A strict transliteration profile that refuses replacements the default profile would make

How to fix it

Try options.translitProfile (base covers most European characters; german handles umlauts per German banking convention). If specific characters still fail, the response detail names their positions — never their values.

Does it bill?

Yes on a live key. See Test vs Live Keys for the full billing rules.

Related

• Errors Overview — the problem+json shape and the closed catalog
• Every response carries an X-Request-Id; quote it when contacting support.