Payments

/dashboard/payments is where payments taken from callers during phone calls are listed.

This is a different surface from your subscription billing — see Plans & billing for that.

How payments happen

If you've connected Stripe, the agent can take a card payment from a caller during the call. The flow:

1. Caller agrees verbally to be charged.
2. Agent reads back the amount, what it's for, and asks for explicit consent.
3. Agent transfers the caller to a secure payment IVR (Stripe-hosted) where the caller enters their card themselves. The agent never hears or stores the card number.
4. Stripe charges the card and notifies Foan via webhook.
5. The agent comes back on the line to confirm the receipt was sent.

Failed charges are caught — the agent apologises, offers to retry, and logs the failure for follow-up.

Where the money goes

Foan uses Stripe Connect Standard for caller payments. The funds go to your own Stripe account, not Foan's — we just orchestrate. You're the merchant of record; Foan never touches the money.

This is distinct from how affiliate payouts work (see Affiliate program) — those use Stripe Connect Express on Foan's platform account.

What's logged

Each row on this page shows:

• The caller (matched to a Contact where possible)
• The amount + currency
• The Stripe payment intent ID — clickable to open in Stripe
• The agent that took the payment
• Linked call (clicks through to the call detail)
• Status: succeeded / failed / refunded

Refunds

Refund a caller payment from this page — no need to switch to Stripe. The refund reason is logged against the call so the agent has context if the same caller rings back.

Compliance

Card data never touches Foan's systems. The IVR is Stripe-hosted and PCI-DSS Level 1. We log the payment intent ID and amount but never the PAN, expiry, or CVC.

For verbal consent, the agent's confirmation step is recorded into the call transcript — you have a written record of "yes, charge me £49 for the consultation".