Cardless Subscriptions Need a Different Renewal Machine

Key takeaway

Canva's launch of recurring Capitec Pay in South Africa removes the credit-card requirement from subscription access. It does not turn an account-to-account mandate into a card on file. The growth opportunity is real, but only for operators prepared to rebuild renewal, recovery and cancellation around a bank-authorized pull.

What's changing

On September 2, Canva became the first international merchant to offer recurring subscriptions through Capitec Pay, with EBANX connecting the South African bank's account-to-account method to Canva's cross-border checkout. A customer approves the recurring payment once inside the Capitec app; participating merchants can then collect later subscription payments automatically.

That is a small product launch with a large distribution consequence. EBANX says only 8% to 10% of South African adults have a credit card, leaving about 44 million people outside the default card-on-file subscription model. The figures are attributed to the South African Reserve Bank and World Bank; the exclusion estimate comes from EBANX's analysis. Capitec itself reports 26 million active clients and about 15 million active app users, or roughly one in three South African adults.

The installed base is not theoretical. Capitec said e-commerce transactions, including Capitec Pay, rose 32% to 643 million in the year ended February 2026. Pay-wallet transactions more than doubled to 335 million. Canva is attaching recurring billing to a payment behavior that customers already use, instead of asking them to acquire a card before they can buy software.

Sources: EBANX announcement, September 2, 2026; Capitec annual-results summary, April 22, 2026.

Why it matters

Global subscription localization is often treated as a checkout problem: add a local method, translate the price and watch conversion rise. Recurrence changes the job. The merchant is no longer optimizing one authorization. It is operating a mandate across months, balance cycles, plan changes, cancellations, refunds and customer disputes.

Card programs have spent decades building lifecycle machinery around expiring credentials, network tokens, account updaters, retry rules and issuer response codes. A bank-account mandate has different failure modes. The account does not have an expiry date, but a payment can still fail because funds are unavailable, the account is restricted, the mandate has been withdrawn or the bank's risk controls intervene. Reusing a card retry calendar without observing local salary and cash-flow patterns can turn access into involuntary churn.

The customer-control surface also moves. Authorization happens in the banking app, while the service relationship lives with the merchant. If a subscriber changes plans, pauses service or cancels, the merchant has to keep the product entitlement, its own billing ledger, EBANX's payment state and the bank mandate synchronized. A cancellation that stops access but leaves a live collection authority is a trust failure. A revoked mandate that leaves premium access running is a revenue-leakage problem.

This is why the launch is more consequential than simply adding another alternative payment method. It makes the local bank app part of the subscription product. Approval copy, merchant naming, collection timing and revocation status now influence conversion and retention.

There is also a measurement trap. The first dashboard will probably show new paid accounts that could not previously subscribe by credit card. That is useful, but it is not sufficient. A2A cohorts should be evaluated on first-payment success, second- and third-cycle survival, recovery after insufficient funds, refund completion time, mandate revocation, support contacts and net revenue retention. Comparing only checkout conversion with cards will reward acquisition while hiding weak renewal economics.

What operators should do

Build the mandate ledger before scaling acquisition. Each subscription should have a traceable link among the customer consent, bank authorization, current plan, next collection date, amount-change history and cancellation status. Support teams need to see that state without reconstructing it across providers.

Create an A2A-specific recovery policy. Test collection timing against local income cycles, separate soft failures from revoked authority, and cap repeated attempts. A failed pull is not permission to keep probing the account. The recovery path should offer a clear reauthorization or alternate method rather than an opaque retry loop.

Design cancellation and refunds as end-to-end flows. The product entitlement, merchant billing record and mandate state should reconcile quickly, with plain customer messaging about what has stopped and whether any already-initiated debit is still settling.

Finally, price and package for the segment actually being opened. Cardless access expands the addressable market, but it does not prove that imported plan tiers or annual commitments fit local willingness to pay. Track A2A performance by plan, price point and acquisition channel. The method may work best with lower entry tiers, monthly billing or locally timed offers rather than as a drop-in replacement for the existing card mix.

Bottom line

Canva and Capitec Pay show that recurring A2A can remove a structural gate from subscription commerce. The winning metric will not be how many payment logos appear at checkout. It will be whether a bank-authorized mandate can produce understandable consent, dependable renewals and clean exits. Cardless distribution becomes durable only when the renewal machine is rebuilt for the rail.