Skip to main content
InfoCode

How to fix: Payment Request API Usage

Payment Request API detected.

Why it matters

Ensure secure payment handling.

Payment API handles financial transactions.

How to fix it

  1. 1Follow PCI DSS guidelines for payment handling.

Code examples

Payment Request API: always verify server-side

JavaScript
const req = new PaymentRequest(methods, details);
const response = await req.show();

// Never trust the browser response alone
// Always verify the payment server-side:
const serverVerify = await fetch("/api/verify-payment", {
  method: "POST",
  body: JSON.stringify({ paymentId: response.requestId }),
  headers: { "Content-Type": "application/json" },
});
if (!serverVerify.ok) throw new Error("Payment verification failed");
await response.complete("success");

References

Detected automatically by VulnRadar. The check id is payment-request-api, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is Payment Request API Usage?
VulnRadar rates this info severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id payment-request-api, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for payment request api usage

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Payment Request API Usage | VulnRadar