Production Launch Checklist

This checklist helps confirm that the partner app, merchant setup, support process, and production configuration are ready before going live. Production launch must be coordinated with Netevia.

Launch Goal

The goal of production launch is to confirm that:

• The partner app is ready for live merchants
• UAT testing is completed
• Production configuration is approved
• Support ownership is clear
• Pilot merchants are confirmed
• Launch timing is aligned with Netevia

Before Production Launch

Before production access is enabled, confirm:

• UAT testing is completed.
• Critical UAT issues are resolved.
• Open non-critical issues are documented.
• Partner app build is ready for production.
• Production release timing is confirmed with Netevia.
• Partner technical owner is assigned.
• Partner support owner is assigned.
• Netevia support contact is confirmed.
• Pilot merchant list is confirmed, if applicable.

App Readiness

Confirm the app is ready for production:

• App installs successfully.
• App launches successfully.
• User can log in.
• Merchant can access the payment flow.
• Tap to Pay option is visible.
• App uses the production environment.
• UAT configuration is not included in the production build.
• App handles errors clearly.
• App does not expose sensitive data in logs.
• App version is documented.

Merchant Readiness

Confirm merchant setup is ready:

• Merchant is approved for production.
• Merchant payment setup is complete.
• Merchant is enabled for Tap to Pay.
• Required merchant configuration is available.
• Pilot merchant access is confirmed, if applicable.
• Merchant support path is confirmed.

iOS Production Readiness

For Tap to Pay on iPhone, confirm:

• Apple Development Entitlement is approved.
• Apple Publishing Entitlement is approved.
• App Store review is completed, if required.
• Required Tap to Pay user experience is included.
• Required Apple review videos are prepared or submitted, if applicable.
• Tap to Pay button is visible at checkout.
• Terms & Conditions flow is supported.
• Merchant education is included.
• Receipt option is available.

Android Production Readiness

For Android Tap to Pay, confirm:

• Supported Android devices are confirmed.
• Required permissions are configured.
• NFC is available and enabled on test devices.
• Android SDK integration is validated.
• Android payment flow is tested.
• Device-specific issues are documented, if any.

Security Readiness

Before launch, confirm:

• Production credentials are not hardcoded.
• Production credentials are not committed to source control.
• Production credentials are not shared through unsecured channels.
• Sensitive data is not exposed in logs.
• Full card data is not stored or displayed.
• Access is limited to approved users and systems.
• UAT and production environments are separated.

Support Readiness

Before launch, confirm:

• Partner support owner is assigned.
• Netevia support contact is confirmed.
• Escalation path is understood.
• Known issues are documented.
• Launch monitoring plan is confirmed.
• First production transaction support is available, if needed.

Pilot Launch

For the first production rollout, Netevia recommends starting with a limited pilot.

Before pilot launch, confirm:

• Pilot merchants are selected.
• Pilot launch date is confirmed.
• Partner and Netevia are aligned on monitoring.
• Support contacts are available during launch.
• Pilot success criteria are defined.
• Rollback or feature flag plan is confirmed, if applicable.

General Availability

Before expanding beyond pilot merchants, confirm:

• Pilot transactions were successful.
• Critical production issues are resolved.
• Support process is working.
• Merchant feedback is reviewed.
• Partner is ready to support more merchants.
• Netevia approves broader rollout.

Summary

Production launch should happen only after UAT is completed, production configuration is approved, support ownership is clear, and launch timing is coordinated with Netevia.