Payment Methods
Set up and manage payment methods for your organization
Payment Methods
Configure how your organization pays for AfricaOS.
Supported Methods
Credit/Debit Cards
Accepted: Visa, Mastercard, American Express, Discover
Features:
- Tokenized (we never see full number)
- Auto-update for expired cards (Visa/MC)
- 3D Secure supported
- Multiple cards allowed
- Set default
Setup:
- Settings → Billing → Payment Methods
- Add Card → Enter details
- Verify (small auth, voided immediately)
- Set as default
Security:
- PCI DSS Level 1 (via Stripe)
- No card data on our servers
- Token vaulted with provider
Bank Transfers (EFT)
For: ZAR payments within South Africa
Details Provided:
- Bank: Standard Bank
- Account: AfricaOS (Pty) Ltd
- Branch: 051001
- Account #: [Unique per org]
- Reference: INV-XXXXX (critical)
Processing: 1-2 business days
Tips:
- Always use invoice number as reference
- Send proof of payment to billing@africaos.dev
- Allow 2 days before due date
Wire Transfers (International)
For: USD, EUR, GBP, other currencies
Details:
- Provided per invoice (varies by currency)
- SWIFT/BIC, IBAN, intermediary bank
- Reference: INV-XXXXX
Processing: 2-5 business days
Fees:
- Sender pays all fees (OUR instruction)
- We receive net amount
- Shortfalls billed separately
Mobile Money
Supported:
- M-Pesa (Kenya, Tanzania, Ghana, etc.)
- MTN MoMo (Multiple African countries)
- Airtel Money (Multiple African countries)
- Orange Money (Select countries)
Setup:
- Settings → Billing → Add Mobile Money
- Select provider
- Enter phone number
- Authorize via provider app/USSD
- Verify
Processing: Instant to few minutes
Limits: Per provider daily/monthly limits apply
Paystack / Flutterwave / Stripe
For: Card, bank, mobile money via platform
Setup:
- Connect account in Settings → Integrations
- Payment methods managed in provider dashboard
- AfricaOS uses connected account for charges
Benefits:
- Local payment methods
- Better success rates in Africa
- Unified dashboard
Managing Payment Methods
Default Method
- One default for auto-pay
- Change anytime
- Used for: subscriptions, overages, manual payments
Multiple Methods
- Add backup methods
- Auto-pay falls back on failure
- Manual selection per payment
Removing Methods
- Keep at least one
- Can't remove if only method
- Remove before adding replacement
Updating Cards
- Auto-update for supported networks
- Manual update: Remove old, add new
- Expiry warnings sent 30 days prior
Security
Card Security
- PCI DSS compliant (SAQ A)
- Tokenization via Stripe/Paystack
- No CVV storage
- 3D Secure 2.0
Bank Account Security
- Read-only verification (micro-deposits)
- No debit authority
- Reference-only for matching
Mobile Money Security
- PIN/biometric per transaction
- Provider handles auth
- No credentials stored
Access Control
- Only Owner/Admin manage methods
- Audit log of all changes
- MFA required for changes
Troubleshooting
Card Declined
| Reason | Action |
|---|---|
| Insufficient funds | Add funds, retry |
| Expired | Update card |
| Blocked by bank | Contact bank |
| 3D Secure failed | Use app to approve |
| Limit exceeded | Request increase |
Bank Transfer Not Matched
- Verify reference (INV-XXXXX)
- Check amount matches exactly
- Send proof to billing@africaos.dev
- Allow 24h for allocation
Mobile Money Failed
- Check balance
- Check daily limit
- Verify PIN
- Try alternative provider
- Contact provider support
Auto-Pay Failed
- Notification sent immediately
- 3 retries over 14 days
- Update payment method
- Manual pay to avoid service impact
Best Practices
- Always have backup - Card + Bank + Mobile Money
- Enable auto-pay - Avoid service interruption
- Monitor expiry - Update cards before expiry
- Use invoice reference - Critical for bank transfers
- Set billing alerts - 80% usage, failed payments
- Review monthly - Check invoices, usage, methods