RATE THIS ANSWER
+1
Click to Vote:
- 1
0
Your test data strategy or rather plan would comprise of:
1. Accepting Valid Card number
2. Accepting right number of digits (not less or more)
3. Validation of user and password
4. giving appropriate number of chances for user ID and password in case it fails for the first time
5. raising right alarm in case of any misappropriate login trials
6. Doing the right action as per customer requirement
7. updating the tables according to the transaction taken place
8. capturing the correct transaction date from server (and not ATM)
9. storing the transaction date for audit trail or postmortem of any transaction
10. producing the right results as per transaction
11. speed of transaction/query
12. closing of transaction and appropriate logout after customer exits from the screen
Software testing and Quality Assurance (QA), Software testing, Integration testing
I am working on system integration testing for a credit card system. Do you have any test data strategy for system integration testing based on transaction flows? 
