Skip to content

Payment Integration

Payment gateway integration for South African and international businesses: checkout, subscriptions, deposits, refunds and reconciliation, on Paystack and more.

  • A fixed price for the build
  • Provider fees stay visible
  • Test payments first; real money on launch day
A clear invoice: card or EFT

[01] When it fits

Sounds familiar?

  • 01

    You chase EFTs and match bank statements by hand.

  • 02

    Customers cannot pay online, so deals stall.

  • 03

    Your system does not always know who has paid.

What we do about it

A working checkout button is the easy part. The hard part is making sure your system always knows who paid, what failed, what was refunded and what is still pending.

[02] What we build

What we build.

The button is the easy part. The rest is making sure your system always knows who paid, what failed and what was refunded.
  1. Shubble: Confirm and pay
    01

    Once-off, deposit and subscription payments

    Take money the way you sell: in full, as a deposit, monthly or against an invoice.

    Screen from Shubble
  2. webhooks · live 0 failed
    payment.succeeded200signature ok
    order.created201#318 saved
    booking.updated200dates moved
    refund.processed200R 450 back
    02

    Secure checkout, verified webhooks

    Card details stay with the provider. Your system only trusts messages it can verify.

  3. Provider events

    payment.succeeded evt_8f2cRecorded
    payment.succeeded evt_8f2cDuplicate · ignored
    Invoice #1042 paid once · R 4 850
    03

    Each payment recorded once

    Even when the provider sends the same event twice, the order is paid once.

  4. Payments

    Today
    #1042 · CardR 4 850Paid
    #1043 · EFTR 2 450Pending
    #1044 · CardR 990Failed · retry sent
    #0211 · RefundR 450Refunded
    04

    Refunds and failed payments

    Cancellations, refunds and retries, each with a clear status and a message to the customer.

  5. Custom Point of Sale: Cash-up history
    05

    Reconciliation and finance views

    What came in, what is pending and what was refunded, matched to each order or booking.

    Screen from Custom Point of Sale

[03] How it works

How it works.

Test and live payments stay separate. Real money only switches on as a planned launch step.
  1. Start

    Step 1: A call

    Who the seller is, the countries, currencies and payment methods, and what the customer sees at each step.

  2. Before any work

    Step 2: Brief and fixed price

    We compare the current provider fees for your business, then a proposal with a fixed build price and every provider cost listed.

  3. Day 0

    Step 3: Agreement and deposit

    You sign and pay the deposit. We help you open the provider account in your business's name.

  4. About a week later

    Step 4: First test payment

    Checkout working end to end in test mode: pay, fail, refund, receipt.

  5. While we build

    Step 5: Every status

    Pending, paid, failed, refunded and disputed, each tested and shown clearly to your team.

  6. On your date

    Step 6: Live on your date

    AI agents test every payment path before launch. You choose the day real payments switch on.

Afterwards

Then, your choice.

  • A

    Handover

    Your team runs it. The provider account is already yours.

  • B

    Monthly plan

    Monitoring, provider admin and fixes. Transaction fees always stay with the provider.

  • C

    Product partnership

    For a bigger product: billing, plans and finance views keep growing with it.

[04] Seen in the work

Real projects. Real screens.

Payments that set off everything after them: trips, orders, bookings and access.

All our work

Tools we work with

The tools behind it.

Every tool here is in a product we have built and shipped. We pick them once the problem is clear, and set them up in accounts you own.

See the full toolbench
  • PaystackCard, EFT and subscription payments in rand, in apps and on the web.
  • PayFastCheckouts for WooCommerce shops and online bookings.
  • StripeOnline card payments and subscriptions, when a client sells abroad or already runs on Stripe.
  • PolarSoftware subscriptions billed in dollars to customers abroad.
  • WooCommerceOnline shops with stock, delivery options and South African checkouts.
  • PostmarkReceipts, sign-in codes and reports that land in the inbox, not spam.
  • ConvexReal-time backends for our own products and client platforms: data, jobs and sign-in in one place.
  • SentryError alerts, so we hear about a bug before your customers do.

[05] The proof

Why work with us.

A payment usually sets off everything else: access to an account, an order, a booking, an invoice, a message to the right person. We have built that chain for family transport, a services marketplace and our own AI products, so we design it from checkout to the last notification.

Payment providers in work we have shippedPaystack, PayFast, Stripe and Polar
4
Products of our own, live or in testingMoteef, Headroom, Seshat, Roomwise
4
From your deposit to a first preview linkUsual timing across our 2026 client builds
~1 week

Our own counts come from a dated snapshot of our repositories and release feeds (11 October 2026).

Fair questions.

Next step

Start with a call.

Tell us what you need. You get a short brief, then a written proposal with a fixed price before any work starts.

Start a conversation

It depends on your countries, currencies, payment methods, payout timing, subscription needs and fees. We have built on Paystack for several products, and we check the current options for your business before recommending one.

Usually checkout, secure server-side calls, verified webhooks, clear payment statuses, retries, refunds, subscriptions, test payments and alerts. The proposal lists exactly what is in scope.

We charge a fixed fee for the build. The payment provider charges its own setup, transaction, currency and dispute fees, and those stay visible.

Often, yes. We review how it is built first, so payments land safely and the records match.