Payment and money-handling systems: gateway integration, escrow and held funds, subscription and recurring billing, verification and onboarding flows, and booking with deposits.

How is a project priced?

Per project, once the scope is written. A call and a written specification come first, so the price and the delivery date are fixed before any work starts.

Do you work on an ongoing basis?

No. We deliver a defined piece of work and hand it over running. We do not take open-ended retainers or staff-augmentation work.

Who owns the finished system?

You do, outright. It runs in your own accounts and on your own infrastructure, and it is documented at handover.

Remotely, with clients anywhere. Avuno Technologies is registered in South Africa and invoices from there.

A working payment system, live. Fixed scope, fixed price.

Not a developer on your team. A defined piece of work — escrow, subscriptions, a gateway integration, a verification flow — specified up front, built, and handed over running.

Scope a project

Payment gateway integrationEscrow and held fundsSubscription billingVerification and onboardingBooking with depositsPayouts and reconciliationPayment gateway integrationEscrow and held fundsSubscription billingVerification and onboardingBooking with depositsPayouts and reconciliation

The parts that involve money.

Payment gateway integration

Cards, EFT, wallets. Taken properly: amounts settled server-side, payments confirmed against the provider rather than the browser, webhooks verified.Fixed scope

Escrow and held funds

Money held until the work is signed off, then released. Built on TradeSafe, live and moving real money today.Fixed scope

Subscription and recurring billing

Plans, renewals, failed-payment chasing, cancellation and reinstatement. The dull half nobody scopes for, which is the half that causes support tickets.Fixed scope

Verification and onboarding

Identity and company checks, document handling with real retention rules, and the flow that gets someone from signed up to allowed to trade.Fixed scope

How a project runs.

Scope it

A call, then a written specification: what gets built, what it costs, and when it lands. If the scope is wrong we find out here, not in week three.

Build it

You get something you can open and click, not a status update. Test credentials throughout, so you can put a card through it yourself before it goes near a real one.

Hand it over

Live, in your accounts, on your infrastructure, documented. You own it outright, and you deal with the person who built it.

Escrow, verification and payouts. Live.

The clearest way to judge whether we can build this is to look at one we built and run ourselves.

Built and operated by us

myQuack

A live services marketplace: funds held in escrow until a job is signed off, providers checked against identity and company records, payouts released on completion. Front to back, including the parts that hold other people’s money.

EscrowPaystackID & CIPC checksOurs, start to finish

Visit live site ↗

Bookings, escrow and payouts

Account, verification and payouts

Light and dark themes throughout

What we do not take on.

—

Open-ended retainers

We sell a finished piece of work, not hours. If what you need is another pair of hands on your team indefinitely, we are the wrong shop.

—

Rescuing an unfamiliar codebase under deadline

Inheriting someone else’s system and debugging it against a date is how projects go wrong. We will say so rather than take the work.

—

Anything without a written scope

If it cannot be specified, it cannot be priced, and neither of us knows what finished looks like.

Priced per project once the scope is written. Ask and you will get a number, not a rate card.

Tell us what you need built.

Describe the piece of work. You will get a written scope and a price within one working day, or a straight answer that it is not for us.

Scope a project