A prop firm website checklist should cover what happens when a trader changes the programme, arrives from a partner link, enters the wrong country or receives a payment error. Use the tests below on the routes you already have. A sound rules page and a clear receipt matter more than reaching an arbitrary page count.
VERIFY WHAT THE TRADER IS BUYING
Pick one programme customers can buy today. Open its page as a first-time visitor and locate the account type, fee, drawdown basis, phase criteria, prohibited activity and reward eligibility. Find which rules differ by programme or phase. If you have several evaluation sizes, verify the detail links and price update together when the selection changes.
Keep an approved record per programme. Name someone to maintain the record, and show an effective date when the rule changes. Use the approved rule text or a clear explanation linked to it, including an example of how a limit is calculated if traders often ask about it. Keep the programme URL stable or redirect it to the direct replacement when the offer retires.
Programme QA record
- Offer detailsAccount type, fee, currency and availability
- Rule detailsPhase, calculation basis and effective date
- EvidencePublished page, source rule and screenshot
- OwnerPerson who signs off changes before release
TEST THE FAILURES AS WELL AS THE SALE
Open the site on a phone and move through the selector, coupon and checkout. Try a stale promo code, an ineligible country and a declined test payment. Show the exact total and currency before payment, and carry the chosen programme and size into the order. A test environment should let you exercise errors without charging anyone.
For the success case, compare the receipt and payment provider record against what was shown before the payment. If a payment retry or double tap reaches the site twice, confirm only one paid order and one challenge appear. Document where checkout and payment records can be found so a support person can diagnose the order without asking for card information. Affiliate tracking and commission reconciliation.
See how programme, size and offer make the trip from the selector to checkout in the MultiFunded checkout handoff case study. Use the downloadable checkout QA checklist to record expected results, evidence and owners for your own release.
- Wrong regionThe buyer gets an explanation before entering payment details.
- Expired promoThe amount and error are visible before purchase.
- Declined paymentThe buyer can retry without creating an extra account.
- Successful paymentThe correct order, receipt and simulated programme agree.
CHECK THE FIRST TEN MINUTES AFTER PAYMENT
Follow the receipt through to the first dashboard visit. Look for the order reference, programme, account access instructions, the rules that apply and a support route. If access is still being prepared, show the actual state and what the trader can do next. Test a delayed provisioning response so the receipt never claims access exists when the system has not created it.
Hand a test order ID to support and ask them to find its payment and account status. Make the refund or cancellation workflow available through the same help centre. Before launch, remove placeholder legal and support details and check that a programme change will be easy for the people answering traders.
Example handoff
- Payment confirmedReceipt contains the order reference and programme name
- Provisioning pendingCustomer can see the current state
- Access availableDashboard link works from the confirmation
- Issue reportedSupport can find the same order with its reference
SIGN OFF THE BUYER JOURNEY
Record the device, country, programme, link, result and owner for each test. Run the main flow on a narrow device and with the settings your audience is likely to use. Check long rule text, keyboard access, error focus and whether important actions remain usable after zooming. Capture a screenshot only where it helps reproduce a defect.
Retest the affected routes after a change to the offer, payment provider, programme, email or terms. If you use paid ads, make someone check the final destination and campaign variants after any redirect changes. The same QA sheet is useful for the first campaign and for the next price or programme launch. Google Ads destination requirements.
- Save expected and actual resultsA colleague can reproduce the issue from the same entry link.
- Name the release ownerSomeone can approve rule changes and stop a broken flow.
- Set a retest triggerRevisit the relevant cases when an input changes.
SOURCE NOTES.
Publisher guidance behind the checks in this guide.