Based on PayNet’s guidance, participants must have an additional Internet connection instead of relying solely on TM MPLS. Banks may choose MPLS or Secure Internet as primary, with at least two options. Applicable to API V3 or only TCP/IP?

Is it correct that participants need to sign off a request using the same businessMessageId in Sign-On, or is it unnecessary to use the same request?

How many TPS for each API can PayNet support for participant?

Are your endpoints deployed in AWS (Kuala Lumpur)? If so, are you using AWS Global Accelerator?

Is the API v3 connectivity stable?

Is the API connection through MPLS? Are there any FQDN or IP whitelisting requirements?

Does PayNet have an API timeout? If so, how long is the timeout?

If the participant (requestor) does not receive a response from PayNet within the timeout interval, should they treat this transaction as U002 Accepted?

What is the configured timeout duration for outgoing transactions on the PayNet API Server?

Will legacy connectivity channels (e.g., TCP/IP, API Direct) continue to be supported?

Is the Modernised API backward compatible with previous versions?

What are the domain and IP configuration requirements for different environments?

Can Real-time Retail Payments Platform (RPP) set a percentage traffic split for Issuer and Acquirer?

What is the Disaster Recovery (DR) Requirement for Modernised API (API v3)