Managed Certification

Managed EMV Level 3 Certification

Keep your engineers focused on your application. We manage testing, findings, and certification coordination.

Managed certification is for teams that already have a payment application and developers who can maintain and fix it. Paying.co runs the testing, tracks findings, validates fixes, and coordinates submission.

Is this the right engagement?

task_alt
You have a working applicationBuilds that can be tested against your processor and terminal.
task_alt
Your developers fix findingsThey change the code. We document, validate, and retest.
swap_horiz
Need the application built or reworked?Explore EMV Level 3 certification services
01 · Who it fits

Who managed certification is for, and what must be ready.

Processors, ISVs, and terminal manufacturers choose this option when the application exists and the internal team can own the code. Execution can start once the items below are available or have named owners.

Application readiness

  • check_circleAn existing application and its current build status
  • check_circleDevelopers available to investigate and fix findings
  • check_circleProcessor and specific host or platform
  • check_circleTerminal models, firmware and kernel versions, and relevant approval evidence
  • check_circleRegions, card brands, entry modes, and transaction types
  • check_circleRequired specifications, credentials, SDKs, hardware, and a test environment
  • check_circleProcessor project setup and any known external dependencies
  • check_circleAgreed owners for access, code changes, submissions, and decisions

When another engagement fits better

If you need an application built, substantially reworked, or fixed by us, the engagement is application development plus certification. Explore EMV Level 3 certification services.

Not sure which applies? Compare managed certification with full payment application development.

Engineering QA is not a substitute for formal processor or scheme test plans. Review application testing beyond approved and declined transactions.

02 · Responsibilities

What Paying.co handles, what you handle, and what depends on others.

This is the typical division of work. Processors differ in workflow, terminology, and approval path, and the final split for your engagement is set in the Statement of Work.

WorkstreamPaying.coClientProcessor or other approval parties
Scope and certification planDefines the contracted testing and coordination workConfirms application requirements and deployment scopeConfirm applicable requirements and approval path
Application readinessAssesses readiness within the agreed scopeSupplies working builds, hardware and access, and developer supportSupply required specifications and access through the appropriate relationship
Test execution and evidenceExecutes agreed tests and organizes resultsProvides builds and resolves application dependenciesDefine or confirm applicable test and evidence requirements
Findings and code changesDocuments findings and validates submitted fixesImplements application changesReview findings or submissions where required
Submission coordinationCoordinates agreed submission activitiesSupplies required approvals and application inputsConduct applicable review and approval activities
Status and blockersReports progress and dependenciesResponds to decisions and assigned actionsSupply external scheduling and review updates
CompletionDelivers agreed evidence and handoffAccepts deliverables and prepares rolloutProvide applicable approval outcomes
03 · Deliverables

What you receive.

Exact inclusions are listed in your scope. These are the core deliverables of a managed engagement.

checklist

Certification plan

The agreed scope: device and configuration, processor and host, brands, entry modes, transaction flows, and assumptions.

fact_check

Test execution

Execution of the agreed tests against the builds you supply.

folder_open

Results and evidence

Results organized and maintained as evidence for submission and review.

bug_report

Findings tracking

Each finding recorded with expected result, observed behavior, owner, and status.

send

Submission coordination

Coordination of the agreed submission activities with the processor and other parties.

monitoring

Status reporting

Progress, dependencies, decisions needed, and blockers reported through the engagement.

04 · Findings, fixes, and retesting

How a finding moves from failed test to closed.

Your developers change the code. We keep the loop moving and keep the evidence current.

  1. RecordFailed test, observed behavior, expected result, and available evidence.
  2. AssignName an owner and classify the cause: application code, configuration, access, hardware, or external dependency.
  3. FixYour developers implement application fixes where applicable.
  4. ValidatePaying.co validates the new build and performs the agreed retesting.
  5. UpdateEvidence is updated and further review or submission is coordinated as required.

Included retest cycles, change-control rules, and the effect of new requirements or configuration changes are defined in the Statement of Work.

Source code and IP

