Traffic policy
Configure target TPS, ramp-up time, duration or transaction count, amount behavior, and plan-specific execution inputs.
Performance & load testing
Generate controlled payment traffic. Measure what the host actually does.
IsoTran combines reusable payment configuration, load orchestration, host coordination, and live operational telemetry so performance tests remain realistic, observable, and repeatable.
LIVE LOAD SESSIONCoordinated batch / 3 plans
TrafficRampingtoward policy
HostsReadyleased to batch
ResponsesTrackedoutcome + timing
TARGET POLICY
Actual TPS Target
The testing problem
A transaction generator alone cannot explain system performance.
Useful load testing requires controlled traffic, realistic message variation, endpoint coordination, connection awareness, live telemetry, and evidence that survives after the run. IsoTran brings those functions into the same workflow.
- Build traffic from payment-domain profiles instead of static payloads
- Coordinate work around actual remote-host availability
- Separate target rate from measured throughput
- Retain enough detail to investigate abnormal outcomes and compare runs
Controlled by design
Define the workload and the operating policy
Load Plans describe what to generate; the Load Processor coordinates how those plans execute.
Coordinated batches
Submit multiple Load Plans together and coordinate their start after every required remote host is ready.
Connection resilience
Control host connection, retries, reconnect attempts, availability, and remote-host ownership during execution.
Live telemetry
Observe active and queued work, transmitted and response counts, actual TPS, latency, approvals, declines, and lost traffic.
Retained sessions
Preserve execution details, plan context, metrics, status, errors, and trace evidence after the load completes.
Run comparison
Compare completed sessions to identify changes in throughput, response time, response quality, and behavior.
QUEUED BATCH
AAuthorization mixHost 1
BEMV workloadHost 2
CReversal flowHost 3
Wait for every host
COORDINATED START
All plans execute as one batch
Multi-host coordination
Start the test together—not whenever each plan happens to connect.
When multiple Load Plans are submitted as a batch, IsoTran can hold the batch until every required remote host is available. This supports more meaningful end-to-end tests where participating workloads need a common start point.
- Remote-host use coordinated across operators and workspaces
- Queued state and wait reason visible to the operator
- Batch membership retained with the resulting processes and sessions
- Individual process termination and error handling remain controlled
A measurable operating cycle
From workload definition to comparative evidence
Keep the test objective, execution policy, live system behavior, and final result connected.
Define
Target host, transaction mix, card and device populations, rate, ramp, duration, and retry policy.
Coordinate
Queue individual plans or synchronized batches until the required endpoint capacity is available.
Generate
Create varied transactions from reusable profiles while controlling pace and connection behavior.
Measure
Track throughput, response timing, outcomes, loss, warnings, and execution status in real time.
Compare
Use retained sessions and metrics to establish baselines and evaluate change.
Baseline and compare
Understand how the result changed—not only whether the run finished.
Retained Load Sessions support investigation and side-by-side analysis across selected runs. Use the comparison workflow to make performance conversations more concrete.
- Actual throughput and volume
- Average and time-series response latency
- Response, approval, decline, lost, and late behavior
- Plan, host, duration, timing, warnings, and completion context
IsoTran reports observed test behavior; interpretation of production capacity and release readiness remains the responsibility of the testing organization.
LOAD COMPARE
BaselineCandidate
Throughput
Response time
Response quality
Baseline session Candidate session
Make performance testing explainable
Design a load test around your actual interface and transaction mix.
Discuss target endpoints, connection rules, traffic composition, ramp policy, evidence requirements, and how results should be compared.