Address Verification System (AVS) checks are enabled
Why it matters
Without billing address data, the card network's Address Verification System (AVS) cannot run a fraud check on the transaction. AVS compares the postal code and street address the customer provides against the address on file with the card issuer — a mismatch is one of the strongest signals that a card is being used fraudulently. Skipping AVS doesn't just reduce fraud detection accuracy; it increases your Stripe Radar risk score across all transactions and can raise your effective fraud dispute rate. PCI-DSS 4.0 Req 6.4 covers fraud detection controls; missing AVS data is a direct gap in that control layer for card-present and card-not-present transactions alike.
Severity rationale
Medium because omitting billing address data disables AVS fraud scoring at the card network level, increasing the success rate of fraudulent card-not-present transactions against your store.
Remediation
Collect billing address fields in the checkout form and pass them in billing_details when creating or confirming the PaymentMethod.
const { error } = await stripe.confirmPayment({
elements,
confirmParams: {
return_url: `${window.location.origin}/checkout/complete`,
payment_method_data: {
billing_details: {
name: formData.cardholderName,
email: formData.email,
address: {
line1: formData.billingLine1,
city: formData.city,
state: formData.state,
postal_code: formData.postalCode, // minimum required for AVS
country: formData.country,
},
},
},
},
})
At minimum, collect postal_code and country. Stripe Radar uses the AVS result automatically once billing_details.address is populated — no additional Radar rule configuration is required.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Payment Security Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- pci-dss:4.0 · Req 6.4 — Web-facing applications protected against attacks
Taxons
History
- 2026-04-18·v1.0.0·Initial import from ecommerce-payment-security·automated