Remittance Disclosure and Corridor Cost

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 Reg E remittance disclosure and corridor cost benchmarking. Step 1 computes the required CFPB Reg E subpart B (12 CFR 1005.31/1005.32) disclosure fields: transfer amount, exchange rate, amount received in destination currency, fees breakdown, and disclosure type. The gate reads /estimate_permissible: when true (12 CFR 1005.32 estimated disclosure applies), the chain exits with the ESTIMATED receipt: no corridor benchmarking required. When false (exact disclosure, the default path), Step 2 benchmarks total cost against the World Bank RPW Q1 2026 snapshot and SDG 10.c 3% target. 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 · GATE §21.4 gate

Remittance Disclosure Calculator (Reg E Subpart B) art-248-compute-remittance-disclosure

GATE: /estimate_permissible eq true → end (ESTIMATED receipt) | default → art-249-compare-corridor-cost

Computes required CFPB Reg E subpart B disclosure fields: transfer_amount_usd, exchange_rate_disclosed, amount_received_dest, fees breakdown, disclosure_type (EXACT or ESTIMATED), estimate_permissible flag, and accounting identity check. Gate on estimate_permissible: true exits with ESTIMATED disclosure (12 CFR 1005.32 estimated path); false proceeds to corridor cost benchmarking.

MCP Call · compute_remittance_disclosure

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_remittance_disclosure",
    "arguments": {
      "send_amount": 1000,
      "exchange_rate": 17.15,
      "provider_fee": 2.99,
      "third_party_fees": 0,
      "taxes": 0,
      "destination_currency": "MXN",
      "destination_country": "MX",
      "estimate_permissible": false
    }
  },
  "id": 1
}

↓

2 TERMINAL node

Corridor Cost Comparator (World Bank RPW) art-249-compare-corridor-cost

Benchmarks total cost (fee % + FX margin %) against World Bank RPW Q1 2026 snapshot for the origin-destination corridor, SmaRT global average (6.36%), and SDG 10.c 3% target. Returns meets_sdg_target, vs_rpw_benchmark, cost_at_200_usd, and cost_at_500_usd. Final stage.

MCP Call · compare_corridor_cost

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compare_corridor_cost",
    "arguments": {
      "from_country": "US",
      "to_country": "MX",
      "send_amount": 1000,
      "provider_fee": 2.99,
      "fx_rate_used": 17.15,
      "fx_rate_mid": 17.21,
      "service_name": "Felix-USDC-corridor"
    }
  },
  "id": 2
}

Question: A customer wants a 200 dollar transfer to Mexico. Does this corridor's all-in cost come in under the three percent target? Run the AINumbers MCP tool `run_chain` with {"chain":"remittance-disclosure-and-corridor-cost"} and read `art-249-compare-corridor-cost.meets_sdg_target`. Re-run with `inputs` for `art-249-compare-corridor-cost`, reusing the values that result echoed, with `provider_fee` set to 12. Compare the same field. 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/remittance-disclosure-and-corridor-cost.html

Remittance Disclosure and Corridor Cost

Ask your agent