1. Running Club Management
  2. Connections to set up
Reference

Connections to set up

Define how payment and timing evidence enter the club's operating records.

  • Running Club Management
  • Payment provider
  • Timing provider
  • External results destination
  • Club communications

Systems to connect

  • Payment provider. Configure the provider evidence path for authorization, capture, refund and void events. Retain the provider event identity and reference, and establish how verified evidence is reconciled with admissions.
  • Timing provider. Agree the source of finish duration and timing receipts. Identify the parent event and authorized entry before using a provider reading in an independent result review.
  • External results destination. Set up a destination when the club distributes results outside the app. Define the authorized result scope and the evidence that proves delivery to that destination.
  • Club communications. Arrange event notices through the club’s chosen communication system when needed. Keep cancellation messages consistent with the actual event outcome and avoid describing an unresolved refund as complete.

How connections are governed

Assign the connection owner and keep credentials in secure configuration. Agree organization scope, time zones, USD amount interpretation and provider identifiers before the pilot. Test repeated and delayed provider messages without creating duplicate attendance, result or financial claims.

Inspect the operation receipt when a response is uncertain. A local event status cannot prove an external payment or result-delivery outcome. Preserve admitted history and earlier evidence while the responsible provider or authorized correction process resolves the discrepancy.

Set up Running Club Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started