Proteside Docs

Payment integrity

See, method by method, whether what the customer sees at checkout is the payment your store generated.

The Payment Integrity page shows a card for each of the store's payment methods: card, Pix, clipboard, cryptocurrency, boleto and others. You don't pick the methods: the SDK recognizes on its own the ones that show up at checkout. For each one, you see whether the observed payments are intact and whether the recipient shown to the customer really belongs to your store.

The concept is explained in What is payment integrity?, and the swapped QR code scam in Pix QR code scam protection.

Payment Integrity page with the Credit card, Pix and Clipboard cards, the INTACT status, the Recipient matches the trusted list line on the Pix card and the Other methods not seen yet button
A method's card (1), status (2), recipient check (3) and other methods (4).

What each card shows

Each card (1) includes:

  • the method's name and a description of what's monitored;
  • the status (2), explained below;
  • Last validated, when the last payment was checked, or "Waiting for the first transaction of this type";
  • the recipient check (3), for methods that have a recipient: Pix, boleto, cryptocurrency, UPI, PayNow, PromptPay, DuitNow, QR Ph, HK FPS, Transferencias 3.0 and QR wallets.

Credit card has no recipient: the SDK checks the payment provider's form and iframes. On Clipboard and the other methods, the card says the method doesn't need a registered recipient.

Status

StatusMeaning
NOT CONFIGUREDThe store hasn't sent any SDK event yet.
WAITINGThe SDK is active, but no payment of this type has been observed yet. It changes on its own when a customer pays.
INTACTThe last observed payment was validated and there's no open tampering alert.
TAMPEREDThere's an open tampering alert for the method. The card turns red and shows Divergence detected.

The alerts that make each method TAMPERED:

MethodAlerts
Credit cardKeylogger Detected, Form Action Hijack, Iframe Replaced, Unexpected Iframe, Card Field Outside Vault, Amount Tampered
PixPix Tampered (and Amount Tampered on Pix)
CryptocurrencyCrypto Address Swap, QR Tampered
BoletoBoleto Tampered
UPIUPI Tampered
ClipboardClipboard Hijack

See what each alert means in Alerts.

When a method shows as TAMPERED

Open the alert

On the red card, click View Alert →. The Alerts page opens with the alert highlighted.

Investigate

Check the Technical details to see what changed and on which page. A Pix with a recipient outside your list or a form with a changed destination point to an attack until proven otherwise: check the page's scripts in Scripts and the recent changes to the site.

Resolve the alert

After you deal with the cause, resolve the alert with a note. The method goes back to INTACT or WAITING.

Snoozing doesn't take the method out of TAMPERED

A snoozed alert stays open, and the method remains TAMPERED until you resolve the alert. The date in Divergence detected is when the most recent open alert was created, not when it last occurred.

Trusted recipients

The recipient check compares the Pix key, the crypto address, the UPI VPA or the boleto bank shown at checkout with the list of recipients that belong to your store. Register this list so Proteside can confirm that the recipient shown to the customer is yours.

The recipient check line (3) shows one of these situations:

  • Recipient matches the trusted list: all good.
  • Recipient does NOT match the trusted list: the recipient shown isn't yours. Treat it as an incident.
  • A recipient is registered, but this checkout's code carries no readable recipient: not verified. The payment goes through normally, without a recipient check. If you can, show a code that carries the recipient at checkout.
  • No trusted recipient registered for this method., with the Register link.

Click Register

The link opens Settings → Payment protection, at the Who can receive your money step. For methods that accept manual registration, the form opens with the right method already selected. On the Cryptocurrency card, the method is Crypto wallet, and the network is detected from the address format. For Pix, the screen guides you to confirm the recipient under Recipients seen at your checkout.

Add or confirm the recipient

Click It is my store on a recipient seen at checkout, or enter the Key and, if you like, a Label, and click Add. The full walkthrough is in Payment protection.

Only owners and admins can register recipients. Proteside doesn't store the key in plain text.

Other methods not seen yet

The main grid always shows Credit card, Pix and Clipboard, plus the methods that already had a payment checked or have an open alert. The others are collapsed under Other methods not seen yet (N) (4), such as boleto, QR wallets (Mercado Pago, PicPay and others), UPI and instant payments from other countries (PayNow, PromptPay, DuitNow, QR Ph, HK FPS, Transferencias 3.0 and CoDi).

Click it to see those cards. Each one shows its status and the message "Not seen at this store's checkout yet. The SDK recognizes it on its own when it appears." There's nothing to enable: when the method shows up at checkout, its card moves to the main grid.

Notes

Show the payment code as visible text

Show the Pix copy-and-paste code and other payment codes as visible text on the page, outside form fields. The recipient check applies to codes that carry the recipient.

The unregistered recipient notice may be wrong

On a TAMPERED method, the card always shows "No trusted recipient registered", even if you've registered one. The same can happen with old SDK versions. Check the list in Payment protection before registering again.

  • QR Tampered alerts for QR wallets and instant payments from other countries appear on the Cryptocurrency card.
  • Short history: events are deleted after the plan's history period (7 days on Store). If there are no events in the period, every method goes back to NOT CONFIGURED.
  • The page shows whether the payment matches or not, without a side-by-side comparison of the expected and observed values. The data for each divergence is in the alert.

Who can see it

Every role sees this page. It has no actions that change anything: recipients are registered in Payment protection.

Next steps

On this page