---
title: "CBPR+ SR2026 Structured Address Pre-Flight"
method: POST
path: "/v1/tools/cbpr_sr2026_address_preflight"
tags: ["CBPR+", "SR2026", "ISO 20022", "Swift", "structured address", "pacs.008", "pain.001", "camt"]
---

# CBPR+ SR2026 Structured Address Pre-Flight

`POST /v1/tools/cbpr_sr2026_address_preflight`

## Request

- Base URL: `https://ainumbers.co`
- URL: `https://ainumbers.co/v1/tools/cbpr_sr2026_address_preflight`
- Auth: none declared

Classify each party and agent postal address in a CBPR+ payment message as structured, hybrid, or unstructured per message type. Flags addresses Swift will hard-reject at CBPR+ network level once the structured-address requirement takes effect (formerly 14 November 2026; deferred by Swift on 27 August 2026 under a controlled extension of Standards Release 2026, new date not yet published), per the message-type exemption list, hybrid definition, and agent BIC-only rule published in Swift's CBPR+ SR2026 guidance. Client-side. Works offline. Zero PII.

**Tool URL:** https://ainumbers.co/tools/632-cbpr-sr2026-address-preflight.html
**AP2/Policy Mandate export:** yes

## Request body

- object
  - `msgType` 'pacs.008' | 'pacs.009' | 'pain.001' | 'camt.052' | 'camt.053' | 'camt.054' | 'camt.025' | 'camt.060' | 'admi.024', required
  - `parties` unknown[]
    - unknown

## Response `200`

Successful tool execution result

- object
  - `verdicts` unknown[]: Per-party verdict: PASS-structured, PASS-hybrid, PASS-exempt, or FAIL-reject, with missing-field list and hybrid rendering where applicable
    - unknown
  - `reject_count` number

---

[API](https://skmtc.dev/ainumbers/apis/ainumbers-co-fintech-intelligence-suite.md) · [All operations](https://skmtc.dev/ainumbers/apis/ainumbers-co-fintech-intelligence-suite/llms.txt) · [OpenAPI document](https://skmtc.dev/ainumbers/apis/ainumbers-co-fintech-intelligence-suite/revisions/b462e4f5bb28?raw)