TSWG API Payment Documentation

View API pricing · API platform

Current implementation

PASS166E creates payment-readiness infrastructure and pending payment review intents. It does not process live charges. Live gateways require a separate sandbox/live payment pass.

Payment lifecycle

Plan selection
→ Country/currency/payment method review
→ Gateway candidate selection
→ Pending payment intent
→ Gateway-specific checkout/webhook pass
→ Verified payment
→ API client activation
→ Usage limits + proof requirements

Country/local payment matrix

CountryCurrencyMethodsGateway candidatesNotes
European Union EUR Card, SEPA where available Stripe, PayPal SEPA/card support needs compliance and tax handling.
Ghana GHS Mobile Money, Card, Bank Transfer Paystack, Flutterwave, manual bank review MTN MoMo, Vodafone Cash, AirtelTigo Money should be supported through configured local gateway.
Global USD Card, PayPal, Bank Transfer, Local methods where available Stripe, PayPal, Flutterwave, Paystack Fallback routing for unsupported countries should use invoice/manual review.
Kenya KES M-Pesa, Card, Bank Transfer Flutterwave, local M-Pesa-capable gateway M-Pesa readiness should be tested separately before activation.
Nigeria NGN Card, Bank Transfer, USSD, Mobile Money where available Paystack, Flutterwave Local bank transfer and card rails are important for API buyers.
South Africa ZAR Card, EFT, Bank Transfer Paystack, Flutterwave, Stripe where supported EFT and card support matter for SaaS/API billing.
United Kingdom GBP Card, Bank Transfer Stripe, PayPal Card and bank payments with VAT/tax review.
United States USD Card, ACH where available Stripe, PayPal Stripe subscriptions and card payments are primary.

Non-negotiable gateway test rules