Frequently Asked Questions
Everything you need to know about PostalIQ and CBPR+ compliance.
What is the SWIFT CBPR+ postal address deadline?
Starting November 2026, SWIFT will reject CBPR+ messages that contain only unstructured postal addresses (AdrLine without TwnNm and Ctry). All addresses must be in structured or hybrid format with at minimum a TownName and Country element.
What is the difference between structured and hybrid address format?
Structured format uses discrete XML elements for each component: StrtNm (street), PstCd (postcode), TwnNm (town), Ctry (country). Hybrid format combines AdrLine elements (max 2 × 70 chars) for street information with structured TwnNm and Ctry. Both are CBPR+ compliant.
Does PostalIQ require changes to my core banking system?
No. PostalIQ deploys as a Docker container between your backoffice and SWIFT. It intercepts messages, transforms the addresses, and forwards the compliant version. Your core banking system continues to operate exactly as before.
Is PostalIQ GDPR compliant?
Yes. PostalIQ runs entirely on-premise within your infrastructure. No message data leaves your network. The self-learning cache stores only address patterns, not personal information or message content. Full audit trail included.
What message types does PostalIQ support?
Currently PostalIQ supports pacs.008 (FI to FI Customer Credit Transfer), which covers the majority of CBPR+ payment messages. Support for pacs.009, pacs.004, and camt.056 is on the roadmap.
How does the self-learning cache work?
When an operator corrects an address in the review queue, that correction is cached. When the same (or similar) address appears in a future message, the cached correction is applied automatically — no manual review needed. The cache also learns from high-confidence automatic transformations.
Can I test PostalIQ with my own messages?
Yes. Send us 100 anonymized pacs.008 messages and we'll process them through PostalIQ within 24 hours, returning a detailed report showing how each address was transformed, the confidence scores, and any addresses that would require manual review.
What happens when PostalIQ can't resolve an address?
When the confidence score is below the threshold (default 70%), the address is routed to a review queue. Operators see the original address, the proposed transformation, and the reasoning. They can correct the address manually, and that correction feeds the learning cache.
What is SR 2026 and how does it affect postal addresses?
SR 2026 (Standards Release 2026) is SWIFT's annual update that takes effect in November 2026. The key change: all CBPR+ messages must use structured or hybrid PostalAddress24 format. Messages with only unstructured AdrLine elements will be rejected at the SWIFT network level. PostalIQ ensures your messages comply with SR 2026 automatically.
What is PostalAddress24 and what are its field limits?
PostalAddress24 is the ISO 20022 data type for postal addresses used in CBPR+ messages. Key fields: StrtNm (street, max 70 chars), BldgNb (building number, max 16 chars), PstCd (postcode, max 16 chars), TwnNm (town name, max 35 chars, mandatory), Ctry (country, ISO 3166 alpha-2, mandatory), and AdrLine (free text, max 70 chars x 2 lines in CBPR+ hybrid format).
What is the PMPG CUTOVER2026 placeholder?
CUTOVER2026 is a temporary placeholder recommended by the Payments Market Practice Group (PMPG) for the TwnNm field when the real town name cannot be determined. It signals to the receiving bank that the address needs manual review. PostalIQ uses this as a last resort when confidence is too low for auto-resolution, ensuring the message still passes SWIFT validation.
How does PostalIQ resolve the country from an unstructured address?
PostalIQ uses a 5-priority resolution chain: (1) Explicit Ctry element if present, (2) IBAN prefix (positions 1-2), (3) Agent BIC code (positions 5-6), (4) Clearing system code mapping, (5) Text analysis of country names in the address. Each source is cross-validated against others for accuracy.
Still have questions?
Contact Us