← Back to Whitepapers

ForgePay: The Value Bridge

A Whitepaper on Chain-Agnostic Sovereign Payments

Version: 1.0
Author: Jack Mosel / Forgechain OS
Date: March 12, 2026
Chain-Stamped: 1f524ab5...2aa051

Abstract

ForgePay is a chain-agnostic value bridge that enables seamless conversion between BSV, HBAR, XRP, USD1, and fiat currencies. It is the payment and settlement layer for the entire Forgechain ecosystem: every micropayment in ForgeVerse, every credential mint in ForgeSci, every file save in ForgeDrive, every transaction across every Forge product flows through ForgePay.

Unlike centralized exchanges that custody your funds, harvest your data, and charge 1-3% per transaction, ForgePay operates as a non-custodial bridge with spread-based revenue. You keep your keys. You control your funds. ForgePay converts between chains and takes a thin spread. That's it.

ForgePay is the glue. Without it, the Forge ecosystem is a collection of chain-specific tools. With it, the ecosystem becomes a unified economic system that speaks every chain language.

1. The Problem

1.1 The Payment Stack Is Broken

Every digital payment touches a chain of middlemen:

Layer Player Cut
Payment processor Stripe, Square 2.9% + $0.30
Card network Visa, Mastercard 0.13-0.15%
Issuing bank Chase, BofA 1.5-2.0% (interchange)
Platform Apple, Google, Gumroad 15-30%
Currency conversion Banks, Wise 0.5-3.0%

A $10 purchase costs the merchant $0.60-$3.30 in fees. A cross-border $10 purchase can cost $1.00-$4.00. The consumer pays the inflated price. The merchant eats the margin. The middlemen extract value for moving numbers between databases.

1.2 Crypto Exchanges Are the New Banks

Coinbase charges 1.49% per trade. Binance charges 0.1-0.6%. Both require KYC, custody your funds, and can freeze your account at will. They replaced banks with slightly cheaper banks that also track your transactions and report to governments.

Decentralized exchanges (Uniswap, PancakeSwap) solve custody but create new problems: gas fees ($2-50 per swap on Ethereum), MEV extraction (bots front-running your trades), impermanent loss for liquidity providers, and smart contract exploit risk.

1.3 The ISO 20022 Opportunity

As of March 2026, the global SWIFT migration to ISO 20022 messaging is complete. Every bank worldwide now uses the new standard. Cryptocurrencies built with ISO 20022 compatibility have a structural advantage:

ForgePay bridges the gap: BSV handles data and storage (cheap, permanent), while ISO 20022 chains handle institutional payment rails.

1.4 The Stablecoin Landscape

USD1 (World Liberty Financial) has reached $4.9B market cap, deployed on Ethereum, BNB Chain, Solana, Tron, and Monad. Backed by U.S. Treasuries and dollars held by BitGo Trust. This is real liquidity, real institutional backing.

USDC ($32B+), USDT ($140B+), and PYUSD (PayPal) provide additional stablecoin rails.

ForgePay doesn't compete with stablecoins. ForgePay ROUTES through them. When a ForgeVerse Parcel owner in Carmel, NY needs to pay a developer in Lagos, Nigeria, ForgePay finds the cheapest path: BSV to XRP to USD1 to local fiat, or whatever combination offers the lowest spread.

2. Architecture

2.1 Design Principles

  1. Non-Custodial: ForgePay never holds your funds. Atomic swaps or time-locked contracts ensure trustless exchange.
  2. Chain-Agnostic: BSV, HBAR, XRP, USD1, and expandable to any chain with programmable transactions.
  3. Spread Revenue: No flat fees. No percentage fees. ForgePay earns from the bid-ask spread on conversions. Transparent. Predictable.
  4. ISO 20022 Native: Transactions carry ISO 20022 compliant metadata where supported, enabling institutional interoperability.
  5. Micropayment Optimized: Sub-cent transactions must be economically viable. BSV enables this natively.

2.2 Supported Chains and Roles

Chain Role in ForgePay Transaction Cost Settlement Speed
BSV Data layer, micropayments, file storage, ecosystem backbone <$0.001 ~5 seconds
XRP Institutional bridge currency, cross-border settlement ~$0.0002 3-5 seconds
HBAR Credential layer (ForgeSci), DID/identity operations ~$0.001 3-5 seconds
USD1 Stablecoin settlement, fiat on/off ramp Varies by chain Chain-dependent
USDC/USDT Alternative stablecoin rails Varies by chain Chain-dependent

2.3 Conversion Flow

