Built in Malaysia for
Malaysian merchant portfolios
Most merchant monitoring platforms treat Southeast Asia as an afterthought. Kenal AURA is built in Malaysia for Malaysian acquirers and PSPs: SSM Live integration, Bahasa Malaysia classification, BRAM-aligned rules, and per-country data residency honoured from day one.
Summary
Kenal AURA is the merchant lifecycle risk operations platform for Malaysian acquirers, PSPs, and fintechs. Company and director data comes directly from SSM Live e-Info. Content classification runs in English, Bahasa Malaysia, and Chinese. Malaysian tenants are placed on the AWS Malaysia region so PDPA residency stays satisfied.
SSM Live is the source of truth
Company status, directors, and shareholders come directly from Suruhanjaya Syarikat Malaysia's e-Info API, the authoritative registry. Merchant-uploaded PDFs of company profiles are optional supplementary evidence, not the primary source. When SSM says a company is struck off, the case surfaces that immediately.
Bahasa Malaysia is a first-class classification language
BRAM rule coverage runs in English, Bahasa Malaysia, and Chinese. A merchant switching to a Malay-language gambling site does not slip through because the classifier only speaks English. Multilingual classification is not a post-hoc add-on. It is how the rule set is maintained.
Malaysia PDPA residency honoured per tenant
Production Kenal AURA runs on a multi-cloud regional footprint: AWS Malaysia (ap-southeast-5) and GCP Singapore (asia-southeast1). Malaysian tenants are placed on the AWS Malaysia region at provisioning time, so Malaysia PDPA data residency is honoured by infrastructure, not by policy promise. Tenant isolation is row-scoped and encryption at rest uses AES-256.
BRAM and MMP coverage out of the box
Mastercard BRAM rules are the default rule set for Malaysian acquirers. MMP reports are generated in a format aligned to Mastercard's MMP reporting requirements, from the same case data analysts work in. Both MMP SLA clocks are tracked on every case: 5 business days for detection-to-escalation, 15 calendar days for acquirer remediation.
Modules that power this
SSM Live Integration
Company, director, and shareholder data from SSM e-Info for every Malaysian merchant.
Learn moreDirector eKYC
Selfie, MyKad OCR, and face similarity for every declared director.
Learn moreWeb Change Detection
Multilingual classification in English, Bahasa Malaysia, and Chinese.
Learn moreMCC Drift Detection
Alert when a merchant's content drifts outside its approved BRAM category family.
Learn moreCompliance Reporting and Evidence
MMP report generation and 7-year immutable evidence retention.
Learn moreSecurity Posture
Multi-cloud regional footprint, Malaysia PDPA alignment, and tenant isolation controls.
Learn moreFrequently asked questions
- Is Malaysia PDPA residency actually honoured, or is this a policy promise?
- It is an infrastructure property. Kenal AURA runs on a multi-cloud regional footprint: AWS Malaysia (ap-southeast-5) and GCP Singapore (asia-southeast1). Malaysian tenants are placed on the Malaysia region at provisioning time, and tenant-scoped data for that tenant stays in that region. The placement is enforced by configuration, not by running a cross-region job afterwards.
- Does SSM Live integration need anything from our side?
- SSM Live e-Info is accessed through Kenal AURA's integration, so acquirers do not need to maintain their own SSM API credentials. The platform handles the lookup, the parsing, and the attachment of registry data to the merchant case. Response fields preserve the verbatim e-Info labels for audit.
- How is Bahasa Malaysia content handled in practice?
- The BRAM rule set runs in English, Bahasa Malaysia, and Chinese. Keyword rules, classification prompts, and category definitions are all maintained in the three languages. A Malay-language gambling page gets the same classification treatment as an English one. The classifier does not fall back to translating it first.
- Do you support acquirers operating across Malaysia and other ASEAN markets?
- Yes. Acquirers with tenants in Malaysia and elsewhere in ASEAN can run multiple tenants: one placed on the AWS Malaysia region, others placed on the GCP Singapore region as required. Each tenant is isolated at the data layer, and each is placed on the regional cloud that meets its country's data residency requirement.