Payment acceptance for banks and acquirers
A gateway, checkout and payment links under the institution's own brand, taking cards, DuitNow QR, FPX and the major Malaysian e-wallets. Bought once, owned outright and run in the institution's own environment.
- Your brand
- Checkout, links and portals carry the institution's name.
- Every method
- Cards, DuitNow QR, FPX and the major e-wallets.
- Tokens only
- Card data stays with the acquirer's processor.
- Owned outright
- No share of volume and no fee per transaction.
From the application to the settlement run
Six features on one acceptance platform, for the institution, its merchants and their developers.
- GatewayMerchants, routing, settlement, fees and disputes on one console.
- CheckoutHosted or embedded, under the institution's brand.
- Payment linksA link or a printed QR, settled like everything else.
- Merchant portal and appTakings, settlement, refunds and disputes, on a laptop or a phone.
- Developer portalDocs, sandbox, keys and SDKs, so merchants integrate themselves.
- Onboarding and riskApplication to live, with officers on the exceptions.
A day of payments on asasii acceptance
From the morning's applications to the afternoon's settlement run.
- 08:30
The team signs in
Holds, dispute deadlines and applications waiting on the institution, oldest first.
- 09:40
A cafe goes live
With its documents read and screening clear, a cafe with no website is activated for links and printed QR.
- 11:15
A sale on the checkout
A customer pays a homeware store by DuitNow QR on the institution's hosted checkout.
- 12:30
A catering order by link
The cafe sends a link by message. The customer pays on a phone and the cafe is told at once.
- 13:05
Walk-ins at the counter
Customers scan the cafe's printed QR, and the counter phone sounds a confirmation for each payment.
- 13:50
A webhook stops landing
The store's developer finds the failing endpoint in the event log. Queued events retry and can be replayed.
- 14:20
A dispute, answered
The store answers a card dispute with the signed delivery note, and the team reviews the case against its deadline.
- 15:00
The settlement run
Approved by two people. Each merchant's run shows the fee and the SST on it, line by line.
Who it's for
Each person works on their own screen, on the same records.
A licence, not a share of every payment
The institution buys the software and keeps everything it produces. idataraya is paid to customise, install and maintain it.
| Topic | A hosted payment platform | asasii acceptance |
|---|---|---|
| Who owns the software | The platform's vendor | The institution, outright |
| Where it runs | The vendor's cloud | The institution's own environment |
| Routing and risk rules | Requested from the vendor | Set by the institution's own team |
| The brand customers see | The vendor's name on the checkout | The institution's name on checkout, links and portals |
| What it costs | A share of every payment | A licence and a yearly agreement, with no share of volume |
Security and Malaysian compliance
The questions procurement, audit and compliance ask, answered in the platform.
Security and data overview- DuitNow QR and FPX
- First-class methods beside cards and e-wallets, with the settlement files read back.
- MyInvois e-invoicing
- E-invoices on request, consolidated B2C on the institution's schedule.
- SST on fees
- Shown on every merchant statement as its own line.
- Bank Negara reporting
- The return's fields carried on every transaction and merchant.
- PDPA 2010
- Retention set per data class, in the institution's own environment.
- Card data
- Stays with the acquirer's processor; the platform holds tokens and references.
Installed and maintained by idataraya
asasii acceptance runs in the institution's own environment, its data centre or its cloud account. idataraya customises it, installs it and keeps it current, and the institution owns the software, the data and the audit log.
- Response times by severity, measured against the agreement
- Monitoring from inside the institution's environment
- Software updates and the customisations made for you
- Releases tested in the institution's sandbox first
Questions institutions ask
About methods, merchants, card data and the agreement.
Which payment methods does it take?
Cards, DuitNow QR, FPX and the major Malaysian e-wallets, on the hosted checkout, the embedded checkout and payment links. The institution sets the default order the methods appear in, and its routing rules decide where each payment goes and what happens when a rail is slow.
Does card data touch the platform?
No. Card data stays with the acquirer's processor, and the platform holds tokens and references only. On the embedded checkout the card fields are the processor's, rendered inside the SDK, so the merchant's app never handles a card number.
How does a merchant go live?
Onboarding is digital from application to live acceptance. The platform's document AI reads the documents and screening runs before an officer looks, so officers review the exceptions. A merchant applying for payment links and printed QR only can be activated without a site visit, with a daily limit by tier.
Can larger merchants integrate without our team?
Yes. The developer portal carries the documentation, a sandbox, scoped keys, signed webhooks, request and event logs and SDKs under the institution's brand. A developer goes from a test key to a first payment in three calls, and the go-live checklist is the institution's gate.
Does it cover terminals?
Yes. asasii smart terminals, countertop devices and unattended readers in toll lanes, vending machines, car park exits and kiosks accept DuitNow QR, cards and the major Malaysian e-wallets. The terminal and soundbox estate is provisioned, configured, updated and monitored from one console.
Where does it run?
In the institution's own environment, its data centre or its cloud account. idataraya customises it, installs it and keeps it current, and the institution holds the keys, the data and the audit log.
Can our other systems talk to it?
Yes. The gateway sits over the institution's existing payment, account and customer APIs, and every product carries a documented API. Every report is also an API endpoint, and fee revenue and SST go to the ledger by export.
What does the yearly agreement cover?
Maintenance and updates, the customisations made for you, monitoring from inside your environment, and response and restoration targets by severity. Hosting stays with you. It is a fee, never a share of volume or a charge per transaction.