get_route(), '/wp/v2/' ) === 0 ) {\n return new WP_Error( 'rest_forbidden', 'Not available', [ 'status' => 401 ] );\n }\n return $res;\n}, 10, 3 );\n\n/* ---------- Render ---------- */\nadd_action( 'template_redirect', function () {\n if ( ! is_page() ) return;\n $id = get_queried_object_id();\n if ( get_page_template_slug( $id ) !== KW_LEGACY_TEMPLATE ) return;\n $html = get_post_meta( $id, 'kw_legacy_html', true );\n if ( ! $html ) return;\n header( 'X-Robots-Tag: noindex, nofollow', true ); /* 2026-11-03: archived former site under /www9/, never indexed */\n if ( strpos( $html, '' ) !== false ) {\n $fid = (int) get_option( 'kw_legacy_form_id' );\n $form = $fid ? do_shortcode( '[contact-form-7 id="' . $fid . '" html_class="kw-legacy-form"]' ) : '';\n $html = str_replace( '', $form, $html );\n }\n status_header( 200 );\n header( 'Content-Type: text/html; charset=UTF-8' );\n echo $html; // stored, already processed HTML of the former site\n exit;\n}, 5 );\n\n/* ---------- Build helpers (used once by the import script) ---------- */\nfunction kw_legacy_local_base() {\n $u = wp_upload_dir();\n return [ $u['basedir'] . '/kw-legacy/', '/wp-content/uploads/kw-legacy/' ];\n}\n\n/** Download one old-site path (e.g. wp-content/themes/Divi/style.css) into uploads/kw-legacy/. CSS refs are followed. */\nfunction kw_legacy_mirror( $path, &$done = [] ) {\n $path = ltrim( preg_replace( '/[?#].*$/', '', $path ), '/' );\n if ( $path === '' || isset( $done[ $path ] ) ) return;\n $done[ $path ] = 1;\n if ( ! preg_match( '/\.[a-z0-9]{2,5}$/i', $path ) ) return; // directory-like\n [ $dir ] = kw_legacy_local_base();\n $dest = $dir . $path;\n if ( ! file_exists( $dest ) ) {\n $r = wp_remote_get( KW_LEGACY_SRC . '/' . $path, [ 'timeout' => 30 ] );\n if ( is_wp_error( $r ) || wp_remote_retrieve_response_code( $r ) !== 200 ) { $done[ $path ] = 'ERR'; return; }\n wp_mkdir_p( dirname( $dest ) );\n file_put_contents( $dest, wp_remote_retrieve_body( $r ) );\n }\n if ( preg_match( '/\.css$/i', $path ) ) {\n $css = file_get_contents( $dest );\n preg_match_all( '/url\(\s*[\'"]?([^\'")]+)[\'"]?\s*\)|@import\s+[\'"]([^\'"]+)[\'"]/i', $css, $m );\n foreach ( array_merge( $m[1], $m[2] ) as $ref ) {\n if ( ! $ref || strpos( $ref, 'data:' ) === 0 ) continue;\n if ( preg_match( '#^(https?:)?//#', $ref ) ) {\n if ( ! preg_match( '#^(https?:)?//(www\.)?kersonwallaw\.com/(.+)$#', $ref, $mm ) ) continue;\n $p = $mm[3];\n } elseif ( strpos( $ref, '/' ) === 0 ) {\n $p = substr( $ref, 1 );\n } else {\n $p = kw_legacy_resolve( dirname( $path ), $ref );\n }\n kw_legacy_mirror( $p, $done );\n }\n // make absolute old-host refs inside CSS local\n [ , $web ] = kw_legacy_local_base();\n $css2 = preg_replace( '#(https?:)?//(www\.)?kersonwallaw\.com/(wp-content|wp-includes)/#', $web . '$3/', $css );\n $css2 = preg_replace( '#url\(\s*([\'"]?)/(wp-content|wp-includes)/#', 'url($1' . $web . '$2/', $css2 );\n if ( $css2 !== $css ) file_put_contents( $dest, $css2 );\n }\n}\n\nfunction kw_legacy_resolve( $base, $rel ) {\n $rel = preg_replace( '/[?#].*$/', '', $rel );\n $parts = $base === '.' ? [] : explode( '/', $base );\n foreach ( explode( '/', $rel ) as $seg ) {\n if ( $seg === '' || $seg === '.' ) continue;\n if ( $seg === '..' ) array_pop( $parts ); else $parts[] = $seg;\n }\n return implode( '/', $parts );\n}\n\n/** Decode a Cloudflare-obfuscated e-mail. */\nfunction kw_legacy_cfdecode( $hex ) {\n $k = hexdec( substr( $hex, 0, 2 ) ); $o = '';\n for ( $i = 2; $i < strlen( $hex ); $i += 2 ) $o .= chr( hexdec( substr( $hex, $i, 2 ) ) ^ $k );\n return $o;\n}\n\n/** Turn an old page's HTML into the bridge copy. $pages = [old path => new path]. */\nfunction kw_legacy_process( $html, $pages ) {\n [ , $web ] = kw_legacy_local_base();\n $src = preg_quote( 'www.kersonwallaw.com', '#' );\n\n // 1. Contact form → placeholder\n $p = strpos( $html, '
', $p );\n $e = strpos( $html, '
', $e ) + 6;\n $html = substr( $html, 0, $p ) . '' . substr( $html, $e );\n }\n\n // 2. Scripts to drop: cookie banner, reCAPTCHA, Google tag, old CF7 JS, Cloudflare helpers\n $drop = '(complianz|cmplz|recaptcha|googletagmanager|gtag\(|contact-form-7|wpcf7|/swv/|cdn-cgi|challenge-platform)';\n $html = preg_replace_callback( '#]*>.*?#is', function ( $m ) use ( $drop ) {\n return preg_match( '#' . $drop . '#i', $m[0] ) ? '' : $m[0];\n }, $html );\n $html = preg_replace( '#]*(complianz|cmplz)[^>]*>#i', '', $html );\n $html = preg_replace( '#]*rel=["\'](alternate|EditURI|pingback|https://api\.w\.org/|shortlink)["\'][^>]*(feed|xmlrpc|wp-json|oembed|\?p=)[^>]*>#i', '', $html );\n $html = str_replace( '', "\n", $html );\n\n // 3. Cloudflare e-mail obfuscation\n $html = preg_replace_callback( '#href="/cdn-cgi/l/email-protection\#([0-9a-f]+)"#i', fn( $m ) => 'href="mailto:' . esc_attr( kw_legacy_cfdecode( $m[1] ) ) . '"', $html );\n $html = preg_replace_callback( '#<(span|a)\b[^>]*data-cfemail="([0-9a-f]+)"[^>]*>.*?#is', fn( $m ) => esc_html( kw_legacy_cfdecode( $m[2] ) ), $html );\n\n // 4. Assets → local mirror (plain and JSON-escaped)\n $html = preg_replace( '#(https?:)?//' . $src . '/(wp-content|wp-includes)/#', $web . '$2/', $html );\n $html = preg_replace( '#(https?:)?\\\\/\\\\/' . $src . '\\\\/(wp-content|wp-includes)\\\\/#', str_replace( '/', '\\/', $web ) . '$2\\/', $html );\n $html = preg_replace( '#(["\'(])/(wp-content|wp-includes)/(?!uploads/kw-legacy/)#', '$1' . $web . '$2/', $html );\n $html = str_replace( $web . 'wp-content/uploads/kw-legacy/', $web, $html ); // guard against double rewrite\n\n // 5. Page links → bridge pages\n $html = preg_replace_callback( '#(https?:)?//(www\.)?kersonwallaw\.com(/[^"\'\s<>]*)?#i', function ( $m ) use ( $pages ) {\n $full = $m[3] ?? '/';\n if ( $full === '' ) $full = '/';\n $path = preg_replace( '/[?#].*$/', '', $full );\n $tail = substr( $full, strlen( $path ) );\n $key = '/' . trim( $path, '/' ) . '/';\n if ( $key === '//' ) $key = '/';\n if ( isset( $pages[ $key ] ) ) return $pages[ $key ] . $tail;\n return $full; // other same-site paths (e.g. /ubitrak_grc/) stay relative\n }, $html );\n $html = preg_replace( '#(action|href)="/fr/\##', '$1="/www9/fr/#', $html );\n\n return $html;\n}\n Which PCI self-assessment questionnaire applies to you? A plain guide for small merchants - Kerson Wallaw
Kerson Wallaw
400-3 Place Ville Marie, Montréal QC H3B 2E3
Ph: (514) 312-1555
Book a free consult
Pick a time · Request a callback
Back

Which PCI self-assessment questionnaire applies to you? A plain guide for small merchants

← Back to all insights

If you accept credit cards and your business is not large, your bank or payment processor has probably asked you to complete an “SAQ”. The term is confusing, and picking the wrong form is one of the most common mistakes we see. This guide explains what a Self-Assessment Questionnaire is, how to tell which one applies to you, and what changed for SAQ A in 2025.

What is an SAQ?

A Self-Assessment Questionnaire is a form, published by the PCI Security Standards Council, that lets eligible merchants report on their own compliance with PCI DSS. Each SAQ covers only the requirements that apply to a particular way of accepting payments. The fewer card systems you control, the shorter the form.

Two points matter before you start. First, not every business may self-assess: the Council tells merchants to contact their merchant bank (acquirer), the payment brands or other compliance entity to confirm eligibility and the right SAQ. Second, the SAQ is a validation tool. The underlying security requirements still apply even when they are not on your form.

The main SAQ types

The Council’s overview of the v4 SAQs lists the following options. Here they are in plain terms:

  • SAQ A: card-not-present merchants (online, mail or phone) that have fully outsourced card handling, for example by redirecting customers to a payment provider’s page or using the provider’s embedded form.
  • SAQ A-EP: e-commerce merchants that outsource payment processing but whose own website can affect the security of the payment transaction.
  • SAQ B: merchants that use only imprint machines or standalone dial-out terminals.
  • SAQ B-IP: merchants that use only standalone, PCI-approved payment terminals connected by IP to the processor.
  • SAQ C-VT: merchants that key transactions one at a time into a provider’s virtual terminal on an isolated computer.
  • SAQ C: merchants with payment application systems connected to the internet.
  • SAQ P2PE: merchants that use only a validated point-to-point encryption (P2PE) solution.
  • SAQ SPoC: merchants using a validated software-based PIN entry on COTS solution, such as accepting cards on a commercial phone or tablet.
  • SAQ D: everyone else, and the only SAQ available to eligible service providers.

A quick way to narrow it down

  1. List every way you take payments: website, phone orders, terminals in store, mobile devices, kiosks.
  2. For each channel, ask who touches the card data: you, your systems, or only a third party.
  3. Check the eligibility criteria at the start of the SAQ you think fits. If you cannot answer “yes” to every criterion, that SAQ does not apply.
  4. If you have several channels, ask your acquirer whether you can complete more than one SAQ or must use a broader one.

What changed for SAQ A in 2025

PCI DSS v4 introduced two requirements aimed at web skimming: 6.4.3 (managing scripts on payment pages) and 11.6.1 (detecting unauthorized changes to payment pages). Originally, they appeared in SAQ A, which worried small online merchants that rely on a provider’s embedded payment form.

On 2025-01-30, the Council announced an updated SAQ A that removes requirements 6.4.3, 11.6.1 and 12.3.1 from the questionnaire. In their place, it added an eligibility criterion: the merchant must confirm that its site is not susceptible to attacks from scripts that could affect the merchant’s e-commerce system(s). The updated SAQ A took effect on 2025-03-31.

The Council then published FAQ 1588 on 2025-02-28 to explain how to meet this criterion. A merchant that embeds a provider’s payment form (for example, in an iframe) can either:

  • use techniques such as those described in requirements 6.4.3 and 11.6.1 to protect its own page from script attacks, or
  • obtain confirmation from its payment provider that the embedded solution includes techniques that protect the merchant’s payment page from script attacks, when implemented according to the provider’s instructions.

The FAQ also notes that this criterion applies to merchants using embedded payment forms, not to those that fully redirect customers to the provider’s site.

The Council stressed that these changes to SAQ A do not remove or diminish the underlying requirements within PCI DSS.

Practical tips

  • Keep written confirmation from your payment provider on file if you rely on it for the script criterion.
  • Review your eligibility each year. A new plug-in, a redesigned checkout or a new sales channel can move you to a different SAQ.
  • Do not guess. Completing the wrong SAQ can leave you exposed if a breach occurs.

Our PCI DSS overview explains the standard in more detail. The Accel PCI self-assessment portal, built by our Accel PCI division, guides merchants to the right SAQ and helps them complete it, and our sample documents show what is expected. If you need help with scope, contact us.

Sources

Does this apply to you? A free 30-minute consult maps the requirement to your systems and tells you what to do next.

Book a free consult
xlowmyzckw
https://kersonwallaw.com