Press Releases

Fime’s Shenzhen lab receives EMVCo, Mastercard and Visa accreditations

September 11, 2018

Posted by: Anasia D'mello

Lionel Grosclaude of Fime

Fime’s Shenzhen, China laboratory is now accredited by EMVCo to deliver contactless EMV Level 1 card, terminal and mobile, and contact EMV Level 2 terminal testing, debugging and type approval services.

In parallel, the lab has received accreditation from Mastercard and Visa to deliver contactless terminal testing and type approval services in-line with each scheme’s respective requirements. This stack of accreditations gives Chinese chip, terminal and device manufacturers access to local support as they seek to certify their EMV projects in line with the payment industry’s key international payment body and schemes.

Combined with Fime’s leading payments testing consultancy, tools and solution engineering services, the Fime China office is now able to deliver end-to-end support for EMV projects, responding to the region’s increasing demand for multi-scheme solutions and the rise of vendors keen to trade internationally.

“Payments in China is a rapidly expanding market, and vendors have increasingly global business aspirations. Combining these latest accreditations with our global expertise, our China lab can now offer local support to vendors delivering EMV solutions in line with the biggest international schemes, without the additional cost and inconvenience of a test service provider based abroad.” comments Lionel Grosclaude, CEO at Fime.

“We’re excited by the significant and swift progress of our Shenzhen lab since opening in December last year. We’re closer than ever to our customers and are committed to continually expanding our scope of localised,best-in-class and increasingly automated test tools, platforms and services to address the market’s needs”.

Fime has over twenty years’ experience in the EMV space and works actively with EMVCo and the global and regional payment schemes to support the development and evolution of these specifications and guidelines.

Comment on this article below or via Twitter @IoTGN