AmahoroPay is a Celo Mainnet payment SaaS stack (SDK → SaaS) built around four source-verified contracts: the AMHR token (0x06CAe70F…B3FAa3bfa, ERC-20 with EIP-3009-style signed transfers, payMerchant, batch deposits/claims, access control), the AmahoroProcessorGuard (0x031363E7…9159DAf1E, spend limits, relayer authorization, secureBatchPayout gating, constructor bound to AMHR with initial limit 50000), and the AmahoroGateway proxy (0xD70c1f5e…D8C06135d, EIP-1967 UUPS proxy → impl 0x95548046…420E6a61a, initialized with guard/fee-recipient/treasury/owner and 100/50/50 bps).
The SaaS (PHP vanilla, index.php router, PSR-4 controllers, Web3Service JSON-RPC client) plus amahoropay-sdk.js lets vendors integrate checkout, escrow, batch payouts, cross-chain swaps and gasless payments into merchant apps.
Let any vendor plug AMHR gateway features into their app so customers pay vendors directly: checkout, escrow, batch payouts, cross-chain swaps (settler-fronted settleCheckout), and gasless payments, while the relayer fronts on-chain liquidity and the SDK/SaaS handles signing, verification, limits and webhooks. Anchored to verified Celo Mainnet contracts: AMHR 0x06CAe70F…B3FAa3bfa, GUARD 0x031363E7…9159DAf1e, Gateway proxy 0xD70c1f5e…D8C06135d (celoscan.io).
Merchants cannot safely accept token payments directly: raw contract calls are fragmented across AMHR + GUARD + Gateway, require private keys for server-signed relay (checkout create, batch payout), lack on-chain verification before crediting users (phantom-record risk), have no spend-limit/relayer gating for payouts, and expose no merchant dashboard. Customers also have no gasless path (signed EIP-3009 authorizations) and no escrow/cancel protections.
(1) Server-signed EIP-155 relay (pure-PHP Secp256k1 + RLP, byte-verified vs ethers) for gateway writes: checkout create, batch payout through GUARD's secureBatchPayout (relayer pre-authorized + payer batchPaymentAllowed + approval of the Guard).
(2) Public wallet-signed pages for customer-controlled actions: payCheckout, depositEscrow, releaseEscrow, cancelCheckout, transferWithAuthorization/receiveWithAuthorization (EIP-3009, validAfter/validBefore/nonce, 65-byte packed sig).
(3) On-chain event verification (CheckoutPaid, EscrowFunded/Released/Refunded, CheckoutCancelled, BatchPayoutExecuted) before flipping any DB row — no phantom records; idempotent confirm pages with on-chain flag fallback.
(4) Per-tier plan limits (checkouts/escrows/API calls), SIWE-proven wallet registration (EIP-4361), SIWE-gated API key on-chain registration, CSRF on all mutating routes, and webhook relayer (HMAC) for CheckoutPaid/EscrowReleased/BatchPayoutRouted/FeeCollected.
AmahoroPay is a Celo-based payment gateway SaaS (PHP backend + JS/TS SDK) that monetizes six streams: 1. Gas relay surcharge: margin on CELO gas paid by the relayer for server-signed EIP-3009/EIP-2612 transactions (operator-set, no default %). 2. Merchant transaction commission: per payMerchant payment, locked on-chain via fees().merchantFeeBps; default 1% (100 bps), client cap 10% (1,000 bps). 3. SaaS subscriptions: plans payable in USDC/AMHR: Free 0; Pro Monthly 29/mo; Pro Yearly 290/yr; Enterprise. 4. Batch / payroll fee: quoteBatchFee on batchPayout volume, degressive by recipient count (operator-set; ProcessorGuard enforces limits). 5. Cross-chain swap spread: operator-controlled rate multiplier (default 1:1, max 10x) + swap_spread_bps (default 0, max 10 bps/1,000 bps cap) on source→target USD conversion. 6. API overage: calls above a key's daily_calls quota (default 1,000/day, max 100,000) are rejected (429); higher quotas sold via the dashboard. 7. Treasury custody / on-ramp: custody + conversion fees for non-default assets (USDC/KOKO) held in the relayer treasury via EIP-3009 (operator-set). Customer segments: Web2/Web3 developers (NPM SDK), merchants/e-commerce (checkout/escrow), enterprises/payroll (batch payouts), gasless end consumers (EIP-3009), and relayer/node operators. Channels: NPM/GitHub, developer portal, Celo ecosystem, SaaS dashboard.
Global, Africa