SWSS Pay routes every transaction through SWSS Chain mainnet, Sub Second finality, Finality Certificate per settlement, Sumsub KYC reused from SWSS App, no off chain reconciliation queue.
SWSS Pay is a Q4 2026 product built on a chain that is already running. SWSS Chain went mainnet after a 365+ day testnet, so Pay launches onto live infrastructure, SCP v3.2.1 four pillar consensus, 1 second blocks, not a future commitment.
Every Pay settlement issues a DTS 05.6 Finality Certificate, a protocol level cryptographic instrument, not a smart contract side effect. Pay is the third revenue stream feeding the Settlement Combustion Model, alongside RwaX and Draw.
// SWSS Pay, settle on SWSS Chain
import { SwssPay } from "@swss/pay";
const pay = new SwssPay({
chainId: 122605, // SWSS Chain mainnet
rpc: "https://swssrpc.swss.io",
});
const tx = await pay.settle({
amount: "100.00",
asset: "SWSS", // or stablecoin
deed: "DTS-05.1", // Home Deed
memo: "Order #12345"
});
// → tx.finalityCertificate (DTS 05.6)
// → SWSS Mainnet Explorer /tx/...Payments rebuilt around blockchain finality, not bolted onto it
Every SWSS Pay transaction settles natively on SWSS Chain with a Finality Certificate, no off chain reconciliation queue.
Bridge fiat acceptance into SWSS Chain settlement, adding a structural fiat demand stream for SWSS Coin.
One Sumsub verification in SWSS App unlocks SWSS Pay alongside RwaX, Draw and every regulated product.
Pay flows live inside SWSS App, wallet, bridge, staking and Pay share one login, one balance, one history.
Merchants accept SWSS Coin or stablecoins and settle to fiat or hold on chain, with marketplace split payment logic.
Pay revenues feed Layer 2 of the Settlement Combustion Model, Ecosystem Revenue Recirculation Protocol.
Four layers, API, settlement, certificate engine, identity & risk
REST endpoints, hosted checkout, webhook events, OAuth + signed requests
Direct submission to SWSS Chain Mainnet, no intermediary clearing layer
Each settled tx emits a DTS 05.6 cryptographic Finality Certificate
Sumsub identity, sanctions screening, transaction monitoring, risk scoring
Protocol level cryptographic settlement proof, not a smart contract side effect
Five tier validator staking (4 phases) underwrites every settlement
Reusable identity layer shared across SWSS App, RwaX, Draw and Pay
The SWSS Mainnet Explorer exposes every tx, deed and certificate in real time
SCP v3.2.1 four pillar consensus delivers sub second user perceived finality
4 live validators + 20+ in testing, expanding with NodeX rollout
Mainnet bring up only after 365+ days of continuous testnet operation
Standard tooling, Foundry, Hardhat, Viem, Ethers all work day one
SWSS Pay co issues four of the five Deed Transaction Standards, every settlement carries the right legal envelope, recorded on SWSS Chain
SWSS Pay does not bolt blockchain on, it IS a blockchain product. Every payment writes to SWSS Chain mainnet.
Accept SWSS Coin natively plus major stablecoin pairs, with optional fiat off ramp at settlement.
Pay co issues four of the five Deed Transaction Standards, every settlement carries the right legal envelope.
Pay revenues feed all three SCM layers, TSL retirement, ERRP recirculation and Stake Gravity Protocol.
EVM standard tooling, Foundry, Hardhat, Viem, Ethers all work day one against SWSS Chain Testnet
EVM standard SDKs plus REST/GraphQL endpoints, works with any web3 toolchain
Real time settlement, KYC and Finality Certificate events delivered to your stack
Full feature sandbox on SWSS Chain Testnet, same code paths as mainnet
0x1DEED, production SWSS Chain
0x1DEEE, same code paths as mainnet
SCP v3.2.1 four pillar consensus
Sumsub identity, sanctions screening, transaction monitoring, all reused from SWSS App, all visible on Explorer
Sumsub KYC
Identity Verification
AML Monitoring
Continuous Screening
GDPR Aligned
EU Data Standards
SCP v3.2.1
Four Pillar Consensus
Finality Certificate
Per Settlement
Malaysia HQ
Global Tech Centre
Pay rails connect RwaX, InfraX, OwlX, Draw and trade finance under one settlement layer
Pay rails settle Home Deeds and Commercial Property Deeds for SWSS RwaX, title transfer + payment in one tx.
Hosted checkout for merchants accepting SWSS Coin or stablecoins, with optional auto conversion at settlement.
DTS 05.5 Trade Finance Deed, Pay co issues with REALM to settle invoice and trade finance flows on chain.
Winning BEP-721 tickets settle prizes through SWSS Pay rails, provably fair RNG, certificate backed payout.
Metered GPU compute on SWSS InfraX bills through Pay, DTS 05.2 Compute Deed settled per delivery.
OwlX agents register under DTS 05.3 AI Agent Deed and settle per call revenue through SWSS Pay.
Every Pay settlement is recorded on SWSS Chain mainnet, not a database entry
SCP v3.2.1 confirms blocks in one second, end to end
Each transaction issues a protocol level cryptographic settlement proof
Every tx visible on the SWSS Mainnet Explorer with full receipt and certificate
Accept SWSS Coin, stablecoins, cards and bank transfers in one flow
Lives inside SWSS App, no separate wallet, bridge or staking screen
Standard EVM tooling, EIP-1153 supported
Pay revenues retire SWSS Coin via TSL, no inflation, ever
From research, to ERRP activation, to launch inside SWSS App
Pay rails architecture drafted alongside SCM Layer 2 (ERRP) economic model.
SWSS Chain mainnet, SWSS App beta, Sumsub KYC layer and Explorer all live, Pay's prerequisites in production.
Settlement Combustion Model Layer 2 (Ecosystem Revenue Recirculation Protocol) activates, Pay revenue stream wires in.
SWSS Pay launches inside SWSS App with crypto, stablecoin and fiat bridge acceptance, settling Home, Compute, AI Agent and Trade Finance Deeds.
Trade Finance and Commercial Property Deeds scale; cross chain Pay flows tracked under SCP cross chain settlement.
One Sumsub KYC, one wallet, one settlement layer, Pay joins RwaX, Draw, Bridge and Staking under a single login.
Single login across the entire ecosystem
Sub Second finality, SCP v3.2.1
5B fixed supply, TSL retirement per tx
Every Pay tx visible on the SWSS Mainnet Explorer