Skip to content
Insights

Plain-English guides for the people who run a payment ISO.

Reading a merchant’s statement, pricing a quote, residuals and month-end, boarding across acquirers, PCI revenue — and what changed on the platform. Written by the people who built Valtura, from running an ISO.

Platform update

Why we built Valtura: from a Plymouth ISO to a platform company

Valtura was built by an ISO that was tired of pricing merchants on a calculator. This is how a Plymouth payments business ended up building the platform it wished it could buy.

Sebastian Wood
Guide

ISO residuals explained: where the money comes from, why it leaks, and what month-end looks like on one system

Residuals are the reason an ISO is worth building, and the month-end spreadsheet is where some of them go missing. Here is how the money flows and what the month end looks like when it runs on one system.

Valtura
Guide

How to read a merchant’s card-processing statement in three minutes — and why it takes an hour by hand

Every quote starts with someone reading a statement. Here is where the hour goes, what the platform puts on screen instead, and why the same reading every time matters to the acquirers you board with.

Valtura
Announcement

Valtura Platform is open to UK ISOs: one system from the merchant’s statement to the commission run

We built Valtura because running our own ISO on spreadsheets, calculators and inboxes was costing us deals. It now runs the whole business, and from today any UK ISO can run theirs on it too.

Sebastian Wood

Reading about it is the slow way to find out.

Thirty days, no card, nothing to install. Import demo data, then take a real statement all the way to an accepted proposal.

Start your 30-day trial Book a guided demo