Skip to content

What is Payment Page Integrity?

Definition

Payment Page Integrity is the set of controls that makes sure the page where the buyer pays hasn’t been altered to steal card data or divert the payment. It’s the subject of PCI DSS requirements 6.4.3 and 11.6.1, which cover the scripts on that page and changes to it.

What PCI DSS requires for the payment page

Requirement 6.4.3 calls for every script loaded on the payment page to be authorized, justified and integrity-assured, with an up-to-date inventory. Requirement 11.6.1 calls for a mechanism that detects and alerts on unauthorized changes to script content and to the payment page’s security headers, as the buyer’s browser receives them.

Both exist because of attacks that insert malicious code into the page to copy card details while the buyer types, known as Magecart.

The three controls of payment page integrity

  • Inventory and authorization: knowing which scripts run, why each one is there and who approved it.
  • Change detection: noticing when a script, a field or a header changes without authorization, and raising an alert.
  • Checking the result: verifying that what the buyer sees and submits is what the store published, including card forms, QR codes and boleto payment codes.

Why an inventory alone isn’t enough

An inventory tells you that an authorized script is on the page. It doesn’t tell you whether that script’s content changed yesterday, or whether an extension on the buyer’s computer swapped the Pix QR code. That’s why payment page integrity combines script control with checking what actually appears on screen.

For methods other than cards, such as Pix (Brazil’s instant payment system), boleto (a Brazilian bank payment slip) and instant payment QR codes, checking the result is the only control that catches the swap.

What evidence to keep

For the PCI DSS assessment and for the store itself, it’s worth keeping:

  • the script inventory with the justification and approval for each script;
  • the history of detected changes and what was done about each alert;
  • records of blocked swap attempts, with date, page and payment method.

Examples of what can happen to a payment page

Each row is a change the buyer doesn’t notice and that the page’s controls need to catch.

Payment methodWhat the store issuedWhat the screen shows after the swap
Credit cardApproved payment script with no changesSame script with a new snippet that sends typed details elsewhere
Debit cardThe store’s card fieldsExtra fields asking for a PIN or details the store doesn’t ask for
PixThe order’s QR codeQR code swapped after the page loaded
BoletoPayment code issued by the storePayment code changed on screen

What payment page integrity is not

  • It’s not just a report for the auditor

    Evidence is a by-product. The goal is to stop the buyer from paying someone else or handing over card details.

  • It’s not only about cards

    PCI DSS is about cards, but the same page shows Pix, boleto and other methods, which can be swapped in the same way.

  • It’s not script blocking

    Blocking everything breaks the store. The right control authorizes what’s needed and checks the result.

Frequently asked questions

My store uses the gateway’s card fields. Do requirements 6.4.3 and 11.6.1 apply?

It depends on how the page is built. When the store’s page loads the gateway’s form, the store’s page can still be altered to show a fake form. Confirm the scope with your assessor.

How often does the page need to be checked?

Requirement 11.6.1 calls for the check at least once every seven days, or at the frequency set by the company’s risk analysis. A check on every payment goes beyond the minimum.

Is Payment Page Integrity the same as Payment Integrity?

They complement each other. Payment Page Integrity protects the payment page. Payment Integrity checks the payment data itself. The right page with the wrong Pix is still a loss.

Before your next payment, check who’s protecting your customer’s screen

Choose the path that fits your business: start a free trial for your store or book a demo built on your real payment flow.