Certify open loop payments

To certify your open loop payments that are powered by Google Pay, complete all of the following phases:

Phase 1: Pre-launch Phase 2: Post-launch
Transit operator responsibility
  • Implement transit operator EMV enhancements.
  • Ensure that the firmware and software for all terminals are up to date.
  • Provide access for Google to test them in a lab or in real stations.
  • Keep terminals up to date with the latest specification.
Google responsibility
  • Send testers with the top 20 Android-powered devices in the region to perform tests.
  • Test stability and tap success rates.
  • Test card verification method (CVM) checks.
  • Continue tests at a reduced frequency to identify issues.
  • Monitor tap trends over time.
Joint ownership
  • Address all launch-blocking bugs.
  • Implement marketing and promotions to increase awareness.

Certification criteria

The following table describes the certification criteria:

Test case Number of devices Pass criteria
Device test: Test a variety of Android-powered devices. Each device is tested to measure the average tap times. Each mobile device needs to be tested with two different cards. 10

20 taps with at least 80% at 500 milliseconds or less.

At least 95% success is the pass rate.

Tap success rate: Test the performance and stability of the network on both high-end and low-end devices with the same payment card.

The objective is to ensure performance of the network. This pass rate doesn't include failures due to issues like user error.


100 taps with a 95% pass rate

Cardholder verification methods (CVM) test: Test device unlock rules to ensure that they're implemented correctly. Tests are based on the time since last user unlock.

Unlocking shouldn't be required for up to 10 low-value transit transactions.

1 Approximately 10 taps for all of the types of CVM rules. This is a pass or fail test.

After the tests listed above are confirmed as successful by your team, Google conducts our own tests in production.