01
Define the scenario
Compose transactions into a Script Plan using shared host, card, device, message, and security profiles.
Functional & regression testing
Turn payment scenarios into repeatable test evidence.
IsoTran Script Plans and Script Sessions help teams move beyond one-off message sending. Build a controlled transaction sequence, execute it interactively or by schedule, and retain the details needed to understand and approve the result.
Network sign-on0810 · matchedComplete
Purchase approval0210 · response 00Complete
Purchase reversal0400 · awaiting responseRunning
04Balance inquiryQueued transactionReady
The testing problem
Manual transaction checks are difficult to repeat, review, and scale.
When the transaction definition lives in one place, operator notes in another, and evidence in log files, regression coverage becomes dependent on individual knowledge. IsoTran keeps the scenario, execution state, response data, and trace context together.
- Reuse the same test assets across releases and environments
- Preserve the exact session state for later review
- Rerun individual transactions without recreating the workflow
- Separate configuration, operation, viewing, and approval responsibilities
Session-based automation
A controlled path from scenario to proof
The operator remains in control while IsoTran captures the repeatable structure and execution detail.
02
Control execution
Start, pause, resume, stop, or rerun the script or an individual transaction while preserving session context.
03
Capture outcomes
Record response code, response time, timestamp, STAN, trace details, errors, and operator comments against each step.
04
Review the evidence
Return to the retained Script Session to complete review, repeat selected steps, and support approval.
SESSION SUMMARYIssuer Regression / Build Candidate
COMPLETETransactionsCaptured
ResponsesCorrelated
CommentsRetained
Selected transaction
Purchase reversalRequest, response, timing, STAN, timestamp, validation, and operator notes
Evidence stays with the work
Review more than a pass or fail.
Each session can retain the transaction-level information needed to investigate behavior, explain exceptions, and support an internal completion process.
- Response code and selected response data
- Response time and transaction timestamp
- STAN and other execution identifiers
- Error output and operator comments
- Trace context for request and response
- Ability to rerun and update the transaction result
Broad transaction coverage
Model the scenarios that matter to your interface.
Script Plans can combine payment and network-management transactions using the same configuration model as IsoTran’s interactive and load-testing workspaces.
Explore platform configuration01Authorization approval and decline paths
02Reversal, advice, completion, and timeout handling
03Network sign-on, echo, and key-exchange sequences
04EMV response and issuer-authentication behavior
05Message-format and field-mapping regression
06Host migration and release validation
Make regression testing repeatable
Build a functional test workflow around your real payment messages.
A demonstration can use representative transaction sequences and show how IsoTran captures execution status and evidence.