How Float Uses PayFast to Process Installment Collections

PayFast is South Africa's largest independent payment gateway. If you have bought anything online locally, you have almost certainly encountered it. For Float, PayFast is more than a checkout widget. It is the collection rails that move instalment payments from users' accounts into the Float settlement system.

Why a Payment Gateway Matters for Instalment Products

Collecting recurring instalment payments requires infrastructure that most fintechs do not build from scratch. It is complex. You need bank connectivity, debit order processing, payment reconciliation, failed payment handling, and dispute management. Building each of these layers takes years and significant regulatory investment.

PayFast provides this infrastructure as a service. For Float, integrating PayFast as a collection partner meant access to established bank connectivity, South African rand settlement, and compliance frameworks that PayFast has already built. Practically, this reduces Float's time-to-market for reliable collections significantly.

How PayFast Processes Float Collections

When a Float user activates an instalment plan, the backend creates a recurring payment schedule. On each collection date, Float triggers a payment request through the PayFast API. PayFast handles the actual debit order instruction to BankServ, monitors collection status, and returns a result to Float within the banking day.

The PayFast API supports both once-off and subscription-style payment models. For Float's use case, each instalment is technically a standalone scheduled payment rather than a subscription, because the amounts may vary (if a user makes a partial early repayment, for example) and the collection dates are confirmed per-plan rather than on a generic monthly cycle.

Fact: PayFast processes over R3 billion in transaction value annually for South African merchants. The infrastructure is battle-tested. Not experimental.

Reconciliation and Failure Handling

Not every debit order succeeds on first attempt. Insufficient funds, bank account changes, and authentication failures all cause collection failures. How a product handles these failures is as important as how it handles successes.

PayFast provides webhook notifications for payment events: successful collection, failed collection, dispute raised. Float receives these events and takes action: for a failed collection, a user notification is triggered, and a grace window is opened. If the collection fails twice, Float contacts the user to understand the situation before any adverse action is taken.

In our beta, the collection failure rate was under 4% across all attempted debits. Of those failures, 85% were resolved within 7 days through user-initiated retries. That is better than industry average for debit order products in South Africa, where failure rates of 8 to 12% are common.

Security and Compliance

PayFast is PCI-DSS compliant. It holds a Payment Service Provider registration with the South African Reserve Bank. For Float, using a compliant gateway rather than building direct bank integrations shifts a significant portion of the security and compliance burden to a specialist provider.

Security first. All communication between Float's backend and PayFast uses TLS 1.3. Payment data is never stored on Float's servers. PayFast tokenises payment methods, meaning Float holds a reference token, not raw account details. This architecture is the right approach. Trust us on this: the security risk surface on fintech products that handle raw bank account details directly is orders of magnitude higher than tokenised integrations.

The Role of Ozow

PayFast is not the only gateway we have evaluated. Ozow, South Africa's instant EFT specialist, is integrated for specific use cases where real-time account-to-account payment is preferable to debit order. Ozow allows users to pay directly from their internet banking without entering card details, and provides near-instant settlement confirmation.

For Float's instalment collection model, debit orders via PayFast are the primary channel because they are scheduled rather than user-initiated. Ozow is relevant where a user wants to make an ad-hoc early repayment. The two gateways serve complementary functions in the Float payment architecture. Different jobs. Same goal.

What This Means for Users

The payment infrastructure is mostly invisible when it works well. Users see a debit leave their account on the confirmed date for the confirmed amount. That is all. The PayFast integration is the mechanism that makes that reliability possible.

Where users might notice it: PayFast's merchant name appears on bank statements. Float instalments may appear as a PayFast reference rather than a Float-branded description, depending on the bank's statement formatting. We are working on improving statement descriptors to make Float-sourced collections clearly identifiable.

Read more about how DebiCheck authentication works alongside PayFast, or apply for early access to Float.