A typical cross-chain conversion:

USER SENDS: 1,000,000 sats (BSV)
           |
           v
  ForgePay Routing Engine
  - Checks BSV/XRP rate across liquidity sources
  - Calculates optimal path
  - Applies spread (0.1-0.5%)
           |
           v
  Atomic Swap: BSV -> XRP
  - Time-locked contract on BSV side
  - Corresponding lock on XRPL side
  - Both settle or neither settles
           |
           v
USER RECEIVES: XRP equivalent minus spread

For multi-hop conversions (e.g., BSV to USD1):

BSV -> XRP (atomic swap) -> USD1 (XRPL DEX or bridge)

ForgePay finds the cheapest route automatically. The user specifies source and destination. ForgePay handles the path.

2.4 Liquidity Model

ForgePay doesn't need massive liquidity pools to start. The model scales:

Phase 1: Aggregator
- Routes through existing exchanges and DEXs via API
- Takes a thin spread on top of market rate
- Zero liquidity risk. Zero capital requirement.

Phase 2: Direct Pairs
- ForgeClan members provide liquidity for BSV/XRP, BSV/HBAR pairs
- Liquidity providers earn spread revenue
- Smaller spreads than aggregated routes

Phase 3: Market Maker
- ForgePay maintains its own order book for high-volume pairs
- Tightest spreads. Fastest execution.
- Revenue from spread accumulates in ForgePay treasury

2.5 Micropayment Architecture

BSV enables true micropayments. A 1-satoshi transaction costs less than $0.001 in fees. This enables:

No other chain can economically process transactions this small. Ethereum charges $2-50 per transaction. Even XRP at $0.0002 per transaction becomes expensive at millions of micropayments per day.

BSV handles them at scale. ForgePay routes the value wherever it needs to go.

3. Revenue Model

3.1 Spread Revenue

ForgePay earns from the bid-ask spread on every conversion:

Volume Tier Spread Example on $100 swap
Standard 0.5% $0.50
ForgeClan Brother 0.3% $0.30
ForgeClan Elder 0.1% $0.10
Founding Father 0.05% $0.05

Compare to competitors:
- Coinbase: 1.49% ($1.49)
- Stripe: 2.9% + $0.30 ($3.20)
- PayPal: 2.99% ($2.99)
- Wire transfer: $25-50 flat

3.2 Revenue Projections

Conservative estimates based on ecosystem transaction volume:

Year Monthly Volume Avg Spread Monthly Revenue
Year 1 $50K 0.4% $200
Year 2 $500K 0.35% $1,750
Year 3 $5M 0.25% $12,500
Year 5 $50M 0.2% $100,000

These numbers are conservative. They assume only Forge ecosystem internal volume. External adoption (businesses using ForgePay for cross-border payments) would multiply these figures significantly.

3.3 Zero-Fee Internal Transfers

BSV-to-BSV transfers within the Forge ecosystem carry no ForgePay spread. Only cross-chain conversions generate revenue. This incentivizes BSV adoption within the ecosystem while providing an exit ramp to any other chain when needed.

4. Cross-Border Payments

4.1 The $150 Trillion Opportunity

Global cross-border payment flows exceeded $150 trillion in 2023. Average fee: 1.5-3%. That's $2.25-4.5 trillion extracted annually by intermediaries.

Current cross-border payment flow:

Sender Bank -> SWIFT -> Correspondent Bank ->
Correspondent Bank -> Receiving Bank -> Recipient
Time: 1-5 business days
Cost: 1.5-3% + flat fees ($25-50)

ForgePay cross-border flow:

Sender (any chain) -> ForgePay -> XRP Bridge ->
USD1 Settlement -> Recipient (any chain or fiat)
Time: 10-30 seconds
Cost: 0.1-0.5% spread

4.2 Corridor Strategy

ForgePay targets underserved corridors first:
- US to Nigeria (remittances): $4B annually, avg fee 8.5%
- US to Philippines: $12B annually, avg fee 4.5%
- US to Mexico: $63B annually, avg fee 3.7%

A ForgePay user sending $500 to Nigeria:
- Traditional: $42.50 in fees (8.5%)
- ForgePay: $2.50 in spread (0.5%)
- Savings: $40.00 per transaction

4.3 ISO 20022 Compliance

ForgePay transactions that touch XRP or HBAR carry ISO 20022 compliant metadata:
- Structured remittance information
- Debtor/creditor identification
- Purpose codes
- Regulatory reporting fields

This makes ForgePay transactions legible to institutional systems. Banks can receive ForgePay-routed payments without special integration: the ISO 20022 metadata speaks their language.

