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.
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.
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.
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.
| Workstream | Paying.co | Client | Processor or other approval parties |
|---|---|---|---|
| Scope and certification plan | Defines the contracted testing and coordination work | Confirms application requirements and deployment scope | Confirm applicable requirements and approval path |
| Application readiness | Assesses readiness within the agreed scope | Supplies working builds, hardware and access, and developer support | Supply required specifications and access through the appropriate relationship |
| Test execution and evidence | Executes agreed tests and organizes results | Provides builds and resolves application dependencies | Define or confirm applicable test and evidence requirements |
| Findings and code changes | Documents findings and validates submitted fixes | Implements application changes | Review findings or submissions where required |
| Submission coordination | Coordinates agreed submission activities | Supplies required approvals and application inputs | Conduct applicable review and approval activities |
| Status and blockers | Reports progress and dependencies | Responds to decisions and assigned actions | Supply external scheduling and review updates |
| Completion | Delivers agreed evidence and handoff | Accepts deliverables and prepares rollout | Provide applicable approval outcomes |
Exact inclusions are listed in your scope. These are the core deliverables of a managed engagement.
The agreed scope: device and configuration, processor and host, brands, entry modes, transaction flows, and assumptions.
Execution of the agreed tests against the builds you supply.
Results organized and maintained as evidence for submission and review.
Each finding recorded with expected result, observed behavior, owner, and status.
Coordination of the agreed submission activities with the processor and other parties.
Progress, dependencies, decisions needed, and blockers reported through the engagement.
Your developers change the code. We keep the loop moving and keep the evidence current.
Included retest cycles, change-control rules, and the effect of new requirements or configuration changes are defined in the Statement of Work.
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.
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.
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.
Plan, readiness assessment, test execution, findings and retesting, submission, and completion. Each milestone lists what it depends on and who owns it.
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.
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.
You see findings, decisions needed, milestones, and blockers as the engagement progresses, with status reporting at an agreed cadence.
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.
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.
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.
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.
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.
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.
No. Approval decisions come from the processor and other applicable parties. Paying.co manages testing, evidence, findings, and submission coordination, and reports the outcome.
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.
Include as much of the following as you have. Gaps are fine; we will help identify them.
Tell us about your project — we route you to the right specialist.