Payment depth over generic abstraction
IsoTran is shaped around ISO 8583, issuer processing, transaction state, EMV, payment cryptography, remote hosts, and the realities of test-system integration.
Purpose-built payment testing
Built from the realities of engineering and testing payment systems.
IsoTran was created to give payment teams a focused platform for complex transaction simulation, automation, load testing, EMV, cryptography, observability, and evidence—without forcing those workflows into unrelated generic tools.
THE ISOTRAN PURPOSE
Make sophisticated payment testing easier to configure, repeat, observe, and explain.
Enterprise Payment Testing
Why IsoTran exists
Payment testing is specialized work. The platform should reflect that.
ISO 8583 interfaces are shaped by message formats, network rules, card and device data, cryptographic state, EMV application behavior, connection management, transaction chains, and host-specific responses. Performance testing adds concurrency, pacing, endpoint coordination, failure handling, live telemetry, and evidence.
Those concerns are often divided across message editors, scripts, load tools, spreadsheets, log viewers, and individual expertise. IsoTran brings them into one coherent product.
- Built specifically for authorized payment-system testing
- Designed for issuer, processor, network, gateway, and certification workflows
- Intended to support both individual investigation and enterprise test operations
- Developed as an on-premises product for customer-controlled environments
ISO 8583EMVCryptographyLoadAutomationEvidence
Product principles
The decisions behind the platform
IsoTran is developed around a small set of practical principles that guide its architecture and workflow.
A complete workflow over disconnected utilities
Configuration, execution, observation, and evidence belong together. A test result is easier to trust when its context is preserved.
Customer control over public dependency
Payment test data and connectivity often belong inside the customer environment. IsoTran is designed around that operating boundary.
Repeatability over operator memory
Reusable profiles, plans, sessions, schedules, traces, and comparisons turn specialized knowledge into a durable testing capability.
JB
FOUNDER & DEVELOPER
Jerimiah Barsalou
Payments systems engineer and software developer
Experience translated into product
Designed by a payment engineer for payment engineers.
Jerimiah Barsalou has worked across payment-system development, integration, testing, support, and consulting. IsoTran translates that hands-on experience into a modern application that treats transaction data, host behavior, payment security, high-volume execution, and test evidence as parts of the same engineering problem.
The product continues to evolve around practical customer workflows: making sophisticated tests easier to build, allowing teams to share and repeat them, and improving the visibility available during and after execution.
Payment-domain engineering Product development Customer implementation Performance testing
RESPONSIBLE USE
Deployment model Built for authorized test environments.
IsoTran is intended for legitimate development, integration, certification, quality, and performance testing. Customers are responsible for authorizing endpoints, governing test data and keys, controlling access, and operating the platform within applicable policies and agreements.
Talk directly with the product team
Discuss your payment-testing environment with the person building IsoTran.
Product, implementation, consulting, partnership, and technical discussions can begin with a focused conversation.