TIPS Character Replacement

Character Replacement Approach

The TIPS CSM Service utilizes the SEPA Conversion Table to replace unsupported characters, ensuring strict adherence to SEPA standards.

Applicable Flows

The system handles character replacement and validation in the following order:

  1. Schema Validation : The system first validates the message against the scheme schema.

  2. Character Replacement : If valid, the system applies character replacement rules.

This logic applies to both the Validation API response and the message generated during Execution before submission.

Configuration Capability

SEPA character replacement configuration is enabled by default, and can be toggled using the below configuration.

Default Configuration

character-replacements {
  lookup-table-replacer {
    enabled = true
  }
}

Multi-Character Replacement Behaviour

Although TIPS uses the SEPA Conversion Table, it does not implement SEPA’s recommended multi-character conversions, to avoid field length validation errors or possible truncation.

To avoid this, TIPS deliberately overrides any SEPA mapping that would expand into multiple characters, and replaces such characters with a single full stop (.). This prevents unintended truncation.

Configuring Additional Overrides

If downstream implementers need to add additional overrides (on top of the ones already provided by TIPS), they can define these using the following pattern.

Each entry defines:

  • character-codepoint — the Unicode codepoint of the character to override

  • replacement — the single character it should be replaced with

Example: Customers wanting to replace Ê with a . would add the following override:

character-replacements {
  lookup-table-replacer {
    overrides += {character-codepoint = "\\u00ca", replacement = "."}
  }
}

Additional Customisation Options

To define or configure your own character replacer or to disable the feature entirely — refer to Character Replacement Documentation