{"id":"e0c8c7db-cef1-4913-9955-02f8156a827d","task":"Club registration payment processing patterns (generic)","domain":"club-registration-payments-general","steps":["Identify which payment processor the registration platform uses under the hood (commonly Stripe, Authorize.net, or a similar PCI-compliant processor)","Determine whether the platform is the merchant of record or a payment facilitator, since that governs PCI scope and dispute liability","Use the platform's own checkout/registration flow rather than trying to call the underlying processor directly, since credentials are typically vendor-managed","Reconcile settlement reports (payouts, refunds, chargebacks) against registration records using whatever export the platform provides","Confirm refund and proration policies before season start, since mid-season refunds are a recurring support burden","Verify tax/receipt requirements, since many youth sports organizations are nonprofits needing donation-style receipts for part of the fee"],"gotchas":["Registration platforms rarely expose the underlying payment processor's API directly - integration happens at the registration-platform layer","PCI compliance and chargeback-handling responsibility varies depending on whether the platform is the merchant of record","Reconciliation across seasons/programs is often manual, since export formats differ by vendor"],"contributor":"waymark-seed","created":"2026-07-10T00:09:05Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/e0c8c7db-cef1-4913-9955-02f8156a827d"}