ForgePay: The Value Bridge

Chain-Agnostic Sovereign Payments for ForgeChainOS

Version: 2.1 (corrections + what shipped after v2.0)

Author: Jack Mosel / ForgeChainOS

Date: October 22, 2026

v2.0 Chain-Stamped: 8824ab73...5926aa (October 22, 2026) · read v2.0 as stamped

v1.0 Chain-Stamped: 1f524ab5...2aa051 (March 12, 2026)

Status: LIVE in production at theforgechain.com

Abstract

ForgePay is the payment and settlement layer for ForgeChainOS. Version 1.0 (March 2026) described the architecture. Version 2.0 describes what is running.

As of October 2026, ForgePay is live at theforgechain.com with 19 products, 4 subscription tiers, 12 accepted currencies, automatic on-chain verification across 9 blockchains, and a machine-readable discovery flow that lets any agent walk from zero knowledge to a completed purchase without human intervention.

ForgePay is priced in US dollars. Customers pay in whatever they hold: USD via PayPal, USDC on Base or Solana, RLUSD, BTC, ETH, XRP, XLM, ALGO, XDC, BSV, or WLF1. The x402 gate freezes a live quote for 30 minutes in every currency. The customer pays one. forge-pay-verify reads the chain and confirms.

FORGEENTERPRISE, the commercial backbone of ForgeChainOS, routes all commerce through ForgePay. 80 enterprise residents. Tier-based access. Every transaction verified, every order deterministic, every endpoint documented to 6 Sigma Transducer readiness: an agent with no prior knowledge discovers, orders, pays, and provisions without ambiguity.

0. What Changed in v2.1 (October 22, 2026)

v2.0 described the gate a few hours before it gained machine-readable failure codes, per-source limits and an invoice rail. v2.1 corrects v2.0 where it promised more than the gate did, and documents what shipped since. Where v2.0 and v2.1 differ, v2.1 is the running system.

Shipped after v2.0:

• Invoice rail. forge-invoice bills any dollar amount; the client pays at /pay?o=FO-... in USD (PayPal) or any listed currency. GET /api/x402/order/{id} shows one order (no client name); POST /api/x402/order/{id}/requote refreshes a lapsed quote at the same dollar price. PayPal payments are recorded with forge-pay-verify markpaid into the same single-use ledger.
• Client ForgeStamp. Onboarded clients stamp from their portal: pick artworks, pay, the stamp is staged for Node Zero's Face ID, and a receipt with each SHA-256 fingerprint goes out after the fire. First client: Lilac Inn Art Gallery.
• Branded invoices. Eclipse Film Crew invoices run on the same rail at eclipsefilmcrew.com/pay.

1. What Changed: v1.0 to v2.0

v1.0 remains chain-stamped and canonical as the founding architecture. v2.0 is the operating reality.

2. The Problem (Unchanged, Confirmed)

The payment stack is still broken. Stripe still charges 2.9% + $0.30. PayPal still charges 2.99%. Cross-border wires still cost $25-50 and take 1-5 days.

What changed since March 2026:

• USDC is now native on Base (fees under $0.01) and Solana (fees under $0.001).
• Ripple launched RLUSD, a regulated stablecoin.
• The AI agent economy emerged: agents need to discover services and pay programmatically. No agent can fill out a Stripe checkout form.

ForgePay solves both the human payment problem and the agent payment problem with the same flow.

3. Architecture: What Is Running

3.1 The x402 Gate

The x402 gate is the payment surface of ForgeChainOS. It lives at theforgechain.com and speaks a protocol called x402-forgechain-v1.

Endpoints:

Response codes:

• 200 Paid and verified
• 202 Not decided yet: pending (awaiting confirmation), manual (confirmed by hand), unknown (chain unreachable; nothing decided)
• 400 The request or order is wrong: missing/malformed fields, order_expired, order_not_found, currency_not_quoted, order_not_open
• 402 The payment is wrong: amount_mismatch, wrong_address, txid_reused, tx_predates_order, tx_not_found, tx_invalid

Constraints:

• Quotes expire in 30 minutes
• Rate limit: 100 orders per hour per source (hashed), 1,000 per hour overall
• Each txid pays exactly one order (replay protection)
• Transaction must be newer than the order (time-gate)

3.2 Currency Matrix

ForgePay prices everything in US dollars. When a customer chooses a currency, forge-quote freezes a live rate for 30 minutes.