5. Integration with Forge Ecosystem

5.1 ForgeVerse

5.2 ForgeSci

5.3 ForgeDrive

5.4 ForgeSocial / ForgeTube

5.5 ForgeSite

5.6 ForgeCreate

6. Technical Implementation

6.1 Atomic Swap Protocol

ForgePay uses hash time-locked contracts (HTLCs) for trustless cross-chain swaps:

1. Alice wants to swap BSV for XRP
2. ForgePay generates a secret hash H
3. Alice locks BSV in HTLC: "Release to ForgePay if preimage of H provided within 1 hour"
4. ForgePay locks XRP in HTLC: "Release to Alice if preimage of H provided within 30 min"
5. ForgePay reveals preimage, claims BSV
6. Alice uses preimage to claim XRP
7. Both settle. Trustless. Non-custodial.

If either party fails to act, time locks expire and funds return to original owners.

6.2 Routing Engine

Input:  Source chain, destination chain, amount
Output: Optimal path, estimated spread, settlement time

Algorithm:
1. Query all available paths (direct pairs + multi-hop)
2. Calculate total spread for each path
3. Estimate settlement time
4. Score by: spread (70%) + speed (20%) + reliability (10%)
5. Execute highest-scoring path

6.3 API

ForgePay exposes a simple API for ecosystem integration:

POST /api/v1/quote
{
  "from": "BSV",
  "to": "XRP",
  "amount": 1000000,
  "unit": "satoshis"
}

Response:
{
  "quote_id": "fp_...",
  "from_amount": 1000000,
  "to_amount": "142.50",
  "to_currency": "XRP",
  "spread": "0.35%",
  "expires": "2026-03-12T15:00:00Z",
  "path": ["BSV", "XRP"]
}

POST /api/v1/execute
{
  "quote_id": "fp_...",
  "from_address": "14LQvsvmTzztAPAQRnZ5Aq6nctAnVd9fMu",
  "to_address": "rN7d9Lq..."
}

6.4 Security Model

7. Competitive Landscape

Platform Custody Spread/Fee Chains Micropayments ISO 20022
Coinbase Yes 1.49% Many No No
Binance Yes 0.1-0.6% Many No No
Uniswap No 0.3% + gas EVM only No (gas too high) No
THORChain No 0.2-1% 10 chains No No
Wise Yes 0.5-2% Fiat only No Partial
ForgePay No 0.05-0.5% BSV+XRP+HBAR+USD1 Yes (BSV native) Yes (via XRP/HBAR)

Key differentiators:
1. Micropayment native: Only ForgePay can economically process 1-sat transactions
2. ISO 20022 metadata: Institutional compatibility via XRP/HBAR routing
3. Non-custodial + low spread: Best of DEX and CEX without the downsides
4. Ecosystem integrated: Native to every Forge product

8. Regulatory Positioning

ForgePay is a protocol, not a money transmitter.

9. Roadmap

Phase 1: BSV Internal (Q2 2026)

Phase 2: Cross-Chain Bridge (Q3 2026)

Phase 3: Stablecoin Rails (Q4 2026)

Phase 4: Institutional (Q1 2027)

Phase 5: Scale (2027+)

10. The Glue

ForgePay is not the flashiest product in the Forge ecosystem. It doesn't have 3D environments or AI-generated content or spatial sovereignty.

But without ForgePay, the ecosystem doesn't breathe. ForgeVerse can't sell event tickets to someone who only holds XRP. ForgeSci can't pay a reviewer in Nigeria with USD1 settlement. ForgeDrive can't accept payment from a user who doesn't know what BSV is.

ForgePay makes the ecosystem currency-agnostic. It meets users where they are and routes value where it needs to go. It's plumbing. But it's sovereign plumbing. Non-custodial plumbing. Sub-cent plumbing.

The Demiurge (traditional finance) charges 1.5-3% to move numbers between databases. ForgePay charges 0.05-0.5% to move actual value between sovereign chains. The math is the argument.

11. IP Declaration

This whitepaper and all concepts described herein are the intellectual property of Jack Mosel and Forgechain OS. Chain-stamped on BSV before publication.

The ForgePay routing engine, spread-based revenue model, micropayment aggregation architecture, and ISO 20022 metadata injection protocol are original works.

BSV Address: 14LQvsvmTzztAPAQRnZ5Aq6nctAnVd9fMu

"The phone is ringing. Will you pick it up?"

Forgechain OS, 2026. All IP on chain before publication.