SWSS Pay is the ecosystem's payment gateway: card and bank acceptance on one side, native settlement on SWSS Chain on the other, with a Finality Certificate for every transaction and no off-chain reconciliation queue.
Conventional payment infrastructure does not settle. It authorises, captures, batches and reconciles, and the merchant learns what actually happened days later when a statement arrives — because the record of a payment lives in several systems that must be made to agree. SWSS Pay removes that gap by settling every transaction natively on SWSS Chain: sub-second finality, a Finality Certificate per transaction, and one record both parties can read rather than two that need reconciling.
It accepts both sides of the market. Cards, bank transfers and stablecoin pairs come in as fiat and crypto acceptance; the value is auto-routed to SWSS Chain settlement with an audit trail on SWSS Explorer. That is the structural point rather than a convenience feature: every fiat payment routed through this gateway becomes a demand stream for SWSS Coin, which is how a payments product contributes to the economics described in Tokenomics instead of merely sitting beside them.
Pay is also where several other products settle their money. Merchant checkout, trade finance instruments, draw payouts, metered compute billing and AI agent revenue all clear through the same rails and the same certificate engine, each under its own deed type. A payment gateway that only moved money would be a utility; one that issues the settlement record for five different classes of obligation is infrastructure the rest of the ecosystem depends on.
It operates under a licensed framework rather than an unregulated rail, and identity is not its own to assert: verification is completed once through the Identity Verification Layer and unlocks Pay alongside every other regulated product, so a member proves who they are once rather than per platform. Pay flows live inside the SWSS App, where wallet, bridge, staking and payments share one login, one balance and one history.
What SWSS Pay Provides
| Capability | What it means in practice |
|---|---|
| Settlement-First Rails | Every transaction settles natively on SWSS Chain with a Finality Certificate — sub-second finality, native SWSS Coin gas, EVM Cancun compatible, and no off-chain reconciliation queue |
| Crypto ↔ Fiat On/Off Ramps | Card and bank acceptance and stablecoin pairs, auto-routed into SWSS Chain settlement with the audit trail public on the explorer |
| Single Verification | One identity verification through SWSS IVL unlocks Pay alongside RWAX, Draw and every other regulated product — no repeat KYC per platform |
| SWSS App Integration | Payments sit beside wallet, bridge and staking in one interface: one login, one balance, one history |
| Merchant & Marketplace Tools | Merchants accept SWSS Coin or stablecoins and either settle to fiat or hold on chain, with split-payment logic for marketplaces |
| Revenue Recirculation | Pay revenues feed Layer 2 of the Settlement Combustion Model through the Ecosystem Revenue Recirculation Protocol |
Architecture
| Layer | Component | Function |
|---|---|---|
| 1 | Payment API Layer | REST endpoints, hosted checkout, webhook events, OAuth and signed requests |
| 2 | SWSS Chain Settlement | Direct submission to SWSS Chain mainnet — there is no intermediary clearing layer between the payment and the chain |
| 3 | Finality Certificate Engine | Each settled transaction emits a DTS 05.6 cryptographic Finality Certificate |
| 4 | KYC & Risk Layer | Identity through SWSS IVL, sanctions screening, transaction monitoring and risk scoring |
Layer 2 is the one that distinguishes this from a gateway with a blockchain feature. Most crypto payment products hold a clearing layer between the payment and the chain, which reintroduces exactly the reconciliation gap the chain was supposed to close. Submitting directly to mainnet means the settlement a merchant relies on and the record a regulator can audit are the same event.
What Settles Through Pay
| Flow | Settlement |
|---|---|
| Merchant Checkout | Hosted checkout for merchants accepting SWSS Coin or stablecoins, with optional auto-conversion at settlement |
| Trade Finance | The DTS 05.5 Trade Finance Deed, co-issued with SWSS REALM to settle invoice and trade finance flows on chain |
| Draw Payouts | Prizes from SWSS Draw settle through Pay rails against a provably fair draw, certificate-backed on payout |
| Compute Billing | Metered GPU compute on SWSS InfraX bills through Pay, settled per delivery as a DTS 05.2 Compute Deed |
| AI Agent Payments | OwlX agents settle per-call revenue through Pay against their AI Agent Identity record; the DTS 05.3 AI Agent Deed is the separate, tradable claim on that revenue |
Regulatory Foundation
| Licence / Framework | Entity | Scope |
|---|---|---|
| FINTRAC Canada (MSB Licence) | SWSS FintechCanadaMSB Licence | AML compliance, KYC, payment processing, SWSS Pay operations |
The licences above are those that bear on payment operations. The full regulatory position for the ecosystem — every entity, licence and jurisdiction, with the scope of each — is set out in the Legal & Regulatory Framework, which is the authoritative statement; this table is the payments-scoped extract of it.
Payment infrastructure touching conventional banking cannot operate on any other basis, and the licences above are the reason Pay can accept fiat at all. Compliance obligations are met through the identity and monitoring layer rather than by restricting who may transact after the fact: sanctions screening and transaction monitoring run against a verified identity, so a payment is checked before it settles rather than reversed afterwards — which on an irreversible settlement layer is the only order that works.
Milestones
| Period | Description | Status |
|---|---|---|
| Q4 2027 | SWSS Pay launch | In Development |
What is SWSS Pay?