Frequently asked questions
The questions banks, acquirers and payment companies ask about methods, merchants, card data and the agreement, before a proposal.
Methods and card data
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.
Merchants, developers and terminals
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.
Deployment and the agreement
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.
Still have a question?
Send it with the methods you take and the number of merchants, and an engineer replies within one working day.