Skip to main content

Payment Providers Overview

SolydFlow acts as an intelligent orchestration and consensus layer above your payment providers.

Instead of writing bespoke gateway integrations, handling divergent webhook schemas, and maintaining custom retry queues for every app, you connect your merchant accounts to SolydFlow using a secure Bring Your Own Keys (BYOK) model.


Supported Provider Compatibility Matrix​

ProviderPrimary MarketsSupported Payment MethodsStatus
PaystackNigeria, Ghana, South Africa, KenyaLocal Cards, USSD, Direct Bank Transfer, Apple PayProduction Ready
FlutterwavePan-Africa (30+ countries)Cards, Mobile Money (MTN/Airtel/Telecel), BarterProduction Ready
StripeGlobal (US, EU, UK, CA, AU)International Cards, Apple Pay, Google Pay, SEPAProduction Ready
M-Pesa / DarajaKenya, TanzaniaM-Pesa STK Push, Paybill, Buy GoodsProduction Ready
MonnifyNigeriaReserved Virtual Accounts, Dynamic AccountsProduction Ready
Apple In-App PurchasesGlobal (iOS App Store)StoreKit 2 Subscriptions & In-App PurchasesTesting / Beta
Google Play BillingGlobal (Google Play Store)Google Play Billing SubscriptionsTesting / Beta

The Bring Your Own Keys (BYOK) Model​

SolydFlow does not process funds through intermediary accounts:

┌───────────────────────────────────────┬────────────────────────────────────────────────────────┐
│ Ownership Principle │ How It Works in SolydFlow │
├───────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ 1. Direct Merchant Ownership │ Funds settle directly from Paystack/Stripe into your bank.│
├───────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ 2. Zero Platform Lock-in │ Your customer records and gateway tokens belong to you.│
├───────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ 3. Hardware-Grade Encryption │ Gateway keys are encrypted at rest via AES-256-GCM. │
└───────────────────────────────────────┴────────────────────────────────────────────────────────┘

Inbound Gateway Webhook Architecture​

When connecting providers, SolydFlow provisions a dedicated, cryptographically isolated inbound webhook endpoint for your project:

https://api.solydflow.com/api/v1/webhook/{provider}/{your_solydflow_api_key}

Why Inbound Webhooks Are Verified Server-to-Server​

Standard integrations blindly trust incoming webhook JSON bodies. SolydFlow’s Consensus Engine prevents spoofing:

  1. Intercepts the provider webhook.
  2. Temporarily holds entitlement activation.
  3. Queries the provider's authoritative REST verification API directly using your encrypted secret key.
  4. Verifies amount, currency, and reference match before writing a SETTLED_CONSENSUS record to your Immutable Ledger.

Provider Integration Guides​

Select a provider to view step-by-step API Vault setup and webhook configuration:

🇳🇬 🇬🇭 🇿🇦 Paystack

Pan-African cards, USSD, bank transfers, and Apple Pay.

Setup Paystack →

🌍 Flutterwave

Pan-African card payments and regional mobile money wallets.

Setup Flutterwave →

🇰🇪 M-Pesa (Daraja)

Native Kenyan mobile money STK push prompts.

Setup M-Pesa →

🌐 Stripe

Global card payments, 3D-Secure, and multi-currency billing.

Setup Stripe →

🏦 Monnify

Nigerian virtual bank accounts and direct debit rails.

Setup Monnify →

📱 Mobile App Stores

Apple In-App Purchases and Google Play Billing.

Setup Store Billing →