OUR OWN PRODUCTBay Software IP

CampusSwap

A marketplace where students can buy and sell with someone they have never met, and both sides are protected while they do it.

OWNER
Bay Software (Pty) Ltd
LAUNCH CAMPUS
Nelson Mandela University
BUILT BY
Bay Software, in house
STATUS
In progress

WHY IT EXISTS

Students were already trading. Nothing was protecting them

Textbooks, laptops, furniture, and everything else changes hands on every campus in the country. The trade was never the problem. The four conditions below were.

01

Money changed hands before anything was delivered

A buyer paid up front and hoped. There was no point in the transaction where the money was safe and the goods were not yet handed over.

02

Nobody could confirm who they were dealing with

Anyone could claim to be a student. Without verification there was no difference between a classmate and someone who had never set foot on campus.

03

A transaction that went wrong had nowhere to go

No process, no record, and nobody with any stake in resolving it. The evidence lived in a chat thread that either party could delete.

04

Reputation did not carry from one deal to the next

Someone who had traded fairly twenty times started every new conversation from zero, and so did someone who had not.

HOW THE MONEY MOVES

Neither side is exposed at the same time

The buyer pays before receiving anything, and the seller ships before being paid. The platform standing in the middle is what makes both of those safe to do.

Neither side exposedIf it goes wrongA person resolves itPayment madeBuyer commitsProtectedHeld, not paid outDelivery confirmedBuyer satisfiedReleasedSeller paid

What is actually in it

01

Protected payments

A buyer is never left having paid for nothing, and a seller is never left having handed something over for nothing. The platform stands between the two until both sides are satisfied.

02

Verified students only

Everyone transacting has been confirmed as a student at the institution. The marketplace stays the community it was built for rather than becoming open ground.

03

Trust that deepens with the stakes

Standing on the platform is earned rather than granted at signup, and more is required as more is at risk. Low friction where it is safe, real friction where it is not.

04

The conversation stays put

Buyer and seller talk inside the platform, so what was agreed is still there when it matters, rather than in a thread either side can delete.

05

Reviews on both sides

Both parties review each other after a completed transaction. Reputation compounds, and it follows the account rather than the conversation.

06

A platform that is run, not just published

Bay Software staffs the moderation and dispute desk. When something needs a decision, a person at Bay Software makes it and stands behind it.

THE TRUST MODEL

Four things have to hold, not one

Most marketplaces solve one of these and hope the rest sorts itself out. Identity without protected payment still loses people money. Protected payment without reputation still lets the same behaviour repeat.

Designing all four to hold together, and to keep holding as volume grows, is the engineering problem. It is the same problem shape we solve for clients.

A real student, every timeIDENTITYMoney that cannot vanishPAYMENTConduct that follows the accountREPUTATIONA person when it goes wrongMEDIATIONFOUR LAYERS, NOT ONE

WHAT IT TOOK

Nine disciplines, one team, one product

A marketplace of this kind is not one problem. It is these nine, all of which have to hold at once, and every one of them is capacity we bring to client work.

01

Payment systems

Money held, released, and reconciled without either party losing track of it.

02

Identity and verification

Confirming a person is who they say they are, at a scale nobody can review by hand.

03

Real-time systems

Messages, listings, and status that update the moment something changes.

04

Mobile and web

One product, delivered wherever a student actually opens it.

05

Cloud infrastructure

Built to carry a campus, and to carry the next one without a rebuild.

06

Security and data protection

Personal information handled to the standard the law requires, by design.

07

Automated testing

A release that touches payments does not ship on somebody's confidence.

08

Product and interface design

A first-year has to understand it without being told how it works.

09

Live operations

Moderation, disputes, and support staffed as an ongoing responsibility.

WHY WE BUILT OUR OWN

We carry the same risk we ask clients to take

CampusSwap was architected, built, and is operated by Bay Software, with no outside development team. Payments, identity, moderation, and disputes are ours to run and ours to answer for. It is the clearest statement we can make about how we work, because we are the client.

Our other product, Skills Grid