3.10.1 Hybrid Address

As of CBPRplus Usage Guidelines SR2025 and SEPA Rule Books 2025, the new hybrid (semi-structured) postal address is introduced, which mandates Town Name and Country as a minimum in their respective structured elements, and up to two occurrences of the unstructured Address Line elements of maximum length 70.

A new screen Network Address Preferences (Function ID: PMDNWADD), is provided to define the applicability of these categories based on Start Date / End Date. For a Network, it is possible to configure the priority for Structured / Unstructured / Hybrid address defaulting from customer/account address details. If the network level maintenance is not available, then a factory shipped static preference details (pmzm_hybrid_addr_pref) are also provided.

In addition to Structured / Unstructured address categories, Hybrid address is also to be supported for payment parties/agents. Payment outbound requests are validated for the applicability of the address category and for the correctness of the format used.

Changes are applicable for the below modules:
  • Generic wires – CBPRplus MX
  • SEPA Credit Transfer
  • SEPA Debit Transfer
  • SEPA Instant Credit Transfer
  • Foreign Currency Demand Drafts

Validation is added to check Country Code And/or Town Name of Structured address are appearing again in unstructured address lines for Hybrid address.

Exception handling preference on address format related validations can be configured in Source Network Preferences (Function ID: PMDSORNW). Transaction can be auto rejected or can be moved to Repair Queue.

In Generic Wires screens, address line length is increased to 70. Address fields are provided in Single payout screen/service for parties/agents.

If any repair validation is failed and the address fields are part of the fields to be repaired, system will list both Unstructured / Structured fields of the related Party/Agent for repair. Structured/Hybrid address is considered in EU Payer validations and in deriving address element values in Routing Rule.

The following SOAP/Rest services will support sending information in either structured address fields/address lines or both. The details received in service requests will get mapped to respective transaction fields.
  • SCT Instant outbound
  • SDD outbound/inbound
  • SCT inbound
  • SCT SI Template service
  • Generic wires SI Template services
  • Generic wires pacs.008 inbound service
  • Generic wires pacs.009 inbound service

Inbound files received are to be validated with updated xsd provided by SWIFT/SEPA.

Note: For inbound UI/service address details are to be provided as received in message. No address validation is added considering impact on R messages. There is no change BIC/Branch address fields.

Parent topic: Regulatory Changes