Proof you can explain — end to end
Reccurs produces an end-to-end trace you can actually follow: what happened, what was recorded, which rule applied, and why the state changed.
Audit timeline fragment
Illustrative example| Time | Source | Event | Ledger | State | Why |
|---|---|---|---|---|---|
| 10:02 | provider | invoice.created | recorded | draft → invoiced | Rule applied (v1) |
| 10:04 | provider | invoice.paid | recorded | invoiced → paid | Matched as expected |
| 10:05 | provider | refund.processed | recorded | paid → refunded | Rule applied (v1) |
| 10:06 | provider | invoice.paid | ignored — duplicate event | refunded → exception | ExceptionDuplicate event ignored |
This is how non-happy-path billing stays explainable.
Capabilities in operational order
Designed for finance and ops ownership: explicit rules, deterministic outcomes, and clear exceptions—without hiding history.
Normalize provider events
Convert provider-specific webhooks into a canonical lifecycle record you can reason about across providers and time.
Mapping snippet
View mapping example
Inputs are mapped into a stable event model so finance and engineering can share one lifecycle language.
Record immutable ledger entries
Write append-only entries that preserve history and support independent audit review.
Ledger entry (example)
See the rule
Reccurs avoids edits-in-place; corrections are new entries linked to the original decision.
Reconcile with explicit rules
Match lifecycle expectations against provider reality and label the result clearly every time.
Reconciliation status
View matching logic
Reconciliation is deterministic: each status is produced by an explicit, reviewable rule.
Explain every change
Each state transition includes a reason, a source, and a rule reference — so every change is explainable after the fact.
State transition
View rule reference
Every decision records which rule version applied so changes remain explainable over time.
Surface exceptions clearly
An exception queue designed for owners — finance, ops, and engineering: what broke, why it matters, and what to do next.
Exception queue (example)
View workflow
Exceptions carry reason codes and ownership so the team can resolve with context, not guesswork.
Controls are product features
Because correctness, auditability, and recovery are core product behavior — not afterthoughts.
Audit trail
Every lifecycle change is traceable to an event, a rule, and a recorded outcome — even after the fact.
Immutability by default
History is preserved; corrections are explicit and reviewable.
Idempotency and duplicates
Duplicate events are handled deterministically and recorded as such — no hidden side effects.
Versioned reconciliation rules
Rules are explicit, versioned, and referenced by every decision — past and present.
Execution boundary and verification
Payment execution is handled through integrated providers. Reccurs records, explains, and reconciles what occurred — even when outcomes are delayed or out of order. KYC/verification is required for payment services, and requirements may vary by country, entity type, and channel.
Scope clarity
Reccurs does not replace your payment processor. It gives your team ownership of lifecycle visibility, reconciliation, and operational controls around recurring revenue.
How it works
Events may arrive delayed, duplicated, or out of order — the system is built to handle that.
Connect
Receive billing lifecycle events from integrated providers and your internal systems — as they happen.
›Integration details
Events may arrive delayed, duplicated, or out of order. Integrations should assume asynchronous delivery and behave idempotently.
Normalize
Convert raw events into a canonical lifecycle record you can reason about.
›Normalization rules
Mappings are explicit so the lifecycle remains stable even when providers vary in naming and timing.
Record
Write immutable ledger entries and state transitions — no edits in place.
›Ledger behavior
Append-only recording supports audit review and controlled change without rewriting history.
Reconcile
Compare expected vs observed outcomes and assign a clear, deterministic status.
›Matching logic
Reconciliation is deterministic and produces reason codes for exceptions, not ambiguous errors.
Operate
Work exceptions with clear ownership, notes, and an audit trail.
›Exception workflow
Teams can triage, resolve, and leave context for future reviews and close processes.
What you gain
Outcomes you can rely on when billing doesn’t go as planned.
- Explainable states: every status has a reason, a source, and a trace — no guesswork.
- Clarity: a lifecycle you can explain without spreadsheets or ad-hoc investigations.
- Controlled operations: changes are reviewable, auditable, and never hidden.
- Finance–engineering alignment: a shared model, deterministic outcomes, and fewer ambiguous investigations.
- Fewer manual checks: automation where rules are clear, exceptions where they are not.
Designed for teams that need to explain outcomes — not just produce them.
Request access
This is a private beta. We’ll follow up with onboarding steps and integration requirements if there’s a good fit.
FAQs
Are events processed in real time?+
No. Events may arrive delayed, duplicated, or out of order; Reccurs is built to handle these conditions explicitly and record outcomes deterministically.
What happens if provider events arrive out of order or are duplicated?+
Reccurs applies explicit, versioned rules to normalize, record, and reconcile events. Duplicate or late events are handled deterministically and recorded as such.
Does Reccurs replace my payment processor?+
No. Reccurs does not execute payments; it provides lifecycle visibility, reconciliation, and operational controls around recurring revenue.
Do you guarantee outcomes or uptime?+
No. Reccurs avoids guarantees that depend on multiple systems, and focuses on explainability, auditability, and controlled operations when things don’t go as planned.
Is verification or KYC required?+
Yes. Verification is required to use payment services, and requirements may vary by country, entity type, and channel.
Is this available to everyone?+
No. Reccurs is currently in a private beta, and access is granted to a limited number of teams to ensure fit and correctness during onboarding.
Explain outcomes. Operate with control.