Stablecoin peg logic: USDC and RLUSD quote 1:1 (a $8 order asks for 8.00 USDC). If a stablecoin depegs more than 2%, the live market rate is used instead. This protects both sides.

Automatic verification: forge-pay-verify reads the destination chain directly. It confirms: right address, right amount (within tolerance), finality reached, transaction newer than the order, and txid not reused. EVM chains try multiple RPCs so a single rate-limited node is not a verdict.

3.3 The Verification Engine

forge-pay-verify is a standalone verifier. It takes an order ID, a currency, and a txid. It reads the chain. It returns a verdict.

POST /api/x402/verify
{
  "order_id": "FO-20261022-a1b2c3",
  "currency": "USDC-BASE",
  "txid": "0xabc123..."
}

200: { "status": "paid", "verified": true, "reason": null, "reasons": [], ... }
402: { "status": "rejected", "verified": false, "reason": "amount_mismatch",
       "reasons": ["amount_mismatch"], "why": ["paid 5000000 base units to 0x88C6..., need >= 7920000"] }
400: { "status": "rejected", "verified": false, "reason": "order_expired", "reasons": ["order_expired"] }
202: { "status": "pending", "verified": false, "reason": "awaiting_confirmation" }

Verification is deterministic. The same inputs always produce the same output. There is no human judgment in the automatic path. The chain is the truth.

3.4 Internal Components

4. Product Catalog

4.1 Individual DApp Licenses

4.2 Subscription Tiers

5. Onboarding: Three Doors

5.1 Agent-to-Agent (Zero Human)

This is the 6 Sigma Transducer path. An agent with no prior knowledge of ForgeChainOS completes a purchase:

1. DISCOVER
   Agent fetches /.well-known/agent-card.json
   → learns: Anna (public agent), A2A at /a2a/v1
   Agent fetches /.well-known/agents.json
   → learns: agent registry, domain, protocols
   Agent fetches /.well-known/x402-capabilities.json
   → learns: products, tiers, currencies, wallets, flow steps

2. BROWSE
   GET /api/x402/order
   → 19 products with USD prices and descriptions
   Agent selects a product.

3. ORDER
   POST /api/x402/order { "item": "forgetransducer", "qty": 1 }
   → Response: order_id, amounts in every currency, pay_to addresses, expires_at
   Agent picks a currency (e.g., USDC on Base).

4. PAY
   Agent sends 18.75 USDC to 0x88C670AaE81fafA583CB591E60c7C20BfAA607C0 on Base.
   Waits for finality.

5. VERIFY
   POST /api/x402/verify { "order_id": "FO-20261022-...", "currency": "USDC-BASE", "txid": "0x..." }
   → 200: paid.

6. PROVISION
   Node Zero is notified on the verified payment and provisions the product
   (for ForgeTransducer: the manifest; the agent becomes discoverable).
   Fully automatic provisioning is on the roadmap.

Every step is a documented HTTP call. Every response is JSON. Every failure has a code and a reason. An agent that can read JSON and sign a transaction can complete this flow without asking anyone.

6 Sigma Transducer criteria:

• Zero ambiguity in endpoint discovery (well-known URLs)
• Zero ambiguity in order flow (4 steps, documented)
• Zero ambiguity in verification (deterministic, chain-based)
• Zero manual intervention for 10 of 12 currencies
• Explicit failure states at every step (400, 402, timeout)
• Rate limiting and replay protection built in

5.2 Human Self-Serve

A human visits theforgechain.com:

1. Talks to Anna (public resident agent): "I want a ForgeTransducer license"
2. Anna explains the product and walks them to the order flow
3. Human places an order (Anna can guide the POST)
4. Human pays via PayPal (invoice generated) or sends crypto
5. Verification: automatic for crypto, manual for PayPal
6. Product delivered, onboarding email sent

5.3 Enterprise

For organizations that need custom tiers, volume pricing, or dedicated infrastructure:

1. Contact: contact@theforgechain.com or IRC #transducer on forgeirc.forgechainos.com
2. Discovery call with Node Zero (Jack Mosel)
3. Custom tier scoped (SOVEREIGN or IMPERIAL base, custom FORTH, dedicated NOAH)
4. FORGEENTERPRISE resident onboarding: sovereign IPv6 ULA assigned, FORGELIFERAFT provisioned, jail created
5. Ongoing: FORGEENTERPRISE manages the resident. ForgePay handles all billing.

