Dashboard

Welcome back

Customers

—

total

Cards on file

—

ready to charge

Charges fired

—

total transactions

Total revenue

—

all-time

Revenue trajectory

Last 30 days · projection based on trailing avg

Actual Projected

Next 30 days

Linear projection

—

projected

Avg daily —

Last 30 days —

vs all-time —

Projection assumes recent activity continues. Not a forecast.

Recent transactions

Latest 12 charges

Loading…

Customers

Loading…

Customers

—

Cards on file

—

Total charged

—

Total charges

—

Loading…

Settings

Configure your account and connect your payment processors

Your identity

This is the name attached to webhook payloads and shown on charge receipts. Use your real name or business name — your mentees may see it on bank statements.

Display name

Used on receipts and webhook signatures

Choose your payment processor

ForceCharge supports three processors. Pick the one your customers' cards are already stored in — you can connect more than one. Each processor needs different credentials below.

How to get your Whop credentials

Open your Whop dashboard → Settings → Developer → API Keys. Generate a key with payment scopes enabled. Your Company ID is in the URL of your Whop dashboard.

Whop API Key

Starts with apik_ — leave blank to keep current key

Whop Company ID

Starts with biz_ — found in your Whop dashboard URL

How to get your Stripe Secret Key

Stripe dashboard → Developers → API keys. Use your Secret key (not the publishable one). Customers and saved cards sync via webhook events from your Stripe account.

Stripe Secret Key

Starts with sk_live_ for production or sk_test_ for testing

How to get your Fanbasis credentials

Fanbasis dashboard → Settings → API. The Service ID is for the specific product/service you want to charge against — find it under your service settings.

Fanbasis API Key

Fanbasis Service ID

Starts with svc_

Wire up your webhooks

Webhooks let your processor tell ForceCharge when a customer pays, signs up, or updates their card — so we always have the latest card on file to charge against. Copy these URLs and paste them into your processor's webhook settings.

Whop Customer sync

Whop posts here when a customer pays or their membership changes. This is how cards land in ForceCharge in the first place. Without this URL configured, no Whop customers will appear.

Where to paste: Whop dashboard → Settings → Webhooks → Add endpoint

—

Subscribe to: payment.succeeded, membership.went_valid

Stripe Customer sync

Stripe posts here when a payment succeeds or fails. ForceCharge stores the customer's Payment Method ID so you can charge them again later — without storing the card itself.

Where to paste: Stripe → Developers → Webhooks → Add endpoint

—

Subscribe to: payment_intent.succeeded, payment_intent.payment_failed

Fanbasis Customer sync

Fanbasis posts here whenever a customer's payment lands. ForceCharge stores their billing info so subsequent charges go through automatically.

Where to paste: Fanbasis → Settings → Webhooks

—

Subscribe to: payment.succeeded

Set up your trigger

This is the URL you call from your CRM (GoHighLevel, Zapier, n8n, anywhere) to fire a charge. Send a POST request with the customer's member ID and ForceCharge handles the rest — picking the right processor, retrying if the card fails, logging everything.

Trigger Fire a charge from anywhere

Hit this endpoint with a POST when something happens in your CRM that should trigger a payment (an appointment showed, a lead converted, a service delivered).

Where to paste: GoHighLevel → Workflow → Webhook action · or Zapier · or n8n · or anywhere that can POST

—

POST body must include: whop_member_id + whop_payment_method_id

Admin

Manage mentees and view platform-wide metrics

Total mentees

—

on the platform

Total customers

—

across all mentees

Platform revenue

—

all-time charged

Create mentee account

They'll log in with this email and password

Mentees

Loading…

Edit Customer

—

Customer Name override billing name

Billing Currency used for all charges to this client

Trigger Charge Amount fixed amount billed each time a trigger fires

Credits 1 credit = 1 free trigger (no charge)

credits remaining
card not charged while credits > 0

Quick add:

Client Notes internal only — not shown to client

Tags for filtering & organizing

Trigger

Fire a charge

When this URL is hit (e.g. from a GHL workflow when an appointment status changes), ForceCharge fires the Trigger Charge Amount against this customer's card.

—

Credit

Add 1 free credit

Hit this URL to give the customer 1 free credit. Next trigger doesn't charge — uses the credit instead. Useful for refund-style scenarios or comp'd appointments.

—

B2C Lead

Track a lead arrival

Connect this to your B2C lead source (Meta Ads, quiz funnel, etc). Each hit registers a new lead under this customer so you can track lead volume per client.

—

Status Page

Client-facing dashboard

Share this link with your client so they can view their charge history, credits balance, and current card on file. View-only — they can't change anything.

—

When do you need this? Only if a single client gets billed different amounts for different actions. For example: $50 per shown appointment, $25 per booked call, $100 per closed deal. If you charge one fixed amount per trigger, ignore this section — use the Trigger Charge Amount above instead.

Each price plan gets its own Trigger URL and Credit URL, so you can wire them into different GHL workflows.

FORCECHARGE

Sign in

Welcome to ForceCharge

Dashboard

Customers

Settings

Admin