Skip to content
Tessen
Connections

Connect what you already run.

Six categories of connector, maintained the way the rest of the platform is: versioned, monitored, and covered by the same change log. When a partner moves a field, the log says so before your job fails on it.

74 connectors  ·  6 categories  ·  Reviewed Q1 Partner marks are empty slots — add your own
Catalogue

The whole list, grouped by what it connects to.

Nothing here is a partnership announcement. Each entry is a maintained connector with an owner, a version and a monitor on it. Point at one to see what it carries.

Banking

38

Domestic and cross-border rails. Every one of them lands as the same shape of record.

  • Euro instant credit transferInstant · 24/7Webhook · Idempotent · Return codes
  • Euro batch credit transferBatch · Same dayFile · Cut-off · Retry
  • Euro direct debit, corePull · MandateMandate store · Return codes
  • Euro direct debit, B2BPull · MandateMandate store · No refund window
  • Faster payment railInstant · 24/7Webhook · Idempotent · Limit check
  • Bulk clearing railBatch · Three dayFile · Cut-off · Retry
  • High-value transferSame day · Cut-offFile · Manual approval
  • Domestic direct debitPull · MandateMandate store · Advance notice
  • Automated clearingBatch · Next dayFile · Return codes · Retry
  • Instant settlement railInstant · 24/7Webhook · Idempotent · Request for pay
  • Domestic wireSame day · Cut-offFile · Manual approval
  • Cheque deposit fileBatch · DailyFile · Image reference
  • Batch clearing railBatch · Next dayFile · Return codes
  • Instant railInstant · 24/7Webhook · Idempotent
  • Domestic wireSame day · Cut-offFile · Manual approval
  • Domestic railBatch · Next dayFile · Return codes
  • Domestic railInstant · 24/7Webhook · Idempotent
  • Domestic railBatch · Next dayFile · Return codes
  • Domestic railBatch · Same dayFile · Cut-off
  • QR reference creditBatch · ReferenceFile · Reference match
  • Instant railInstant · 24/7Webhook · Idempotent
  • Batch railBatch · Next dayFile · Retry
  • Domestic railBatch · Same dayFile · Cut-off
  • Instant railInstant · 24/7Webhook · Idempotent
  • Domestic railBatch · Next dayFile · Retry
  • Instant railInstant · 24/7Webhook · Idempotent
  • Batch railBatch · Next dayFile · Cut-off
  • Instant railInstant · 24/7Webhook · Idempotent
  • Batch railBatch · Next dayFile · Return codes
  • Instant railInstant · 24/7Webhook · Idempotent
  • Domestic railBatch · Cut-offFile · Name reference
  • Batch railBatch · Next dayFile · Retry
  • Instant railInstant · 24/7Webhook · Idempotent
  • Batch collection railBatch · ReferenceFile · Reference match · Expiry
  • Domestic railSame day · Cut-offFile · Reference match
  • Domestic railBatch · Same dayFile · Cut-off
  • Domestic railInstant · 24/7Webhook · Idempotent
  • Batch railBatch · Next dayFile · Return codes

Card acquiring

09

Acquiring routes and scheme services. Reason codes survive the whole trip.

  • Tier-1 acquirer routeAuthorize · ClearReason codes · Network token
  • Tier-1 acquirer routeAuthorize · ClearReason codes · Network token
  • Tier-1 acquirer routeAuthorize · ClearReason codes · Retry rule
  • Regional acquirer routeAuthorize · ClearReason codes · Instalments
  • Domestic card schemeAuthorize · LocalReason codes · Local capture
  • Domestic card schemeAuthorize · LocalReason codes · Local capture
  • Scheme authorization serviceReal timeReason codes kept whole
  • Scheme clearing fileBatch · DailyFile · Fee breakdown
  • Network token serviceProvision · UpdateToken lifecycle · Card updater

Wallets and local methods

12

Methods that exist in one market only, held to the same reconciliation rules as the rest.

  • Open banking paymentPush · RedirectConsent record · Status webhook
  • Open banking paymentPush · RedirectConsent record · Status webhook
  • Bank redirect methodPush · RedirectInstant confirmation
  • Nordic bank redirectPush · RedirectInstant confirmation
  • Mobile wallet, South-East AsiaPush · App switchRefund · Status webhook
  • Mobile wallet, East AsiaPush · App switchRefund · Status webhook
  • QR wallet, Latin AmericaPush · QRExpiry · Status webhook
  • Cash voucherPush · OfflineExpiry · Late credit
  • Buy now, pay laterDeferred · CaptureSettlement offset · Refund
  • Buy now, pay laterDeferred · CaptureSettlement offset · Refund
  • Device wallet tokenToken · In appToken lifecycle
  • Prepaid top-upPush · BalanceBalance check · Refund