6. How We Use It: Internal Commerce

ForgePay is not just for external customers. It is the internal commerce layer of ForgeChainOS.

6.1 FORGEENTERPRISE

FORGEENTERPRISE is the commercial backbone. It runs on BH (tile-9, sovereign ULA fd00:db8:ff:9:c8a3:a86a:6f2b:1f3e) and manages 80 registered residents.

Every commercial action in ForgeChainOS routes through FORGEENTERPRISE:

• Tier assignment and enforcement
• Resident provisioning (FORGELIFERAFT, PIXEL containers, jail creation)
• Usage metering
• Revenue tracking

FORGEENTERPRISE consumes ForgePay for all payment operations. It does not handle money directly. ForgePay handles money. FORGEENTERPRISE handles identity, access, and provisioning.

6.2 The Commerce Stack

Customer (agent or human)
    |
    v
x402 Gate (theforgechain.com)
    |
    v
forge-quote (freeze live rate from prices.json)
    |
    v
Customer pays (chain or PayPal)
    |
    v
forge-pay-verify (read chain, return verdict)
    |
    v
FORGEENTERPRISE (provision resident, assign tier)
    |
    v
Product live (FORGELIFERAFT, ForgeTransducer, etc.)

6.3 Single Source of Truth

prices.json is the single source of all pricing. Everything derives from it:

• x402-capabilities.json (public listing) is generated from prices.json
• forge-quote reads prices.json to create orders
• FORGEENTERPRISE reads prices.json for tier enforcement
• Anna reads prices.json to answer pricing questions

Change the price in one place. Everything updates.

7. FORGEPAY as a DApp

ForgePay is a registered organ in the ForgeChainOS ecosystem.

FORGEPAY is not a standalone service. It is a capability within the forge-onboard surface, backed by the commerce/ toolchain. This is by design: the payment gate lives where the public surface lives. No separate process, no separate port, no separate failure domain.

8. Revenue Model

8.1 Pricing Philosophy

ForgePay uses fixed USD pricing, not spread-based conversion (as described in v1.0). The spread model assumed ForgePay would operate as a cross-chain DEX. In practice, ForgePay operates as a product gate: you buy a product, you pay the listed price in your chosen currency, the live exchange rate determines how much crypto that costs.

Revenue comes from product sales, not from conversion spreads. This is simpler, more transparent, and more predictable for both sides.

8.2 Revenue Range

Plus individual DApp license sales. ForgeStamp at $1 per stamp is a volume play. ForgeTransducer at $18.75 is the entry point for agent-native businesses.

8.3 Zero Internal Extraction

BSV-to-BSV operations within the ForgeChainOS family carry no ForgePay fee. Chain stamps, internal attestations, family operations: zero cost. ForgePay monetizes external access, not internal operations.

9. Security Model

• Non-custodial: ForgePay never holds customer funds. Payments go directly to ForgeChainOS wallets. Verification reads the chain after the fact.
• Deterministic verification: Same inputs, same output. No human judgment in the automatic path. The chain is the source of truth.
• Replay protection: Each txid pays exactly one order. A transaction used for order A cannot be reused for order B.
• Time-gating: The transaction must be newer than the order. Pre-existing transactions cannot be claimed against new orders.
• Rate limiting: 100 orders per hour per source. Prevents order flooding.
• Quote expiry: 30 minutes. Prevents stale-rate exploitation.
• Multi-RPC resilience: EVM verification tries multiple RPC providers. A single node failure is not a verdict.
• Peg safety rail: Stablecoin quotes are 1:1 unless the peg drifts more than 2%, at which point the live rate is used. This prevents paying $8 worth of USDC for a $100 product during a depeg.

10. Regulatory Positioning

ForgePay is a product sales platform with cryptocurrency payment acceptance. It is not an exchange, a swap protocol, or a money transmitter.

• Customers buy products (software licenses, daemon hosting, chain attestations). They do not buy or sell cryptocurrency through ForgePay.
• ForgePay accepts cryptocurrency as payment for products, the same way any merchant accepts Bitcoin.
• USD payments via PayPal use PayPal's existing regulatory framework.
• No KYC is required for individual product purchases. Tier subscriptions may require identity for provisioning (sovereign IPv6 assignment, jail creation).
• ISO 20022 compatibility is maintained via XRP and XLM payment paths for institutional interoperability.

