Cross-Border Payment Pre-Validation

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Gated two-step chain for CBPR+ payment pre-validation. Step 1 checks whether a purpose code is mandatory for the beneficiary jurisdiction (UAE, India, Bahrain, Jordan, China, Malaysia per BIS CPMI d218) and whether SwiftGo eligibility conditions are met. Step 2 runs aggregate pre-validation (IBAN mod-97, BIC format, LEI format, UETR UUIDv4, PostalAddress24 structure) and emits a /ready boolean. The §21.4 decision gate on /ready records which branch was taken: ready=true exits STP-eligible, ready=false exits requiring remediation. No personal data is processed.

OpenChainGraph · 2 Steps compliance mandate · Gated Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII

Chain Stages · 2 Steps · Gated

1 ROOT node

ISO 20022 Purpose Code Requirement Checker art-243-purpose-code-requirement-checker

Checks whether a purpose code is mandatory for the beneficiary jurisdiction (UAE, India, Bahrain, Jordan, China, Malaysia per BIS CPMI d218) and whether SwiftGo eligibility conditions are met. Passes the requirement and eligibility result to aggregate pre-validation.

MCP Call · check_purpose_code_requirement

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_purpose_code_requirement",
    "arguments": {
      "beneficiary_country": "AE",
      "payment_amount_usd": 5000,
      "purpose_code": "TRAD",
      "category_purpose_code": "TRAD"
    }
  },
  "id": 1
}

↓

2 TERMINAL §21.4 gate

Cross-Border Payment Prevalidation Readiness Scorer art-247-prevalidation-readiness-scorer

GATE: /ready eq true → end | default → end (remediation)

Runs aggregate pre-validation (IBAN mod-97, BIC format, LEI format, UETR UUIDv4, PostalAddress24 structure) and emits a /ready boolean with per-check detail. Gate: ready=true exits STP-eligible; ready=false exits requiring remediation.

MCP Call · prevalidation_readiness_scorer

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "prevalidation_readiness_scorer",
    "arguments": {
      "iban": "DE89370400440532013000",
      "bic": "DEUTDEFFXXX",
      "lei": "00000000000000000001",
      "uetr": "550e8400-e29b-41d4-a716-446655440000",
      "address_street_name": "Kaiserstrasse",
      "address_building_number": "29",
      "address_post_code": "60311",
      "address_town_name": "Frankfurt",
      "address_country": "DE"
    }
  },
  "id": 2
}

Question: A client wants this payment routed over CBPR+. Do the identifiers and address on this instruction clear pre-validation? Run the AINumbers MCP tool `run_chain` with {"chain":"cross-border-payment-prevalidation"} and read `art-247-prevalidation-readiness-scorer.ready`. Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`. Ledger, for a human re-check: https://ledger.ainumbers.co/ PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads. Chain page: https://ainumbers.co/chaingraph/chains/cross-border-payment-prevalidation.html

Cross-Border Payment Pre-Validation

Ask your agent