Choose managed EMV certification when you already have a payment app or integration and need help getting it tested, documented, and approved. Choose full payment application development when the app still has to be built, with certification as one phase of that project. The dividing line is simple: does a working application already exist?

This guide shows who does what in each case, what you need before starting, and why readiness is not the same as approval.

Which engagement fits

Your situation Likely fit
A working app exists and needs testing and approval Managed EMV certification
The app needs changes before it can be certified Certification support plus targeted development
There is no app yet, or the current one will be replaced Full payment application development
You are unsure what the processor requires Start with a scoping review

Responsibility matrix

This is a typical split for illustration. The statement of work sets the real one.

Activity Managed certification Full development
Test execution Partner runs the test plan against your app Built into the project phases
Code changes Agreed up front: your team, the partner, or both Development team
Processor coordination Partner supports you, the processor controls its own process Included in the project
Evidence and documentation Prepared by the partner Delivered with the build
Findings Triaged with fix recommendations Fixed in the code
Retesting Scoped for the expected cycles Covered by scope or change control

Prerequisites

✓ A working build you can run against the processor's test environment.

✓ Access to the device, SDK, and any kernel or reader documentation.

✓ The processor's requirements and test plan, or a contact who can provide them.

✓ A named owner on your side for decisions and fixes.

Readiness is not approval

Readiness means your app has been tested against the relevant plans and the evidence is prepared. Approval is granted by the processor, scheme, or lab. Neither a partner nor a developer can promise an approval date or outcome, because scheduling and decisions sit with the external party.

What drives scope

▸ Card brands and regions you need to support.

▸ Contact, contactless, or both.

▸ The number of device models and SDK versions.

▸ Whether the payment kernel and SDK are third party or custom.

▸ The processor's requirements and how many retest cycles occur.

For how EMV levels and the certification process fit together, read the Paying.co guides rather than relying on this summary, and see the managed certification page.

FAQs

Does managed certification guarantee approval?

No. Approval comes from the processor, scheme, or lab. Managed certification aims to get you ready and organized for that process.

Can an existing app that someone else built be certified?

That depends on code access and the state of the app. A scoping review should confirm it before work starts.

How long does certification take?

There is no universal number. It depends on the processor's scheduling, the findings, and retest cycles.

Can we start with certification and add development later?

Yes. Scope them separately so each has clear deliverables.

Next step

If you can share your app status, devices, processor, and brands, we can help decide which engagement fits. Start at the managed certification page.

Sources

▸ EMVCo

▸ Paying.co guides