Distribution
WhatsApp First
Designed around the channels South Africans already use for social and business conversations.
Paylo One
WhatsApp-first payment requests for everyday South Africa
South African Payment Requests
Paylo One turns awkward payment moments into clear request flows for people and small businesses, with WhatsApp, payment links, QR, invoices, reminders, and visible payment status all working together.
Distribution
Designed around the channels South Africans already use for social and business conversations.
Use Cases
Built for dinner bills, deposits, recurring reminders, and everyday payment requests.
Product Shape
Simple enough for friends and families, structured enough for small-business cash flow.
Why It Works
The most useful lesson from Tikkie is not the visual style. It is the product discipline: one clear action, familiar channels, visible trust, and a fast explanation of what the user should do next.
The clearest lesson from Tikkie is that people do not fall in love with payment rails. They respond to a request flow that is easy to send, easy to understand, and easy to act on.
A request feels safer when the amount, purpose, sender, status, and payment path are obvious from the first screen, not hidden in follow-up messages.
Payment links, QR codes, invoices, and WhatsApp delivery matter because they match real South African behaviour without forcing customers into a heavy new habit.
Product Family
Each product belongs to a clear payment-request job: sending, splitting, collecting, operating, or receiving repeatedly.
Payment Links
Send a secure payment request in seconds.
A request-first payment link product for invoices, deposits, and one-to-one collections.
Businesses that want a more professional payment request than a bank transfer message, and individuals who need a clean shareable link.
Collections
Keep collections simple and cash flow moving.
A focused collections workflow built on top of the same request-first payment foundation.
Small businesses and teams that need to follow up on repeat or outstanding payments without overwhelming staff or customers.
Bill Splitting
Split the bill without the awkward maths.
A social payment request product for splitting bills, shared costs, and group contributions.
People who pay up front for a group and want a cleaner way to collect everyone else's share.
Merchant Operations
See every request, payout, and payment in one place.
The operating console for businesses using the Paylo One request products at scale.
Merchants and teams that need better oversight of requests, staff activity, proofs, exports, and support cases.
Personal Identity
Your personal payment profile, ready when you are.
A personal request profile for repeat payments, tips, support, and informal receiving.
Anyone who gets paid repeatedly by different people and wants a more recognizable payment presence.
For Consumers
Splitting a table, collecting for a trip, or asking for money back should feel social and natural, not like admin.
Paylo Split
Turn one shared restaurant bill into clear requests, track who has paid, and remove the awkward chasing afterwards.
Paylo Split
Create a shared contribution request for travel, birthdays, stokvel-style group moments, or school activities.
Paylo Me
Give repeat contacts a simple, recognizable way to pay you without re-explaining your bank details every time.
For Small Businesses
Many South African businesses already sell through messages, mobile phones, and informal follow-ups. The product should meet that reality instead of demanding a full e-commerce stack.
Paylo Link
Create a clean request, attach invoice context, and let the customer pay from the same conversation where the work was discussed.
Paylo Link
Use branded requests and reminders for bookings, catering, home services, events, and custom orders.
Paylo Collect
Keep track of who still owes, who has paid, and which reminder should go out next without falling back to spreadsheets and manual messages.
How It Works
Start with the amount, purpose, recipient context, and expiry so the request is immediately understandable.
Send through WhatsApp, copy a payment link, place it on an invoice, or show a QR code in person.
The payer should move through a simple, trusted payment experience instead of decoding bank details or downloading the wrong app.
See what has been paid, what is still open, and when a reminder or receipt should be sent.
Security And Trust
Trust comes from visible context, familiar payment behaviour, and stronger operations behind the scenes, not from vague security language alone.
Every request should show who is asking, what it is for, how much is due, and when it expires.
The direction is shaped around WhatsApp behaviour, low-value payments, informal merchants, and familiar bank-led payment expectations.
Businesses need payment status, references, receipts, and exports. Consumers need confidence that the request is real and easy to settle.
The front-end brand stays simple and friendly while the back-end can still rely on stronger payments, settlement, and compliance capabilities.
Pricing Direction
Exact pricing still needs validation, but the product direction should already communicate a clean fee philosophy instead of burying it.
Bill splitting and small social requests only work when the payer experience feels lightweight and affordable.
The Tikkie benchmark shows the value of simple fee logic. Paylo One should keep business pricing transparent and easy to explain.
Low-value payments are core to the strategy, so pricing and rail choices must be validated against South African transaction costs before launch.
FAQs
Paylo One is a South African request-first payment product direction for people and small businesses. It is built around asking, paying, splitting, and collecting money more clearly.
The strongest starting audiences are consumers handling shared expenses and small businesses that need invoices, deposits, or payment links paid faster.
The intended experience is low friction for the payer. The payment flow should feel familiar and should not depend on forcing every recipient into an app-install journey.
Trust comes from visible context, familiar payment behaviour, clear sender identity, status visibility, and stronger operational controls behind the scenes.
No. That is one of the market gaps this direction is trying to address. The product should work for formal businesses, side hustles, and everyday informal money moments.
Next step
The landing page now leads with a more controlled hero, clearer use cases, stronger trust framing, and a product system that feels more intentional and credible.