Risk signals
Device, velocity and address checks travel with the request instead of running after it.
- Reason code kept
- Issuer response stored
- Retry rule per scheme
Payment infrastructure
Settlement you can read line by line.
Tessen clears card, bank transfer and wallet payments onto one ledger. Every movement carries the record that explains it, so finance and compliance stop reconciling two versions of the same day.
$18.4B
Processed in the trailing twelve months
412M
Cleared across every connected route
99.98%
Authorization availability, rolling 90 days
310ms
Median time to settlement confirmation
SOC 2 Type II · PCI DSS Level 1 · ISO/IEC 27001
Reviewed Q1
Assurance
Every control has a document behind it.
Each control below maps to a named report, a review date and the person who signed it. When an auditor asks for evidence you send a reference, not a description.
Reports are issued by an independent firm and reissued annually. Between issues, any change to a control is published to the change log within a day, with the affected report section listed alongside it.
- 06
- Independent audits completed since 2021
- 24h
- Window to publish a control change
- 00
- Findings open from the last review cycle
REF-SOC-02
SOC 2 Type II
Security, availability and confidentiality. Twelve-month observation window.
REF-PCI-01
PCI DSS Level 1
Cardholder data environment assessed on site by a qualified assessor.
REF-ISO-27001
ISO/IEC 27001
Information security management system, certified scope covers all production regions.
REF-DPA-28
GDPR Article 28
Processor terms, sub-processor register and transfer mechanism published.
Money path
Where a payment goes, and what it leaves behind.
Five stages, one identifier. The same reference follows an amount from the authorization request to the line in your monthly report.
Entry points
Money arrives from six kinds of counterparty, and every one of them has its own file format, its own cutoff and its own idea of what a reference number looks like. Tessen normalises them at the door. After that point a card capture and a bank credit are the same shape of record.
The route
Ledger entry written at every node
Immutable
-
01
Authorize
The request reaches the issuer with the risk signals already attached. A decision comes back with the reason code intact, not flattened into a pass or fail.
Decision returned in 240 ms median -
02
Clear
Captures batch by scheme and currency. Each batch keeps the list of payments inside it, so a disputed amount resolves to a file you can open rather than a total you have to trust.
Batches close on a two-hour cycle -
03
Reconcile
Bank statements match against expected settlement before anyone opens a spreadsheet. Unmatched lines surface with the difference already calculated and the likely cause named.
94% matched without review -
04
Settle
Payouts leave on the schedule you set, split across accounts by rule. Held funds show the rule that held them and the date they release.
Payout windows configurable per entity -
05
Report
Month end reads from the same ledger the payment wrote to. Drill from a summary figure to the individual authorization without leaving the report.
Close in 3 days, down from 11
Checks
A leg is not finished when the money moves. It is finished when the check behind it has run and the result has a place to live. These are the checks, in the order the route meets them.
Batch integrity
Every capture belongs to exactly one batch, and the batch total is the sum of its rows.
- Row count sealed
- Currency split
- Scheme cutoff
Statement matching
Bank credits match expected settlement on amount, date and reference before a human sees them.
- Tolerance per rail
- Break reason named
- Ageing tracked
Payout rules
Splits, holds and reserves are rules with dates, so a held balance always answers why.
- Rule version pinned
- Release date shown
- Entity level limits
Ledger writes
Each movement writes a double entry. Nothing is edited later; corrections are new entries.
- Append only
- Balanced per entry
- Reversal linked
Report lineage
A figure in a report carries the query that produced it, so the drill-down is exact rather than approximate.
- Query stored
- Period locked
- Restatement flagged
What it leaves behind
The part of a payment that survives the payment is the record. Five entries are written on the way through, and none of them can be edited afterwards. This is what an auditor reads a year later.
Authorization record
The issuer's answer is kept whole. A decline that arrived as insufficient funds stays that way in the record, so a support agent six weeks later reads the same reason the terminal did.
Batch seal
When a batch closes it stops accepting rows. The seal keeps the count and the total that were true at that second, which is what makes a later dispute resolvable rather than arguable.
Match result
Matched, partially matched or unmatched, with the tolerance that was applied and the difference in cash terms. An unmatched line names its likely cause rather than waiting for someone to guess it.
Payout instruction
The instruction stores the rule version that produced it. Change the split next quarter and last quarter's payout still explains itself under the rule that was live when it left.
Period close
Closing locks the period and records who locked it. Anything that arrives afterwards becomes a restatement with its own entry, and the original figures stay readable.
On close
Eight stamps are written when a period closes. They are the short answer to the question an auditor opens with, and each one links to the entries that produced it.
CTL-01
Ledger balanced
Debits equal credits for every entry in the period.
CTL-02
Settlement matched
Bank credits reconciled against expected payouts.
CTL-03
Breaks cleared
Open items carried into the next period are listed with an owner.
CTL-04
Holds explained
Every held balance names its rule and release date.
CTL-05
Access reviewed
Who could approve a payout, and when that changed.
CTL-06
Retention held
Entries kept for the term your regulator asks for.
CTL-07
Restatements linked
Corrections point back to the figure they replaced.
CTL-08
Export reproducible
The same period exported twice returns the same file.
Platform
Four systems, one ledger.
Most teams run these as separate tools and spend the month proving they agree. Here they write to the same record, so agreement is the default state rather than the outcome of a reconciliation.
01 Clearing
Capture, batch and dispute in one place
Authorizations, captures and refunds stay linked to the payment that started them. A chargeback opens with the evidence already assembled.
- Scheme and currency aware batching
- Partial capture and multi-refund on one reference
- Dispute packet built from stored authorization data
02 Reconciliation
Statements matched before you look at them
Bank files land, match against expected settlement, and post. What is left is a short list of genuine exceptions with the delta computed.
- Rules for fees, FX spread and rounding
- Exception queue with named causes
- Audit trail on every manual match
03 Treasury
Balances by entity, currency and rule
Funds sit where policy says they should. Sweeps, holds and payout schedules are configuration, so a change is a review rather than a release.
- Multi-entity accounts with segregated balances
- Scheduled and rule-triggered sweeps
- Hold reasons carried through to reporting
04 Reporting
One record from summary to authorization
Close reads from the ledger the payments wrote to. Any figure in the report expands to the entries behind it, down to the original request.
- Scheduled exports in the shape your ERP expects
- Immutable period locks with reopen history
- Drill-down that never leaves the report
Security
Six layers, each with its own failure plan.
A control is only worth the drill that tests it. Each layer below lists what it protects and what happens the day it does not hold.
AES-256 on stored records, TLS 1.3 between every service. Card data never lands in application logs; the tokenizer sits in front of the write path.
Keys live in a hardware module under dual control. Rotation runs quarterly and on demand; every use is logged with the service that requested it.
Each customer holds a separate database schema and its own encryption context. A query cannot reach across tenants even if the application layer is wrong.
Production access is time-boxed and approved by someone who is not the requester. Sessions record what was read, not only who connected.
Anomaly rules watch authorization patterns, payout destinations and administrative actions. Alerts carry the query that produced them so the on-call engineer starts from evidence.
Restores are rehearsed against production-shaped data every quarter, and the timing is published. A drill that is never run is a plan, not a control.
Connections
It already speaks to the systems you run.
Connectors are maintained, versioned and monitored like any other part of the platform. When a partner changes a field, the change log says so before your job fails.
-
Banks and payment institutions
Settlement accounts 38 -
Card networks
Authorization and clearing 09 -
Wallets and local methods
Regional coverage 12 -
ERP suites
Posting and export 06 -
General ledger tools
Journal sync 05 -
Warehouses and BI
Streaming and batch 04
Operating record
Twelve months, measured.
99.98%
Authorization availability across all regions
94.2%
Statement lines matched without human review
3 days
Median month-end close, down from eleven
11 min
Longest unplanned interruption in the period
Plans
Priced on volume, not on seats.
Read across a row to see what changes between plans. Everything listed is included at the stated rate; there is no separate charge for support, sandbox access or the audit reports.
Ledger
No minimum. One entity.
One entity, one record. Clearing, disputes and a daily payout, with the bank leg reconciled for you and the rest left where you can see it.
Start on Ledger
Clearing
From $40k monthly volume.
Scheme and FX legs reconcile alongside the bank file, payouts follow rules instead of a clock, and the record can sit in the EU or the US.
Move to Clearing
Enterprise
Committed volume, annual term.
Custom sources, treasury sweeps, residency you choose and an engineer whose name you know before the first incident.
Talk to the desk| Capability | Ledger 0.28% + $0.14 | Clearing 0.19% + $0.09 | Enterprise Negotiated |
|---|---|---|---|
| Payment clearing and disputes | Included | Included | Included |
| Automated reconciliation | Bank files only | Bank, scheme and FX | Bank, scheme, FX and custom sources |
| Entities and sub-accounts | 1 entity | Up to 12 | Unlimited |
| Payout scheduling | Daily | Rule-based, per entity | Rule-based, with treasury sweeps |
| Data residency choice | — | EU or US | EU, US, APAC or dedicated |
| Audit reports and evidence pack | On request | Included | Included |
| Support response | Next business day | 4 hours | 1 hour, named engineer |
| Sandbox environments | 1 | 3 | Unlimited |
Bank files alone stop being enough the week a second scheme goes live. Ledger will still balance the bank leg and hand you the card leg.
Marketplace · two schemes · sample
Payment clearing and disputes
Disputes arrive on their own schedule. Every plan clears and defends them the same way, so this is not the row where the decision gets made.
Any operator · sample
Any plan
Nothing changes across the columns here.
Automated reconciliation
Bank files alone stop being enough the week a second scheme goes live. Ledger will still balance the bank leg and hand you the card leg.
Marketplace · two schemes · sample
Clearing
The card leg is where the night goes.
Entities and sub-accounts
One legal entity is fine until a second market needs its own books. Ledger caps at one; twelve covers most groups without a custom build.
Group · four markets · sample
Clearing
Past twelve, the desk prices it.
Payout scheduling
A daily payout is predictable and blunt. Rules let a seller in one market get paid on Friday while another waits for the batch to settle.
Marketplace · 40 sellers · sample
Clearing
Sweeps only matter once treasury is involved.
Data residency choice
Residency is a procurement question, not an engineering one. If a customer contract names a region, Ledger cannot sign it.
B2B SaaS · EU contract · sample
Clearing
Dedicated regions are an Enterprise line.
Audit reports and evidence pack
An evidence pack matters the month an auditor asks and not before. On Ledger it is a request with a queue behind it.
Regulated · annual audit · sample
Clearing
Included means you export it yourself.
Support response
Next business day is fine for a question and wrong for a stuck settlement file. Four hours covers a working day; an hour with a named engineer covers a launch.
Launch week · 24h cover · sample
Enterprise
This is the row that moves teams up.
Sandbox environments
One sandbox works until two teams need to break it on the same afternoon. Three is usually where that stops being a scheduling problem.
Platform · three teams · sample
Clearing
Unlimited is rarely the reason anyone moves.
Enterprise
Negotiated is not a hidden tier. Send us a month of settlement volume and the rails you run on, and we price against those instead of a bracket. Committed volume, an annual term, an engineer with a name.
sales@tessen.example
Questions
What buyers ask before the first call.
Six to ten weeks for a single entity, longer where historical balances need to be carried across. The first two weeks run in parallel with your existing processor so you can compare both ledgers on live traffic before switching.
You choose the region at account creation and it does not move afterwards. Backups stay in the same region. Sub-processors and their locations are listed in the processor register, which is versioned and dated.
You export the full ledger in the same format the reporting API returns, including the authorization detail behind every entry. Export stays available for ninety days after termination, then the data is destroyed and a certificate is issued.
Authorization fails over between regions without operator action. Clearing and reporting queue and replay in order, so nothing is lost and nothing is double-posted. Incident notes are published with a timeline rather than a summary.
Yes. Tessen routes to acquirers you already hold contracts with and reconciles their settlement files alongside its own. Several customers run it purely as the ledger layer over existing processing relationships.
Scheme and interchange costs pass through at cost with the breakdown attached to each settlement. Everything Tessen charges for is in the table above. Implementation is quoted once, before the contract, and does not change after signature.
Next step
See it against your own volume.
Send a month of settlement files and we will run them through a sandbox ledger before the call. You get the reconciliation result either way, whether or not you go further.