Kobana

Connected to the Kobana rail — or running independently

OAuth2 and Kobana webhooks for real-time confirmed payments, the email and SMS providers you already use, and a standalone mode with payment signals from PSPs, CNAB files and manual reconciliation.

Integrations
Outbound webhooks with signed deliveries — success and failure with retry
2
operating modes (Kobana rail and standalone)
3+3
email and SMS providers
4
payment event sources
100%
webhooks deduplicated by idempotency

Your operation connected in four steps

1

Sign in with your Kobana account

Identity runs on Kobana OAuth2. The banking gateway is optional.

2

Connect the channels

Email via SendGrid, Mailgun or SES; SMS via Twilio, Zenvia or Infobip. WhatsApp fits within the channel structure.

3

Choose the payment source

Real-time Kobana webhooks, PSP signals, a CNAB file, or manual reconciliation.

4

Track the logs

Every integration request and webhook is recorded, with a test ping and reconfiguration from the dashboard.

From the Kobana gateway to the provider you already use

Kobana Rail
With the Kobana gateway, payment is confirmed in real time via a signed webhook — and the dunning flow stops at that exact instant.
  • Verified HMAC signature
  • Idempotent inbox: redelivery doesn't duplicate
  • Customer and charge synchronization
Standalone Mode
Without a gateway, the product runs on payment signals from other sources, each with evidence and a confidence level.
  • PSP, CNAB or manual reconciliation
  • High, medium or low confidence per signal
  • Same engine, same guarantees
Email Providers
SendGrid, Mailgun and Amazon SES ready to connect. You use the sending reputation you've already built.
  • Configuration per account
  • Delivery status via the provider's webhook
  • Customizable email layouts
SMS Providers
Twilio, Zenvia and Infobip integrated for short messages with a payment link.
  • Cost recorded per send
  • Provider ID on every message
  • A blocked channel becomes an automatic suppression
Inbound and Outbound Webhooks
An idempotent inbox to receive events; signed outbound endpoints to notify your system.
  • Unique idempotency key per delivery
  • Reprocessable failures, nothing gets lost
  • Secret rotation on outbound endpoints
Integration Logs
Requests and webhooks recorded with direction and status. Test ping and reconfiguration without leaving the dashboard.
  • Fast failure diagnosis
  • History queryable via the API
  • Guided setup for the Kobana integration

Real use cases

ERP + Kobana rail

The ERP issues invoices via Kobana; Dunning receives the payment webhook in real time and stops the flow the second the money lands.

Portfolio held at another bank

No gateway: the daily CNAB return generates high-confidence payment events, and the flow stops for the settled invoices.

Email with your own reputation

Your company already sends through SendGrid. Connect the account and the dunning-flow messages go out from your own domain, with delivery status feeding the telemetry.

Imports of customers and invoices with a rejected-rows report

Standalone mode: portfolio import with a rejected-rows report.

Data exports with filters and expiration

Data export with filters and expiration — ready for your ERP or BI.

Frequently asked questions

Connect your operation in minutes

See the Kobana integration setup, the sending channels and standalone mode in action.