App Review Guidelines

Every app submitted to Moneris Go App Marketplace is reviewed against these 12 criteria before it can be listed. Use this as your pre-submission checklist — apps that meet all criteria on first submission move through review faster.

#	Criteria & What we Check	Why it Matters
01	App Completeness Fully functional end-to-end — no placeholders or 'coming soon' sections.	Merchants abandon apps with incomplete flows. Incomplete apps are returned for revision.
02	Onboarding & First-Time Access Clear setup flow, working demo credentials, and a simple first-run experience.	Friction at first launch is the most common reason merchants abandon an app. Make the path to value obvious and immediate.
03	Integration Readiness APIs are reliable, errors handled gracefully, device compatibility verified.	Unstable integrations cause transaction failures that directly impact merchant revenue.
04	End-to-End Workflow The full user journey runs without interruption from launch to completion.	Broken flows disrupt checkout — especially critical during active payment interactions.
05	UX & Interface Quality Interface is clean and optimised for terminal display sizes and touch input.	Poor UX slows merchants in fast-paced environments and increases errors at the counter.
06	Performance & Stability No crashes, fast load times, stable under real operating conditions.	Delays at checkout directly impact merchant throughput. Slow apps get disabled.
07	Data & Reporting Outputs are accurate, merchants can view their data, and logging is in place.	Merchants rely on transaction data for daily reconciliation. Gaps create operational problems.
08	Payment Flow Integrity Your app does not interrupt or alter the Moneris payment flow.	Any checkout disruption erodes merchant trust and harms the customer experience.
09	Error Handling & Recovery Errors show clear messages and guided steps to recover and continue.	Dead-end error states force merchants to abandon transactions or call support.
10	Security & Access Control Credentials are handled securely and authentication is implemented correctly.	Protecting merchant and cardholder data is non-negotiable for trust and compliance.
11	Device Compatibility App works correctly across all devices in scope; device-specific behaviours are handled.	Inconsistent behaviour across devices leads to support escalations and merchant churn.
12	Documentation & Support Merchant-facing getting started guide, setup instructions, and prerequisites are included in submission.	Missing docs slow onboarding and create avoidable support tickets