OpenChainGraph Suite · OCG v0.8.0 · Cross-Border B2B

Cross-Border Payment Cost Check

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.

Three independent recomputes on your cross-border payment. Step 1 itemizes the invoice's cost stack: FX spread, method fee, VAT or reverse-charge, documentary-credit, and reconciliation cost, as a percentage of invoice value. Step 2 recomputes the corridor's declared cost gap against the hardcoded G20/FSB roadmap targets for the year you declare. Step 3 models the same corridor on a USDC stablecoin rail so you can see the cheaper alternative side by side. Every figure is caller-declared; the page makes no live FX or rate calls. No personal data is processed.

OpenChainGraph · 4 Steps analytics mandate Hash-Anchored §4 chain_depth:4 Client-Side · Zero PII
Not FX, investment, or legal advice. Step 1 itemizes caller-declared cost figures; Step 2 is a transparency benchmark against G20/FSB roadmap targets, not a compliance verdict against any firm; Step 3 models a generic USDC corridor, not a recommendation to use any rail or provider. Confirm pricing with your provider before acting.
Chain Topology: B2B Fee Stack → G20/FSB Target Gap → Stablecoin-Rail Alternative → Session Receipt
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 4 Steps
1 ROOT node
Cross-Border B2B Fee Calculator art-367-compute-cross-border-fees
Itemizes the caller-declared cross-border B2B invoice cost stack: FX spread cost, method/correspondent fee, VAT or reverse-charge cost, documentary-credit cost, and reconciliation cost, plus total cost as a percentage of invoice value
MCP Call · compute_cross_border_fees
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_cross_border_fees",
    "arguments": {
      "origin_country": "US",
      "dest_country": "GB",
      "invoice_amount": 10000,
      "fx_spread_bps": 150,
      "method_fee": 25,
      "vat_rate": 0,
      "doc_cost": 0,
      "recon_cost": 0
    }
  },
  "id": 1
}
↓
2 STEP node
G20/FSB Corridor Cost-Gap Calculator art-549-g20-corridor-cost-gap
Recomputes the caller-declared corridor cost gap in basis points against the hardcoded G20/FSB target for the declared year, with a meets_target verdict
MCP Call · check_g20_corridor_cost_gap
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_g20_corridor_cost_gap",
    "arguments": {
      "as_of": "2026-10-01",
      "corridor_pair": {
        "send_country": "US",
        "receive_country": "MX"
      },
      "observed_cost_bps": 250,
      "send_amount_basis": "USD_200",
      "target_year": 2027
    }
  },
  "id": 2
}
↓
3 STEP node
Stablecoin Corridor Economics Model art-250-model-stablecoin-corridor-economics
Models the all-in cost of the same corridor on a USDC stablecoin rail (on-ramp, chain fee, off-ramp, FX spread, float savings) against the traditional correspondent benchmark, with break-even send amount
MCP Call · model_stablecoin_corridor_economics
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "model_stablecoin_corridor_economics",
    "arguments": {
      "send_amount_usd": 10000,
      "on_ramp_fee_pct": 1.0,
      "chain_fee_usd": 0.01,
      "off_ramp_fee_pct": 0.8,
      "fx_spread_pct": 0.5,
      "correspondent_cost_pct": 6.0
    }
  },
  "id": 3
}
↓
4 TERMINAL node
Agent Action Audit Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Produces session_receipt_root, the Merkle root over the run's execution_hashes (final stage)
MCP Call · aggregate_execution_receipts
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "arguments": {
      "artifacts": [
        ""
      ]
    }
  },
  "id": 4
}
Export Chain Artifact
Download a §4-compliant chain artifact with execution hash and step definitions. Hash is deterministic over canonical {policy_parameters, output_payload} per RFC 8785/JCS.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: My supplier invoiced $10,000 from Germany with a 1.5% FX spread and $25 wire fee. What is the true all-in cost and does the corridor meet the G20 target?
Run the AINumbers MCP tool `run_chain` with {"chain":"cross-border-payment-cost-check"} and read `art-367-compute-cross-border-fees.total_cost`.
Re-run with `inputs` for `art-367-compute-cross-border-fees`, reusing the values that result echoed, with `fx_spread_bps` set to 300. 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/cross-border-payment-cost-check.html