Online
Forms and checkout
Amounts, line items, contacts and business context remain aligned before calling the provider.
Payments and CRM
Connect collection to accounting reality
HelloAsso, SumUp, Stripe and other providers become useful when their state remains coherent with contacts, contributions and receipts.
Journeys
More than a payment button
The journey covers contribution creation, authorisation, return, webhook processing and reconciliation.
In person
Terminal and point of sale
On-site payment connected to the correct person, activity and contribution.
After payment
Webhook and reconciliation
Replay without duplication, identify delays and separate abandonment from real failure.
Principle
The browser does not keep the books
The result visible to the user must be confirmed by persisted data and provider events.
Authority
An explicit source of truth
CiviCRM retains business state; the provider attests financial state.
Idempotency
Handle repetition
Returns and webhooks may arrive repeatedly or in an unexpected order.
Evidence
Explain every state
Transactions, logs and identifiers must support controlled recovery.
Incident or project
Start with one specific payment
One contribution, one transaction identifier and a timeline are often enough for the first diagnosis.