Payment gateways¶
Applies to: Owner and Administrator (to know what is available); developers. Last reviewed: 2026-11-18.
This page states plainly which online payment gateways DriveFlow really supports today, and which ones exist only as names or unfinished code. In short: PayFast is the only gateway that works.
Summary¶
PayFast is the only working gateway
PayFast is the only payment gateway that works end to end in DriveFlow. It is used for two separate things:
- Schools paying DriveFlow for their plan, add-ons and SMS bundles.
- Students paying a school's invoices online, into the school's own PayFast account.
Paystack, Flutterwave and Stripe appear in the code, but no screen uses them and they have no payment notifications. A school cannot select them anywhere.
Gateway by gateway¶
The list of gateway types in the code contains five values.
| Gateway | In the list | Checkout code | Payment confirmation (callback) | Used by any screen | Verdict |
|---|---|---|---|---|---|
| PayFast | Yes (1) | Yes, two implementations: one for DriveFlow's subscriptions, one for each school's own account | Yes: two notification (ITN) endpoints with merchant, signature, server and amount checks | Yes: Subscription, Billing, the mobile app's Subscription screen, the student portal | Working |
| Paystack | Yes (2) | A gateway class exists and is registered | None. No webhook endpoint. A manual "verify" call exists. | No | Not usable |
| Flutterwave | Yes (3) | A gateway class exists and is registered | None. No webhook endpoint. A manual "verify" call exists. | No | Not usable |
| Stripe | Yes (4) | A gateway class exists and is registered (Stripe Checkout Sessions) | None. No webhook endpoint. A manual "verify" call exists. | No | Not usable |
| Manual | Yes (5) | Not applicable | Not applicable | Yes, SuperAdmin only | Not a gateway: a label for payments a DriveFlow SuperAdmin records by hand, for example an EFT received outside DriveFlow |
What exists for Paystack, Flutterwave and Stripe¶
- Code for each of the three providers that can create a checkout, look up a payment's status and request a refund through the provider's API.
- Generic staff functions in the API to create a payment request for a student through a named gateway, ask the gateway whether it was paid (and, if so, record the payment), and check its status. The technical details are covered in the internal technical documentation.
- A fee-settings entry: DriveFlow's SuperAdmin can store fee percentages per gateway, including these three, for commission calculations. That is bookkeeping only and does not make a gateway usable. See the SuperAdmin guide.
What is missing for them¶
- No user interface. Nothing in the web application or the mobile app uses these generic gateway functions. There is no button to send a student a Paystack, Flutterwave or Stripe payment link.
- No per-school settings. A school can only enter PayFast details. These three gateways have no per-school account set-up, so they could not pay money into a school's own account.
- No callbacks. None of the three has a webhook endpoint, so a payment would only be recorded if somebody ran the "verify" step afterwards.
- Not available for subscriptions. The subscription checkout is wired to PayFast only.
- PayFast is not reachable through this generic route. PayFast is not registered in the generic gateway list; asking the generic route for PayFast fails with "Payment gateway 'PayFast' is not supported." PayFast has its own purpose-built paths instead.
Note
Treat Paystack, Flutterwave and Stripe as groundwork for the future, not as features.
Which PayFast account receives the money¶
| Payment | Goes to | Configured by |
|---|---|---|
| Plan, add-on, SMS bundle | DriveFlow's own PayFast merchant account | DriveFlow, in the server configuration |
| A student paying a school invoice from the portal | The school's own PayFast merchant account | The school, under Settings > Payments |
DriveFlow never handles students' money: it only builds the PayFast payment link with the school's merchant details and records the result when PayFast confirms it.
Both uses are described in detail in PayFast.
Currency¶
All online payments are in South African rand (ZAR). PayFast is a South African gateway.
Limitations and notes¶
Refunds for PayFast payments fail
Refunding a student's PayFast payment from DriveFlow is likely to fail. The refund action for a payment that came from an online gateway looks the gateway up in the generic gateway list, where PayFast is not registered. A payment recorded from a student's PayFast transaction therefore cannot be refunded through that route; the refund would have to be done in PayFast itself and the correction made in DriveFlow by other means.
- Refunding a student's PayFast payment from DriveFlow is likely to fail (see above). This belongs to the payments documentation (Refunds and voids); it is noted here because it follows from the gateway set-up. It was read in code, not tried.
- How the PayFast settings are organised on the server is covered in the internal technical documentation.
- No card details ever pass through or are stored in DriveFlow. Payment always happens on the gateway's own page.
Related articles¶
- PayFast: both PayFast uses in detail.
- Subscription management: paying DriveFlow for a plan.
- Online payments: students paying school invoices.
- External services: every external service DriveFlow uses.
- Gateway fee settings: fee percentages for commission calculations.