BNM Open Finance · PayNet OFP · Data Provider & Data Consumer

Open Finance,
ready to deploy
when you are.

Built for Malaysian banks. Covers both Data Provider (DP) and Data Consumer (DC) obligations — Consent Management Console, CBS integration, and audit trail in a single deployable platform.

Platform built · PayNet sandbox integration in progress · First deployments targeted 2026

Request a briefing Compliance details

DP Module

Enables your bank to expose customer data to certified TPPs via PayNet — consent sync, data provision, audit trail.

DC Module

Enables your bank to access consented customer data from other OFP participants via PayNet.

Management Console

Single staff-facing console across both DP and DC — consent visibility, suspend, revoke, analytics, and audit trail.

CBS Adapter

Pre-built IBM MQ / Apache Camel adapter. Field mapping via UI — no bank IT development needed.

Analytics & Reporting

API volumes, consent activity, configurable alerts, and board-ready exports in one dashboard.

The BNM Mandate

Malaysian banks must operate as both Data Provider and Data Consumer.

BNM designates every licensed Malaysian bank as both a Data Provider and a Data Consumer. The deadline is firm. An in-house build takes months of engineering. MYeBills covers both roles in one platform.

Risk of non-compliance

Regulatory

Enforcement action by BNM, public censure for failure to implement a conformant Data Provider capability.

Operational

TPP data requests rejected — customers at your bank cannot participate in Open Finance-enabled services while peer institutions are live.

Reputational

Perception of being behind in digital banking readiness as peer institutions go live.

Customer

Your customers unable to use Open Finance-enabled services at your bank while competitors' customers can.

Platform Capabilities

One platform. Both DP and DC obligations covered.

Configured for your environment. Defined integration points. No framework to build on top of.

Data Provider (DP)

Consent Management Console

Search all customer consents by identity or consent reference
Suspend, reactivate, and revoke consents with mandatory reason codes
Emergency bulk suspension for a compromised TPP
Full immutable audit trail — every action logged with user, timestamp, IP address

Data Consumer (DC)

Consented Data Access from OFP

Consented data retrieval from other OFP Data Providers
Full consent validation before every data request
End-to-end request and response logging
Token lifecycle management and revocation
PayNet OFP DC specification aligned

CBS Integration

Core Banking System Adapter

Pre-built IBM MQ and Apache Camel adapter
Field mapping UI — no redeployment for configuration changes
47 automated integration tests verify connectivity before go-live
Supports Oracle 19c+, SQL Server 2019+, MySQL 8.0+, PostgreSQL

Management

Analytics, Alerts & SLA Monitoring

API call volumes, consent counts by status, top TPPs by activity
Configurable alert thresholds — email or Slack notifications
CSV and PDF export for board reporting and BNM submissions

MYeBills vs In-House Build

Built and ready. No in-house development required.

Every bank needs to comply. The question is how fast and at what cost.

	MYeBills Platform	In-House Build
Time to go-live	Significantly faster than an in-house build	Months of design, development, and testing before go-live
PayNet API compliance	Built to PayNet API Specification v1.2.1	Must be designed, implemented, and tested from scratch
PayNet spec updates	Managed by MYeBills — delivered as platform updates	Bank IT team must track and implement each update
In-house expertise	Minimal — bank provides CBS credentials and server	Requires dedicated Open Finance API engineers
Consent Management Console	Included — full consent visibility, audit trail, analytics	Requires separate development
Audit logging	Included — immutable audit logs, full traceability	Requires separate development
Ongoing maintenance	Covered under MYeBills support agreement	Full burden on bank IT
Cost predictability	Fixed platform fee	Variable engineering cost, ongoing overhead

How It Works

Two deployment paths. One platform.

Two deployment paths. Both scoped at the outset. Your team handles defined tasks — MYeBills handles the rest.

Data Provider (DP) Deployment

Scoping & onboarding

CBS environment assessment. Your team sets up the IBM MQ queue.

CBS adapter setup

MYeBills configures the CBS adapter via field mapping UI. Your team provides credentials and queue access.

PayNet sandbox & UAT

End-to-end PayNet sandbox testing. 47 automated tests before go-live sign-off.

Production go-live

24/7 support, 99.9% SLA. PayNet spec updates absorbed by MYeBills.

Data Consumer (DC) Deployment

Scoping & onboarding

Digital channel architecture review. We identify which apps connect to the DC module.

Digital channel integration

Your digital channel team connects apps to the DC module API. MYeBills provides the spec and support.

PayNet sandbox & UAT

Full consent flow testing — grant through retrieval — against PayNet sandbox.

Production go-live

24/7 support. New OFP data types and spec updates absorbed by MYeBills.

Regulatory Alignment

Built for Malaysia's Open Finance framework — both roles, one platform.

Built specifically for Malaysia's Open Finance framework — every line of code written for PayNet OFP.

Request a briefing

BNM Open Finance Policy

Covers DP and DC obligations under BNM's Open Finance policy.

PayNet API Specification v1.2.1

Built to PayNet API Spec v1.2.1. Spec updates managed and delivered by MYeBills.

ISO 27001 Certified

MYeBills' information security management certified to ISO/IEC 27001:2022 — Certificate No. 763497, valid to August 2028.

On-Premise or Private Cloud

On-premise or private cloud. No data leaves your environment.

Security & Deployment

On-premise. Your infrastructure. Your control.

MYeBills Open Finance deploys within your institution's own server environment. No customer consent data is processed or stored outside your controlled infrastructure.

ISO/IEC 27001:2022 Certified

Independently audited information security management — Certificate No. 763497, valid to August 2028.

On-Premise Deployment

Installs within your institution's own server infrastructure — consistent with BNM data residency and outsourcing guidelines. No customer data leaves your environment.

99.9% Uptime SLA

24/7 support with a named contact and documented escalation path — not a generic helpdesk.

Open Finance,ready to deploywhen you are.