Multi-Tenant Zero-Knowledge Payment Isolation
Cryptographic isolation between SaaS platform subscription revenue and client company acquiring, AES-256-GCM token vault, and custom payment campaigns.
On this page(4)
Zero-Knowledge Multi-Tenant Architecture
A critical invariant in enterprise B2B SaaS is financial isolation. Platform subscription earnings (Sferafy Core Tech SaaS package fees) are processed through dedicated platform accounts.
In contrast, client company invoicing acquiring flows directly into the client organization's own merchant account (Monobank, Stripe, LiqPay, or Bank Wire). Sferafy operates in zero-knowledge mode: platform administrators cannot access or tamper with client financial keys.
AES-256-GCM Secret Encryption with Tenant AAD
All merchant credentials, API secrets, and webhook tokens are encrypted at rest using tenant-bound authenticated cryptographic keys. Sferafy operates in zero-knowledge mode: platform administrators cannot access or tamper with client financial keys.
Each client company's cryptographic keys are bound to its unique workspace identifier, preventing cross-tenant credential reuse or unauthorized extraction.
Custom Payment Campaigns & Routing
Each tenant administrator can configure campaign-specific parameters:
• Statement Descriptor: Custom 32-character merchant label appearing on customer card and banking statements.
• Settlement Currency: Choice of UAH, EUR, USD, PLN, or GBP based on the merchant account.
• Settlement Type: Immediate debit vs two-stage pre-authorization hold.
• Sandbox Mode: Simulated checkout testing without executing live financial charges.
Cryptographic Settlement Webhooks
Inbound payment notifications from Monobank or Stripe are routed to tenant-specific webhook endpoints.
Payloads undergo HMAC-SHA256 signature verification before any invoice status is transitioned to 'PAID', preventing replay attacks and webhook spoofing.