Kobana

Every charge with an explicit state, tracked origin and complete history

Amounts with interest, fines and discounts, a state machine that rejects invalid transitions and a direct link to the workflow. From Kobana, your ERP, the API, a spreadsheet or manual entry — all in the same portfolio.

Dunning
Charges list with status, due date and updated amounts
8
possible charge statuses
5
supported charge origins
4
payment event sources
100%
transitions validated in code

From charge entry to write-off, with the workflow reacting on its own

1

Bring in the charges

Sync from Kobana, integrate via API, import a spreadsheet or register manually. The origin is recorded on every charge.

2

Link to the workflow

The charge enters the current version of the workflow and its steps start to apply.

3

Track the state

Pending, overdue, in negotiation, paid, protested, negativated, written off or canceled — with the status "age" visible.

4

Let the events do the work

Payments, refunds and disputes change the state instantly and the workflow reacts on its own.

A portfolio that leaves no charge in doubt

Full Amounts
Original amount, interest, fines and discount make up the updated amount used in messages and the portal.
  • Updated amount in template variables
  • Partial payment updates future messages
  • Agreement simulation over the current amount
Explicit State Machine
Invalid transitions are rejected in code: you can't reopen a charge written off by mistake or suppress a message already sent.
  • 8 statuses with transition rules
  • Audited change history
  • Status "age": when it was last checked
Tracked Origin
Every charge carries its origin: Kobana, ERP, API, spreadsheet or manual. You know exactly where every charge in the portfolio came from.
  • Filters by origin and status
  • Continuous sync on the Kobana rail
  • Idempotent import — no duplicate charges
Multi-source Payment Events
Payment confirmed by Kobana webhook, PSP, CNAB file or manual write-off — every event with evidence and a confidence level.
  • High, medium or low confidence by source
  • Evidence attached to the event
  • Foundation of standalone mode, no gateway required
Immediate Interruption
Payment ends the workflow and suppresses pending sends. A refund reopens and re-enrolls. Partial payment cancels messages with a stale amount.
  • Pre-send revalidation inside the worker
  • Tested under race conditions
  • Never bill someone who just paid
Automatic Updates
Daily jobs check due dates and update status. Reconciliation every 10 minutes fixes divergences between state and queue.
  • Overdue flagged on the right day
  • Reprocessing queue for failures
  • Honest activity report on the dashboard
Charge detail with history, workflow telemetry and payment events

Charge detail: audited history, workflow telemetry and payment events with evidence.

Real use cases

Mixed portfolio

Charges from the Kobana gateway and bills issued by the ERP in the same workflow, with filters by origin and status for day-to-day operations.

Write-off via CNAB

Without an integrated gateway, the bank's CNAB return file generates high-confidence payment events — and the workflow stops instantly for settled charges.

Payment refund

A card chargeback comes in: the charge reopens automatically and re-enters the current version of the workflow, with no manual work.

Frequently asked questions

Bring in your portfolio and watch the workflow take over

A demo with charges from multiple origins, payment events and the workflow reacting in real time.