Payments & Information Portals
Payment collection that reconciles itself, on DuitNow QR in Malaysia, PayNow QR in Singapore and GIRO or other recurring collection, plus multilingual portals and content sites your own team can update.
The problem, in your words.
Every month somebody matches forty bank transfers to invoices by hand, and the ones with no reference take the whole afternoon.
People send payment screenshots over WhatsApp, and we cannot tell which of them actually went through.
Half the people we serve do not read English first, and our website only speaks it. Changing a single line means emailing a developer and waiting a week.
Payments and portals in the Philippines
Our Philippines team in Iloilo builds payment collection and multilingual portals for local government units and community organisations, editable by your own staff rather than by us. Quoted in pesos.
Two jobs live on this page because they usually arrive together: collecting money, and telling people things. On the money side we build payment pages, invoices and fee or donation collection on the rails people already use: DuitNow QR in Malaysia, PayNow QR in Singapore, and GIRO or other recurring collection for payments that come in every month.
The part that saves the most time is reconciliation. Each QR code or invoice carries its own reference, so when a payment lands the system knows what it was for and marks it paid, and your finance team gets a report instead of a bank statement to decode. For a uniformed youth organisation's gift-matching campaign, it meant a public donation total that was never a manual number.
The information side is portals and content sites: service directories, resource libraries, programme and event pages, and sites in the languages your community reads, with a content editor your communications person can use without calling us. We set up the structure and the translation workflow; your team owns the words.
Underneath the payments are our own open-source DuitNow QR and PayNow QR libraries, which generate and parse codes to the published specifications and are tested against real bank output. We wrote them because charging per transaction for a published specification struck us as cheeky. You can read the code before it touches your money, and keep using it with or without us.
Everything is quoted in ringgit or dollars and fixed for the scope, and the quote shows what it costs to run: hosting, plus whatever your bank or payment provider charges. Payments go straight into your organisation's own bank account; what we build simply tells you what each one was for. The work is done by our Malaysia and Singapore engineers, who run these rails in production.
From first chat to handover.
Follow the money
We trace how payments arrive today, from QR scans to transfers and screenshots, and where the matching goes wrong.
Pick the rails
DuitNow QR, PayNow QR, GIRO or a card gateway, chosen for your payers and your bank, with the fees written down.
Build and test with real banks
Codes and reconciliation are tested against real bank output before anyone pays a real bill.
Hand the words to your team
Your editors get the portal and a training session; finance gets the reconciliation report and a runbook.
Things people ask us.
Do payments go through you?
No. Payments go straight into your organisation's own bank account. What we build generates the codes and invoices, then reads the payment records so each one is matched to what it was for.
How long does it take to add QR payments?
The scope says how long it takes. Adding DuitNow QR or PayNow QR to an existing site or invoice run is short, and most of it is testing with your bank; a new portal with payments and multilingual content takes longer.
What does it cost to run?
The build is quoted in ringgit or dollars and fixed for the scope. Running costs are hosting plus whatever your bank or payment provider charges, and both are listed in the quote. The QR libraries themselves are free.
Can our staff update the site in other languages?
Yes. Content lives in an editor your team uses directly, with each language side by side, so a change does not need a developer. We set up the structure; your team owns the words.
Can we take it elsewhere later?
Yes. The code sits in your repository, the hosting is in your name and the QR libraries are open source, so another developer can carry on from where we stopped.