Source access is not assumed. Testing is normally run against supplied builds and interfaces, and your developers investigate and change the code. Where an engagement needs source access or a code review, we agree the access, permissions, and confidentiality terms in writing first. Your application and IP remain yours.

What we do not do

We do not grant approvals, change your application unless that work is separately scoped, or promise approval dates that depend on processors, labs, or schemes.

05 · Schedule, scope, and pricing

Milestones, dependencies, and scope boundaries.

Timelines have three parts: Paying.co execution time, your time to fix findings, and external scheduling and review. We plan them separately so the dates you are given are honest.

flag

Milestones and dependencies

Plan, readiness assessment, test execution, findings and retesting, submission, and completion. Each milestone lists what it depends on and who owns it.

inventory_2

Scope

The scope names the device and configuration, processor and host, region, card brands, entry modes, and transaction flows, plus included testing, evidence, coordination, and retesting.

rule

Exclusions and changes

Application engineering, hardware, third-party fees, and external-party work are excluded unless listed. Scope changes and additional test cycles go through change control.

Pricing depends on scope, number of devices and configurations, brands and entry modes, and retest cycles. Understand EMV certification cost and timeline factors. Explore the EMV Level 3 certification process.

06 · Visibility and handoff

Know where things stand, and what done means.

visibility

Progress visibility

You see findings, decisions needed, milestones, and blockers as the engagement progresses, with status reporting at an agreed cadence.

done_all

Completion and handoff

Completion criteria are agreed up front. At completion you receive the final test results, applicable approval evidence, documentation, a list of any open items and how they are treated, and a transition to rollout. Post-approval maintenance, recertification, and changes are scoped separately unless the agreement says otherwise.

07 · Related resources

Read before you scope.

08 · Questions

Managed certification FAQ

Do you need access to our source code?

It depends on the engagement. Testing is normally run against builds, interfaces, and logs that you supply, so source access is often not required for test execution. Your developers investigate and implement application fixes. If a particular engagement needs source access or a code review, we agree the access, permissions, and confidentiality terms in writing before work begins.

Who fixes the findings?

Your developers change the application code. Paying.co records each finding, helps identify whether it is an application, configuration, access, hardware, or external issue, validates the fixed build, and performs the agreed retesting. If you want us to make the fixes, that is application development, covered under full EMV Level 3 certification services.

How many retest cycles are included?

Included retest cycles are defined in the Statement of Work for each engagement. New requirements, configuration changes, or cycles beyond the agreed number are handled through change control.

How long does managed certification take?

It depends on application readiness, how quickly findings are fixed, hardware and credential availability, and processor or scheme scheduling and review. We separate Paying.co execution time from client and external time in the plan, and we do not promise approval dates that depend on other parties.

Can you certify an application that is not finished?

Managed certification assumes a working application and developers who can fix findings. If the application needs to be built or substantially reworked, full EMV Level 3 certification services are the better fit.

Does Paying.co grant the approval?

No. Approval decisions come from the processor and other applicable parties. Paying.co manages testing, evidence, findings, and submission coordination, and reports the outcome.

What do you need from us to scope the work?

Processor and host or platform, terminal model, deployment region, entry modes and card brands, required transaction types, application readiness, target date, and any specifications, credentials, or hardware you already have.

Start a conversation

Tell us what you need to certify and how ready your application is.

Include as much of the following as you have. Gaps are fine; we will help identify them.

apps
Application and supportApplication readiness and available developer support
hub
Processor and terminalProcessor and host or platform, terminal and relevant configuration
public
Region and transaction scopeDeployment region, entry modes, brands, and transaction types
key
What you already haveSpecifications, hardware, credentials, and approvals
event
Timing and dependenciesTarget date and known external dependencies
schedule
Response within one business dayMost projects start with a 30-minute scoping call

Start your project

Sales online

Tell us about your project — we route you to the right specialist.

person
error_outlinePlease enter your name.
business
mail
error_outlinePlease enter a valid email address.
call
link
tune
error_outlinePlease tell us a bit about your project.

lock Your details go straight to our sales engineers — never shared or sold.