AQX uses fixed private-framework review packages so applicants can decide quickly. Same-scope renewals are 50% of the current package price. We still review route fit before payment, and payment does not guarantee issuance.
These are fixed service prices for eligible private-framework review and certification-support routes. AQX confirms package fit before sending payment instructions.
For a simple eligible request with one legal holder, one standard, and a narrow scope.
For common ISO or private-framework certificate support where the scope and evidence need more review.
For urgent supplier, tender, marketplace, or onboarding requests that need priority handling.
For multi-site, complex, buyer-specific, or higher-risk requests that need deeper evidence mapping.
Fixed prices apply to the package AQX approves for the reviewed file. If the buyer requires a formal accredited, licensed, regulated, or named-body route, AQX will flag that before payment instead of forcing the wrong package.
Payment links and bank details are issued after AQX confirms the approved fixed package and route suitability. Do not pay through an old link or unverified account.
Before payment, AQX sends payment instructions or a payment link. After cleared funds, AQX can send payment confirmation. A pre-payment email should not be called a receipt.
These controls reduce refund disputes, buyer misunderstanding, and certificate misuse.
AQX links the payment request to a specific applicant, standard, scope, and buyer requirement.
AQX confirms whether the file fits the $398, $699, $999, or $1,599 package before sending payment instructions.
AQX confirms cleared funds and checks that the payer matches the reviewed application or approved client account.
Paid work starts after payment confirmation and remains subject to scope, evidence, corrections, and final review.
If your buyer requires a specific accreditation body, certification body, national scheme, product approval, or government acceptance, send that wording to AQX before payment.
Every support page should move the visitor from vague interest to a clear buying decision: what the buyer wants, what the organization can prove, and whether the route is worth budget.
Clauses, portal text, tender wording, country context, and deadline details turn an unclear request into something AQX can actually review.
The route only makes sense when the activities, sites, services, and legal entity match what the buyer is asking for.
Useful files include records, policies, procedures, monitoring, training, and prior assessments that support the claim being made.
If the requirement still looks ambiguous or misaligned, AQX should review it before the applicant spends on the wrong path.