What do I have to keep in mind for authorization simulations with the a Test Acquirer?
The Test Acquirer configured for your terminal may react differently depending on the authorization amount.
For a successful authorization with the Test Acquirer, only whole amounts should be used, for example 5.00. Cent amounts other than .00 will result in a rejection.
If you want to simulate a specific authorization result, you can use the pattern “y1xx” to force authResult 1xx:
Example:
101 -> AuthResult 101: Transaction declined: Card error
102 -> AuthResult 102: Transaction declined: Card expired
103 -> AuthResult 103: Transaction declined: Card unknown
109 -> AuthResult 109: Transaction declined: System error
128 -> AuthResult 128: SCA required (Contactless) or Transaction declined (Contact); SCA=Strong Customer Authentication
130 -> AuthResult 130: SCA required with restart of transaction (Contactless) or Transaction declined (Contact); SCA=Strong Customer Authentication
666[x] -> Error on acquirer, transaction autoreversed. Note that the amount must only start with this pattern, the remaining digits are ignored.
7xx -> Trigger terminal sync in XX minutes after this transaction → only available if VM argument is set "-Dterminal.test.behaviour=true"
8xx -> Trigger terminal initialization in XX minutes after this transaction → only available if VM argument is set "-Dterminal.test.behaviour=true"
997 -> Error on acquirer (unexpected element), transaction autoreversed
998 -> Error on acquirer (incorrect MAC from acquirer), transaction autoreversed
999 -> No response from acquirer, transaction autoreversed
2015 -> AuthResult 15: Confirm approved amount
2016 -> AuthResult 16: Cardholder ID required
2119 -> AuthResult 119, AuthRespCode 06: Use Chip Reader
Behaviour with PIN input (online PIN):
0001 -> PIN wrong, PinRetryCounter = 2
0002 -> PIN wrong, PinRetryCounter = 1
0003 -> PIN wrong, PinRetryCounter = 0, no further pin entries possible
0005 -> PIN wrong, no PinRetryCounter