Banking Gateway integration (Kobana)

System > Integrations > Kobana (/settings/integrations/kobana). The integration lets you:

1. Send payments to the bank — dispatch authorized payables, one bill at a time or in batch.
2. Sync bank accounts — between Kobana and Smart Finance.
3. Sync the statement — pull in the transactions of the linked accounts.
4. Settle automatically — once the payment is confirmed, the bill is settled and the transaction created. This depends on the bill having "Pay from" set: without knowing which account the money left, the system won't guess, and the settlement is left for you to do by hand.

Connecting

The strip at the top shows the Status — Connected, Not connected or Connection error — and the token.

With no connection, the button is "Connect": paste the API token generated in your Kobana panel. "The token is stored encrypted." The system validates it and reports how many accounts are visible.

Once connected, the button becomes "Manage connection".

"Disconnect" isn't on the page. It lives inside the "Manage Kobana connection" dialog, next to "Update". The confirmation is reassuring: "Only the connection is removed. Accounts and data already synced stay in Kobana Finance."

Syncs

note

Both syncs require a specific company in the header selector: "Select a specific company in the header selector, not 'All companies'. Synced accounts land in the company you choose."

Bank accounts

There's no listing for linking accounts by hand. There's one button — "Sync bank accounts" — that does the whole job and links them for you.

warning

This sync is two-way and it WRITES to Kobana. The card carries the "Two-way" badge, and that isn't decoration: as well as importing the accounts registered in Kobana, it creates in Kobana the accounts that only exist here. That's why there's a mandatory confirmation, and it spells out the stakes: "Creating accounts in Kobana changes the external system."

It's the only operation in the integration that modifies the external system without being a payment. If all you want is to pull the accounts from there, know that the return trip happens along with it.

Statement

"Sync statement" "Import the statement of linked accounts (in the selected company): pulls Kobana transactions into Kobana Finance, without duplicating the ones already imported."

There's a single button and it covers every linked account in the company — there's no per-account button. The imported lines feed Reconciliation.

Payment authorization

When authorization is on (the workspace default), a bill created through the form, through CSV or through the API is not available for sending until a person authorizes it in Authorize payments. With authorization off, the bill is born official and ready to send. See Lifecycle.

Sending payments

With the integration active and the bill authorized, use "Send to the bank" — a manual action, on the detail screen. From the listing, the route is "Send payments", which dispatches in batch. See Sending to the bank.

Automatic sync

note

This section only appears if the server has a public webhook address configured. Without one there's no way for the gateway to notify anything, and neither this section nor the two that follow are drawn.

A single switch: "Keeps dispatched payments' status up to date on its own, without clicking 'Refresh status'."

It's optional, and switching it off doesn't leave you in the dark — you just have to fetch the status by hand, through each bill's "Refresh status".

Notifications

Another switch: "Get an alert in the bell when a payment's status changes (confirmed, scheduled, rejected…)."

The two switches talk to each other: without automatic sync on, "alerts may arrive late" — the bell only rings once the system finds out about the change.

Webhook deliveries

A diagnostics table: "A log of each status-change event the Kobana payment gateway sends. If one fails, you can resend it." It has "Refresh" and, per row, the resend.

This is where to look when a payment seems stuck: if the event never arrived, the status here is running behind the bank.

This table only exists with automatic sync on. It's automatic sync that makes the gateway send the events — switched off, there's no delivery to log, and the section disappears from the page.

History

A log of the syncs that have run, by Date, Type (Accounts or Statement) and Result — with how many were created, updated, pushed or skipped.