Payment channels
Accept payments through the channels enabled for your institution, including FPX, debit cards and credit cards.
Payments that connect to your operations.
Tulus Payment Gateway is owned and managed by Tulus Digital Sdn Bhd, a Payment Exchange under PayNet. It helps institutions, businesses and digital platforms accept payments and connect each transaction to their own records.
Accept FPX, debit card and credit card payments, and bring confirmations, receipts and reconciliation records into your collection workflow. Use it in your existing website, app or system, on its own or as the payment foundation for the other Tulus solutions. The payment channels and settlement arrangements for your institution are agreed during onboarding.
Zakat institutions, waqf administrators, charitable organisations, businesses and digital platforms that need payments connected to their own records and ways of working.
Each institution or merchant has its own agreed scope, payment channels and operating arrangements.
Accept payments through the channels enabled for your institution, including FPX, debit cards and credit cards.
Connect payment acceptance to your website, app or institutional system, with payment references so each confirmed transaction matches the right collection or business record.
Connected systems receive transaction results and signed payment notifications, and can check a transaction's status when a payment needs follow-up.
Confirmed payments are linked to digital receipts, sent through the receipt channels in your service arrangement, and each receipt stays linked to its transaction reference.
Authorised teams see transaction records through the merchant portal and the reporting agreed for your institution, so they can follow payment status and look into exceptions.
Payment and settlement records support reconciliation with your institution's accounts. Settlement timing, deductions and accounts follow your agreement.
Your institution creates a payment request with its reference and amount.
The payer chooses an enabled payment method and authorises the payment.
The gateway receives the transaction result.
Your connected system receives the confirmation and checks the transaction reference.
A receipt is issued for the confirmed payment.
Your teams use the transaction and settlement records for reconciliation and follow-up.
A pending result stays pending until it's confirmed. A payer returning to your website isn't, on its own, proof that the payment went through.
Use the gateway on its own, through your website, app or system, or as the payment foundation for other Tulus solutions. Payment records can be linked to collections and field visits where that's part of your implementation.
Tell us which channels you need, where your payments start and which systems need the records. We'll agree the channels, integration, receipts and settlement arrangements with you.
Talk to Tulus