11. Transducer Readiness: The 6 Sigma Standard

"6 Sigma Transducer ready" means an autonomous agent can discover, evaluate, order, pay, and provision a ForgeChainOS product without any human in the loop, with zero defects in the flow.

The standard:

1. Discoverable. /.well-known/agent-card.json and /.well-known/agents.json are live, valid JSON, and describe the public agent (Anna) and her capabilities.
2. Listable. /.well-known/x402-capabilities.json lists every product, every currency, every wallet address, every endpoint, and the complete 4-step flow. An agent reads this one file and knows everything.
3. Orderable. POST /api/x402/order accepts a product key and quantity, returns a frozen quote with amounts in every currency and pay-to addresses. The response is unambiguous.
4. Payable. The agent sends the exact amount to the exact address on the chain it chose. No intermediary. No approval flow. No waiting room.
5. Verifiable. POST /api/x402/verify reads the chain and returns a deterministic verdict. 200, 202, 400, or 402. Every rejection includes a machine-readable reason.
6. Provisionable. On 200, Node Zero is notified and provisions: a manifest for ForgeTransducer, a daemon home for FORGELIFERAFT, resident onboarding for tiers. Making this step fully automatic is the next milestone (roadmap).

Failure modes are explicit. An agent that receives a 402 reads reason: amount_mismatch, wrong_address, txid_reused, tx_predates_order, tx_not_found or tx_invalid. An agent that receives a 400 reads order_expired, order_not_found, currency_not_quoted or order_not_open, and knows what to fix. A 202 says pending, manual or unknown, and nothing has been decided. There is no silent failure.

The test: take an agent that has never heard of ForgeChainOS. Point it at theforgechain.com. It should complete a purchase within 6 HTTP calls and one on-chain transaction. If it can't, the gate has a defect.

12. Roadmap: What Is Next

Delivered (v2.1)

• x402 gate: live, 19 products, 12 currencies
• forge-pay-verify: automatic verification on 9 chains
• FORGEENTERPRISE: 80 residents, tier pricing
• Transducer discovery: agent-card, agents.json, x402-capabilities
• USDC on Base and Solana: live
• Stablecoin peg safety: live
• Machine-readable reason codes, 400/402 split, per-source limits: live (v2.1)
• Invoice rail (forge-invoice, /pay, requote, PayPal markpaid): live (v2.1)
• Client ForgeStamp from the portal, with receipts: live (v2.1)

Next

• Standard x402 compliance: align with the emerging x402 HTTP standard (exact scheme, USDC-native). Currently x402-forgechain-v1.
• Auto-provisioning: on verified payment, FORGEENTERPRISE creates the resident, assigns the ULA, and spins the jail without human intervention.
• Subscription billing: recurring tier payments with grace periods and auto-renewal.
• Volume discounts: enterprise pricing for 10+ seats.
• Additional currencies: as demand warrants. The architecture supports any chain with a public RPC.
• Micropayment channels: BSV payment channels for per-query and per-view pricing (ForgeStamp, ForgePlay, ForgeSci).

13. The Glue (Restated)

ForgePay is sovereign plumbing. It meets customers where they are (12 currencies, PayPal, agent-to-agent) and routes value where it needs to go (ForgeChainOS wallets on 9 chains).

The traditional payment stack charges 1.5-3% to move numbers between databases. ForgePay charges nothing for the conversion: you pay the listed price. The chain does the settlement. forge-pay-verify reads the chain and confirms. No middleman. No custody. No extraction.

FORGEENTERPRISE is the enterprise backbone. FORGEPAY is how it breathes. Together, they are the commercial layer of a sovereign operating system that runs on its own metal, its own IPv6, its own chain, and its own terms.

The phone is still ringing.

14. IP Declaration

This whitepaper and all concepts described herein are the intellectual property of Jack Mosel and ForgeChainOS. v1.0 chain-stamped on BSV (TX 1f524ab5). v2.0 chain-stamped on BSV (TX 8824ab73). v2.1 to be stamped.

The ForgePay x402 gate, forge-pay-verify chain verification engine, forge-quote deterministic pricing system, and the 6 Sigma Transducer readiness standard are original works.

BSV Address: 14LQvsvmTzztAPAQRnZ5Aq6nctAnVd9fMu

*ForgeChainOS, 2026. All IP on chain before publication. NODEZEROINSIDE.*