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
- 1Follow PCI DSS guidelines for payment handling.
Code examples
Payment Request API: always verify server-side
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.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
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.