Skip to content

Create Transaction

Case

You have only the business data required for the operation, such as the card number, expiration date, amount, terminal parameters, and other transaction fields.

The final result should be a transaction file in JSON format based on the unified Transaction data model. This file can be used everywhere in Signal: loaded into the GUI, sent through the API, processed in CLI mode, or used directly by the Python library.

Because all interfaces work with the same Transaction model, the created file remains fully compatible across the entire system.

The goal is to create a valid transaction file that can be used for processing, as shown in the example below.

JSON transaction example 
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
{
    "message_type": "0200",
    "max_amount": "100",
    "generate_fields": [
        "4",
        "7",
        "11",
        "12",
        "37"
    ],
    "data_fields": {
        "2": "4000000000000000",
        "3": "000000",
        "4": "000000004679",
        "7": "0727142832",
        "11": "981533",
        "12": "230727142832",
        "14": "3504",
        "18": "8999",
        "22": "810",
        "37": "159384172368",
        "41": "70000826",
        "42": "000000010000866",
        "43": "PSP*merch.com               >Limassol>CY",
        "47": {
            "227": {
                "01": "Limassol",
                "03": "CYP",
                "04": "3101"
            },
            "072": "20240303_184906_8769658371",
            "033": "5",
            "027": "30303030433032445531325350334c48474b564c",
            "028": "00000308254236854496634394423610b892eb6a",
            "030": "2",
            "226": "unlimit.com"
        },
        "48": {
            "51": "SOME ONE",
            "96": "415481%8164",
            "54": "HOW ARE YOU",
            "42": "01",
            "92": "000"
        },
        "49": "978"
    }
}

Solution

There are three main ways to create such a transaction file.

1. Create through GUI

Open the Main Window, manually fill in the required fields, then press Ctrl + S or use the Save File button, choose an output folder and JSON format.

This is the most convenient method for manual work, testing, and preparing new transactions during certification or debugging.

2. Create manually

You can manually prepare the transaction file using any text editor such as Notepad.

Signal supports JSON, INI, and DUMP formats. In most cases, JSON is recommended because it is readable, structured, and fully compatible with all system interfaces.

Manual creation is not recommended. Signal provides many tools to work with transaction data.

3. Convert from existing transaction data

If you already have a transaction in INI or DUMP format or an SV dump, it can be converted into a JSON representation.

This is often used when working with raw host dumps, legacy files, or imported certification examples.

Transaction conversion between supported formats is described in a separate chapter of this section.