Operational clarity from beta onward
See how KPay-MZ communicates activation, limits, support, and beta validations with direct and credible language.
Current status
Security in every click
No inflated promises
Each feature is presented with its real beta status.
Phased opening
Public flows only open when the operation is ready.
Human review when needed
Sensitive cases can be followed with more care.
What is already active
The beta can already be explored, with registration available and clear communication about what is still under validation.
Web account
Registration is available so users can enter the platform and follow the beta phase.
Beta virtual card
Creation may be available at no cost in this phase for eligible users.
Public funding
Local top-ups remain under validation before the official opening.
How the beta is handled with care
Trust here comes from clear messaging, real limits, and phased activation.
Guided entry into beta
The account can already be created and explored while full activation remains phased.
Active operational monitoring
The beta operation is observed with progressive controls and human review when necessary.
Public integrations only open when ready
Flows under validation remain clearly identified to avoid the wrong expectations.
Benefits and limits are communicated precisely
The product prefers to be clear about operational maturity instead of projecting unrealistic readiness.
Support with real product context
Support aims to answer with useful information and escalate only what needs more attention.
Limits are acknowledged without exaggeration
Not every rail or public operation is fully open yet, and that is communicated clearly.
Need additional help?
For operational questions or specific cases, talk to the team through public chat or create your account to follow the beta from the dashboard.