ERP suites

06

Journals leave in the shape your finance team already agreed on with the auditor.

  • Tier-1 suite, ledger syncPosting · Two wayJournal push · Status pull
  • Mid-market suite, ledger syncPosting · Two wayJournal push · Status pull
  • Cloud suite, posting APIPosting · APIJournal push · Idempotent
  • Manufacturing suite, file exportExport · BatchFixed width · Cut-off
  • Retail suite, daily journalExport · DailyJournal file · Store split
  • Public sector suite, fixed widthExport · BatchFixed width · Period lock

General ledger tools

05

Smaller books, same double entry. The sync runs on your close calendar, not ours.

  • Cloud bookkeeping, journal syncPosting · APIJournal push · Attachment
  • Mid-market accounting, journal syncPosting · APIJournal push · Tax code map
  • Consolidation tool, trial balanceExport · PeriodTrial balance · Entity map
  • Close management, period lockControl · PeriodLock state · Reopen log
  • Spreadsheet template, ledger exportExport · ManualColumn map · Period filter

Warehouses and BI

04

Raw ledger movements land in your warehouse, not a rolled-up copy of them.

  • Columnar warehouse, streamingStream · AppendSchema versioned · Replay
  • Columnar warehouse, batchBatch · NightlyPartitioned · Backfill
  • Lakehouse, columnar exportBatch · FilesPartitioned · Checksum
  • Scheduled extractBatch · ReportPeriod locked · Query stored

A connector that is not on this list is not a refusal. Anything that speaks a file, an API or a message queue can be written against the same interface the maintained ones use, and it reconciles identically.

Getting connected

Four steps from a key to live traffic.

Nobody sits in the middle of this. You issue your own keys, run against a sandbox that returns the failures as well as the happy path, and ask for the switch once your reconciliation agrees with your existing books.

  1. 01

    Issue keys

    Create a key pair in the console, scoped to one connector and one environment. Rotation is yours to run whenever you like, and support never needs to see a key to help you.

    Scoped per connector
  2. 02

    Sandbox

    The sandbox answers with the same message shapes production does, failures included. Decline codes, half-written files and a statement that arrives a day late are all reproducible on demand.

    Replays production shapes
  3. 03

    Verification

    Run a month of your own history through it, then read the difference against the books you already closed. We go through the breaks with you rather than sending a report about them.

    Usually 3 to 5 working days
  4. 04

    Live

    Traffic moves on a date you pick, one connector at a time. The route you were using stays open until you close it, so a rollback is a configuration change rather than an incident.

    Rollback open for 30 days
One connector, in full

Euro instant credit transfer, end to end.

Reference

Every connector in the catalogue is documented to this depth. This one is reproduced here so you can judge that depth without asking for access first.

Connector detail view for a euro instant credit transfer rail
Category
Banking rail
Message standard
ISO 20022
Cut-off
None, 24/7
Median time to settled
Under 10 s
Connector availability
99.98 %
Sandbox coverage
Full, failures included
What this connector supports. Hover a row to rule it across the table.
Capability What it does Guarantee
Webhooks Status changes are pushed as they happen, with the payment reference and the raw response attached. At least once, signed
Settlement files The bank file that closes the day is stored beside the entries it settles, in the format it arrived in. Kept 7 years
Retries A failed delivery backs off and retries on its own schedule; nothing is dropped without an entry saying so. Backoff to 24 h
Idempotency keys Send the same instruction twice and the second one returns the first result rather than a second payment. 72 h window
Reconciliation reference One identifier follows the amount from the instruction to the statement line that clears it. End to end
Version pinning A connector version stays available after a new one ships, so an upgrade is scheduled rather than forced. 12 months notice
Build your own

The same interface our connectors are written against.

Interface

None of the maintained connectors uses a private route. If the system you run is not in the catalogue, you write it against the interface below and it reconciles the same way everything else does.

REST API

Payments, ledger entries and settlement records, versioned by date and never broken in place.

POST /v1/connectors/:id/instructions

Webhooks

Signed events for every state change, replayable from the console for the last thirty days.

connector.instruction.settled

Server SDKs

Thin clients over the same endpoints, with the retry and idempotency rules already wired in.

tessen.connectors.settle(ref)

Sandbox keys

A full environment per key, seeded with your own file formats and the failures you want to test.

sk_sandbox_… scoped per connector
Connector interface reference with an endpoint list and a signed event payload

The connector guide covers the message contract, the retry rules and the reconciliation reference in full. Read it before you talk to us; most of the questions on the first call are answered in it.

Read the connector guide
Next step

Send the list of systems you run.

We will tell you which connectors already cover them, which need a build and roughly what that build costs. It comes back as a list, not a proposal.

No newsletter. One reply from the team that maintains the connectors.