NFT / Marketplace·Ethereum · Polygon · Arbitrum · Base · EVM
Forte
On-chain compliance and economic infrastructure for games and Web3 apps. Forte combines the open-source Forte Rules Engine (a Solidity policy framework that constrains mints/transfers/burns by balance, value, time, or KYC tier) with FortePay (fiat-and-crypto payments + KYC/AML) to give studios a compliant economy layer. As of 2025 FortePay is the payments backbone for Sequence and other gaming stacks.
- 01compliant on-chain game economies
- 02rules-based token mint/transfer policies
- 03fiat + crypto checkout for in-game items and NFTs
- 04studio-grade KYC/AML and licensing coverage (US, EU)
- 05stablecoin and ERC-20 launches with regulatory guardrails
- forge install thrackle-io/forte-rules-engine
| Variable | Scope | Description |
|---|---|---|
| FORTEPAY_API_KEY | Server | Server-side FortePay merchant API key. |
| FORTEPAY_MERCHANT_ID | Server | Forte merchant / organization ID. |
| NEXT_PUBLIC_FORTEPAY_PUBLISHABLE_KEY | Client | Publishable key for the FortePay drop-in checkout component. |
For policy enforcement, install the Forte Rules Engine via Foundry (`forge install thrackle-io/forte-rules-engine`) and inherit `RuleProcessor` in your ERC-20/721 so every transfer/mint/burn passes through registered rules (max-balance, transaction-volume, oracle allowlist, KYC tier). Manage rules via the Forte admin contract; rule changes are governed and on-chain. For payments, embed FortePay's hosted checkout (`<FortePayCheckout publishableKey amount currency />`) and create payment intents server-side with the FortePay REST API to take card or local-currency payments and settle in crypto/stables. KYC is handled inline by FortePay tiers — gate token transfers in the Rules Engine on Forte's identity attestation oracle.
- ⚑The Forte Rules Engine is open-source but the canonical deployments + admin contracts are managed by Forte/Thrackle — opting out later means migrating users off the rule-bound token contract.
- ⚑FortePay covers compliance (US 50-state + NY BitLicense, EU licenses) only when you onboard as a Forte merchant; using the SDK alone without a merchant agreement is not licensed-by-default.
- ⚑Rule checks add gas to every token transfer (typically a few thousand to tens of thousands of gas depending on rule count) — model this when picking a chain, especially for high-frequency game transactions.
- ⚑FortePay settlement to crypto goes through Forte's custodial bridge — design treasury flows to tolerate T+1 settlement windows rather than instant on-chain receipt.
- ⚑Peer-to-peer transfers between players are still subject to the Rules Engine policies you deploy; misconfigured rules (e.g. global transfer caps) can softlock secondary trading.
- ⚑There are two unrelated 'Forte' brands: Forte.io (web3 game economies) and CSG Forte (legacy fiat payments at forte.net) — make sure SDK references and API hosts target the web3 product.