Skip to main content

Overview

  • GroupFlow provides integrated online payments for groups and their members
  • Payments are used for:
    • Event registrations and tickets
    • Membership dues
  • Payments are processed through GroupFlow’s built-in payments system
  • Full credit card numbers are never seen or handled by GroupFlow’s systems

Event Payments

  • Events can require payment in order to register
  • Event organizers can:
    • Set one or more ticket types
    • Assign prices to each ticket type
    • Limit ticket quantities
  • Members pay during the event registration flow
  • Each registration is associated with a payment record
  • Group financial administrators can view payment information related to events

Membership Dues

  • Groups can charge members for membership
  • Membership dues may be:
    • One-time
    • Recurring (for example, monthly or annual)
  • Membership dues are collected during signup or renewal
  • Payments for dues are recorded and associated with the member
  • Group financial administrators can view all membership-related transactions

Saved Payment Methods

  • Members can save payment methods to their account
  • Saved payment methods can be used for:
    • Event registrations
    • Membership dues
  • Members manage their payment methods in Account Settings
  • GroupFlow stores limited, non-sensitive details about payment methods, such as:
    • Card brand
    • Last four digits of the card number
    • Expiration date
  • This information is visible to the member who owns the payment method
  • Full credit card numbers and security codes are never stored by GroupFlow

Transaction Fees

  • GroupFlow passes through the same transaction fee charged by its third-party payment processor
  • The current transaction fee is:
    • 2.5% of the transaction amount
    • Plus $0.29 per transaction
  • GroupFlow does not add an additional application or platform fee on top of this cost
  • Transaction fees are a standard and unavoidable part of online payments
  • Payment processing cannot be performed “for free”
  • GroupFlow does not use payment processing as a hidden revenue stream
  • Fees exist to cover:
    • Card network costs
    • Fraud prevention
    • Secure handling of sensitive financial data

Refunds

  • Refunds are issued by GroupFlow Support, on behalf of the group
  • Group leaders contact GroupFlow Support to request a refund
  • Refunds are returned to the original payment method
  • Refund processing time:
    • Can take up to 14 days
    • Is often completed sooner
  • Refunds appear in the group’s transaction records

Privacy & Security

  • Sensitive credit card information is handled by Stripe
  • GroupFlow stores only limited payment method metadata
  • Full card numbers and security codes are never accessible within GroupFlow
  • Access to payment-related information depends on user role and permissions
  • Payment data is protected using industry-standard security practices

Transactions & Financial Records

  • Group financial administrators have access to the group’s full transaction list
  • Transactions include:
    • Payments and refunds
    • Whether the transaction is for an event or membership dues
    • The member or user who made the payment
  • Transaction records support:
    • Financial reconciliation
    • Reporting
    • Member support inquiries
  • Members do not currently have access to a personal payment history view

Notes & Limitations

  • GroupFlow provides tools to accept and manage payments but does not function as a bank
  • Refunds must be coordinated through GroupFlow Support
  • Some payment behavior depends on external financial institutions