Security & payments
How money actually moves through Wedgefund
Short version: it doesn't move through Wedgefund. Every club's dues flow through that club's own Stripe Express account, straight to that club's own bank. Here's the plain-language explanation of how, and what that means for the data involved.
How the money flows
Your club creates its own Stripe Express account
When a club sets up dues collection, we hand off to Stripe's own hosted onboarding flow. Your club's treasurer or admin enters their bank details, business or individual information, and identity verification (KYC) directly into Stripe's UI — not ours. That data goes straight to Stripe. Wedgefund's servers never see bank account numbers, government ID, or identity documents.
Members pay dues with a card, on a Stripe-hosted checkout
When a member pays dues, the card entry happens on Stripe-hosted checkout or Stripe Elements — a form served and secured by Stripe, embedded in the app but never touching our servers. Wedgefund never receives, transmits, or stores full card numbers.
The charge is a direct charge into your club's account
The payment is created as a direct charge on your club's own connected Stripe account, not on a Wedgefund account. That means the money legally and technically belongs to your club from the moment the charge succeeds. It never pools with other clubs' money, and it never sits in an account Wedgefund controls.
Stripe pays your club's bank on Stripe's own schedule
Payouts from the connected account to your club's bank happen automatically on Stripe's standard payout schedule for your account (commonly a rolling daily or weekly schedule, depending on the account's history and country). Wedgefund does not initiate, hold, delay, or approve payouts — that relationship is between your club and Stripe.
Card data & PCI compliance
Because card entry happens entirely on Stripe-hosted pages and Stripe Elements, Wedgefund never receives, processes, or stores primary account numbers, CVV codes, or magnetic-stripe data. That keeps our own PCI DSS compliance burden to the simplest applicable level (a self-assessment questionnaire for merchants who fully outsource card handling to a certified processor) rather than the far heavier requirements that apply to businesses that touch raw card data directly. Stripe carries that certification so individual clubs and their treasurers don't have to.
What Wedgefund can and can't see
Wedgefund can see
- Dues amounts, who paid, and when (via the Stripe API)
- Whether a club's Stripe onboarding is complete
- High-level payout status (paid out / pending)
Wedgefund cannot see
- Full card numbers, CVV, or expiration dates
- Bank account or routing numbers
- Government ID or identity verification documents
General data practices
All traffic to and from Wedgefund is encrypted in transit (HTTPS/TLS). Access to club and member data is restricted to what's needed to run the product, and we don't sell member data to third parties. For the specifics of what account and club data we collect and how it's used, see our Privacy Policy.
Wedgefund is not a money transmitter
Because dues are charged directly into each club's own Stripe account and paid out directly to that club's own bank, Wedgefund never takes custody of member funds. We're a software vendor charging a flat subscription fee for the app that helps a club organize itself — Stripe is the regulated payments infrastructure underneath, handling money movement, identity verification, and payouts.
Have a question about this?
Treasurers, admins, and reviewers alike — happy to walk through it.