Question 1

How is my balance calculated?

Accepted Answer

Your balance is the credit count after every recorded transaction. Each transaction snapshots balance_after and held_after on the row itself, so the balance you see is the balance after the most recent write rather than a re-derivation across history. The balance excludes held credits — those sit in held_total until a hold captures or releases. The balance is non-negative by Postgres CHECK constraint, so any path that would drive it below zero fails before the row is written.

Question 2

What does "on hold" mean to me?

Accepted Answer

A hold is credits reserved by a service that has started but not finished. A consult that just began. A records-access session that is open. The credits have moved from your balance column into your held_total column atomically; once the service ends, the hold either captures (the credits become a real debit at the actual amount) or releases (the credits return to your balance). The default hold lifetime is ten minutes; the longest possible hold is twenty-four hours, enforced by the handler before the database is touched.

Question 3

What if I refresh during checkout?

Accepted Answer

Nothing happens twice. The Paystack reference is unique to the initialisation; a refresh during checkout either reaches the verify path with the same reference and resolves to the existing transaction, or never starts a second transaction at all. The unique index on (account_id, reference) is the safety net underneath. The verify endpoint double-checks the webhook so a dropped packet cannot leave you charged without credits, and the webhook is itself idempotent on the same reference.

Question 4

How do refunds work?

Accepted Answer

Only debits can be refunded. The refund inserts a row of type=refund with reference refund:{originalTxID}, the related_tx_id pointing at the original debit, and the amount returned to your balance. The refund is itself idempotent on the refund:{txID} reference, so a duplicate refund attempt resolves to the existing refund rather than a second credit. Refunds appear in your transaction feed under the Refund label with a positive sign and the source service that issued them.

Question 5

How long is a consult hold?

Accepted Answer

Doorcta sets the hold duration based on the consult length plus a small buffer; the FastCredits handler caps every hold at twenty-four hours regardless. If a consult overruns, Doorcta places a follow-up hold rather than letting the original drift; if the consult ends inside the original window, Doorcta captures the hold immediately. The expirer worker is the safety net for the case where Doorcta crashes mid-consult: it sweeps any active hold whose deadline has passed and releases it.

Question 6

What happens if I revoke a OneHealth grant mid-session?

Accepted Answer

The session ends. The cascade releases the FastCredits hold the provider placed at session start; the credits return to your balance. The audit chain on the OneHealth side records the revoke, the session-end event, and the released hold; the FastCredits ledger records the release transaction with reference release:{originalRef}. The provider can request a new grant; you can deny it. There is no quiet way for a session to keep reading after the grant is gone, and no quiet way for credits to stay held after the session has ended.

Question 7

How is my email used?

Accepted Answer

Paystack uses your email to send you a receipt for every successful top-up. We pass the email to Paystack on the initialise call as the receipt destination. We do not use it for marketing; we do not relay it to third parties beyond Paystack itself. The data-processing record names every dataset and every processor; the Paystack-receipt path is the only outbound use of your email from FastCredits.

Question 8

Can I see who debited which credits?

Accepted Answer

Yes. Every transaction carries a source_service column that names the product that drove the debit (doorcta, onehealth, future product slugs as they ship). The dashboard transaction feed surfaces a via {service} subline next to every row. Combined with the timestamp, the amount, and the reference grammar, the feed gives you a per-credit answer to who debited what and when. The relative-time formatter labels recent rows (Just now, {N}m ago, {N}h ago, {N}d ago) before localising older dates.

Question 9

Do my credits expire?

Accepted Answer

No. Credits do not expire. Your balance is yours until you spend it on a Fastclinic product or until the underlying account is closed and the residual balance is reconciled per the published account-closure policy. The audit-chain retention period is seven years from each transaction, but that is record retention, not credit expiry — your spendable balance is unaffected. Account closure routes residual balance back through the same Paystack rail it came in on, against the same reference grammar, so the closure path is itself idempotent against retried calls and resilient against partial failures.

Question 10

What happens to credits if I delete my Fastclinic account?

Accepted Answer

Account deletion follows NDPA 2023 §35 erasure semantics. The residual balance is reconciled before the account is closed; the credits move out of the ledger through a deterministic reference (closure:{accountID}) that the unique-index design dedupes. After reconciliation, the account row is marked active=false, the cached balance is invalidated, and the audit chain records the closure event. The transaction history is retained for the seven-year audit window to satisfy the records-of-processing obligation; the deletion path destroys forward access without destroying the historical record of past transactions.

One balance. Every Fastclinic service.

1 · Your balance, one place

2 · Buy credits

3 · Paystack checkout

4 · Credits land

5 · Spend on a Doorcta consult

6 · Spend on a OneHealth grant

7 · Auto top-up — coming 2026

One balance across every Fastclinic product

Idempotent payments by design

Paystack receipts in your inbox

Holds that release automatically

Capabilities

Integrations

Compliance & safety

Plain answers

Top up once. Spend everywhere.

One balance. Every Fastclinic service.

1 · Your balance, one place

2 · Buy credits

3 · Paystack checkout

4 · Credits land

5 · Spend on a Doorcta consult

6 · Spend on a OneHealth grant

7 · Auto top-up — coming 2026

One balance across every Fastclinic product

Idempotent payments by design

Paystack receipts in your inbox

Holds that release automatically

Capabilities

Integrations

Compliance & safety

Plain answers

01How is my balance calculated?

02What does "on hold" mean to me?

03What if I refresh during checkout?

04How do refunds work?

05How long is a consult hold?

06What happens if I revoke a OneHealth grant mid-session?

07How is my email used?

08Can I see who debited which credits?

09Do my credits expire?

10What happens to credits if I delete my Fastclinic account?

Top up once. Spend everywhere.