Skip to main content

Transaction Emulator

Overview

The Stitch platform includes a transaction emulator designed for development and testing purposes. This emulator allows you to simulate various transaction scenarios without processing actual payments.

Testing Methodology

Basic Response Code Testing

The emulator uses a simple but effective method to generate different response codes based on the transaction amount:

  • The decimal portion of the amount determines the response code
  • For example: A sale amount of R10.51 will return response code 51 (insufficient funds)
  • To get an approved transaction, use a whole number amount (e.g., R10.00)
  • If no description exists for a specific code (e.g., 06), an error will be returned
note

PIN validation is performed before applying other rules. See the Test Cards section for valid PINs.

Special Testing Scenarios

Single Tap & PIN Testing (50.05)

To test the Single Tap & PIN flow:

  • Use the exact amount R50.05 with the single tap & PIN indicator set
  • Without a PIN: Returns response code 65 (exceeds withdrawal/frequency limit, request PIN)
  • With a valid PIN: Returns 00 (approved)

Fall-Forward Testing (.65)

To test the fall-forward scenario (chip transaction after contactless decline):

  • Use a chip entry mode with an amount ending in .65 (e.g., R10.65)
  • Returns response code 00 (approved) instead of 65
  • This simulates a successful chip transaction after a contactless transaction was declined

Timeout Simulation (.69)

To simulate a transaction timeout:

  • Use any amount with decimal value .69 (e.g., R10.69)
  • The emulator will not send a response
  • After approximately 30 seconds, the Stitch platform will return a failed result with code N0 (acquirer transaction timed out)

Response Delay Testing

To test your application's handling of delayed responses, use these amounts:

AmountDelay
R10.1010 seconds
R20.2020 seconds
R30.3030 seconds
R40.4040 seconds
R50.5050 seconds
R60.6060 seconds
R70.7070 seconds
R80.8080 seconds
R90.9090 seconds

All these transactions will eventually return an approval, but with the specified delay.

Test Cards

The emulator validates PINs for the following test cards. If an incorrect PIN is provided, response code 55 (incorrect personal identification number) will be returned.

Card NumberPIN
47617390010100101234
47617390010102261234
54133300896000364315
54133300897005544315
67999989000000600184315
360705000010381234
note

For card numbers not listed above, PIN validation is skipped and any PIN can be used.