Card details are collected by your own page, not a hosted payment field

Why it matters

This page contains its own input fields for the value, so the card number is typed into markup you serve rather than into the payment provider's iframe. Two consequences follow. Security: any script on the page — an analytics tag, a chat widget, a compromised dependency — can read the card as it is typed, which is exactly how card-skimming attacks work. Compliance: touching raw card data takes you out of the simplest PCI DSS bracket (SAQ-A, which is what using a hosted field buys you) and into a far heavier assessment. Providers render these fields in their own iframe specifically so the data never enters your page. If you are knowingly running a full PCI programme, this is expected and can be ignored.

How ShipReady detects it

Payment configuration that stops money arriving. The failure this pillar exists for is mundane and catastrophic: a live site wired to a payment provider's TEST environment. Checkout appears to work, the form submits, a success page renders — and no money ever moves. It survives launch because the developer's own testing passes perfectly, and it is usually found when a founder wonders why a week of signups produced no revenue. Deliberately narrow. Every rule here keys off a marker that is definitionally a test credential — Razorpay's `rzp_test_` prefix, Paddle's sandbox environment call, Adyen's test Checkout host. None of them require interpretation, none of them can appear in a correctly configured production deployment, and none of them involve touching the payment provider or attempting a transaction. One marker is shared rather than definitional: `pk_test_` is issued by BOTH Stripe and Paystack. It still proves test mode, so it is still reported — but the provider is resolved from what the page actually loads rather than assumed from the prefix (see _publishable_key_provider). NOT checked, deliberately: whether a checkout page exists or is reachable. Payment routes have no convention — /checkout, /pricing, /billing, /upgrade, /subscribe are all common and most sites have none of them. Probing a list of guesses and reporting the 404s would produce noise on nearly every scan, which is the opposite of what this pillar is for.

Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.4.0.

How to fix it

This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.

Your page collects card details in its own input fields instead of the payment provider's hosted element, so the card number passes through markup you serve — readable by any script on the page, and disqualifying you from the simplest PCI bracket (SAQ-A). Replace the hand-built card form with the provider's hosted field: with Stripe use Payment Element (`stripe.elements()` then `elements.create('payment')` mounted into an empty <div>) or redirect to Stripe Checkout; Braintree has Hosted Fields, Adyen has Components. The provider renders the inputs inside its own iframe, so the raw number never touches your page and you receive only a token. Delete the old <input> fields entirely — leaving them in the DOM keeps the exposure even if you stop reading them — and make sure no card value is ever logged, stored, or sent to your own backend. If you are knowingly running a full PCI DSS programme and are assessed for handling card data directly, this finding is expected and can be ignored.

Frequently asked questions

What does "Card details are collected by your own page, not a hosted payment field" mean?

This page contains its own input fields for the value, so the card number is typed into markup you serve rather than into the payment provider's iframe.

How serious is it?

ShipReady rates this high. Fix before launch. A real weakness that an attacker can act on.

How do I fix it?

Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.

Can I check my own site?

Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check. The free report lists every issue it finds and shows full evidence and a fix prompt for the critical and high-severity ones; medium and low findings are counted and unlock on Pro.

Related checks

• A payment form submits over an unencrypted http:// connectionhigh
• Payment test mode keyhigh
• Working discount codes are compiled into the browser bundlehigh
• A PayPal order is priced in the browsermedium
• Both live and test Stripe keys are shipped to the browsermedium
• Checkout price is submitted from a hidden form fieldmedium