P2P payment, setup

Omni Channel Payment Solution for P2P Payment, Mobile Payment and In-Store Payments.

Transaction fees

In principle, the Gudix P2P payment module is free of charge. Due to the decentralized software architecture, it is necessary to write data to the Gudix Core. This data is encrypted with nuts and made compatible. Every transaction requires a Gudix Nut.


Nuts can be bought and sold in the public exchange. Every user can generate nuts via the Genesis module. The Gudix Core is a private ledger that relies on nuts being generated.


Fast and easy Set-up

Your own payment solution is quick and easy to set up and can be integrated into existing business processes.

Omni channel

The payment solution is based on a P2P architecture and can also be used for mobile payment and in-store payments.

Alternative business models

The P2P module is suitable for business models with special and individual requirements.

Support Chat

If you have any questions about the setup or if you are interested in even more individual payment solutions, please contact us via Telegram.

open Chat
gudix networker


Peer-2-peer means from device to device. We use every device with an internet connection as a payment terminal. You can send or receive money. Simply generate the QR code that contains the link that the payer will use to pay and the recipient to receive tokenized value. The P2P payment system from Gudix can be easily and simply integrated into existing business processes. The solution is basically free of charge, but since the transaction data must be encrypted, so-called Gudix Nuts must be integrated into the transaction process. Gudix Nuts are authorizations to encrypt data in the Gudix Core, resp. tokenize. Nuts can be purchased in the exchange or are available in packages. Since the Gudix Core secures and validates itself, it pours out Gudix Nuts. Nuts can be created using the Genesis module. In order for a transaction to take place, the user must authenticate his wallet. An authentication can be generated via the API and or via the Telegram supported web interface. If you are not currently logged in, you will find the authentication button here.

First registration / Authentification

After the user has registered for the first time, 1 click on the blue button will be sufficient in the future. This is the world's fastest and easiest authentication. A mobile phone number is sufficient for the initial registration. The Telegram app is required.

Telegram Appstore
Telegram Google Play
Video Example
create and get transaction in one process

Payment Core

The payment process is based on a QR code that is generated for transactions that need to be sent or received. The one who generates the QR code is the initiant. The person who reads the QR code is the reader; the initiant generates a QR code in order to send or receive payments or transactions. The reader preferably reads the QR code with its smartphone camera and opens the link behind the QR code. Once on the target page, the reader authenticates itself and carries out the payment or accepts the amount.

Omni-Channel Payment


The QR code is generated on the initiant's smartphone. The initiant shows the code to the reader. The reader reacts, reads the code via his smartphone, navigates to the payment page, authenticates itself if necessary and carries out the transaction.

Online Payment

The QR code is generated by the initiant. The QR code and the link can be extracted and incorporated into the initiant's website. The link can also be sent or transmitted to the reader as a payment link.

Local in-store payment

The QR code can be printed out and deposited with a fixed amount. If no amount is entered, the reader will determine the amount. The printed QR code can be attached in a retail shop. The reader pays on site using his smartphone.

Prepare transaction

The simplest solution is to use the Gudix web interface. The initiant intuitively generates a QR code on the Gudix Payment Page for initiating a peer-to-peer transmission.

GET Parameter

Under the link https://gudix.net/payment further GET parameters can be attached to the URL, to further automate the work steps up to the QR code. Without a GET parameter, it must be defined on the payment page whether a transaction is to be sent or received and, under certain circumstances, what amount is involved. The process can be further prepared by adding the following parameters:


indicates the amount to be transmitted or received


The currency for the country is recognized by default. Currently only CHF, USD and EUR are available, with tokenized CHF being billed in the background, resp. is converted.


To send a transaction, choose "send". To get one the value "get". Important note: If the parameter Action is built into the URL, the URL is reformatted to a configuration. A configuration is specified with the "conf" parameter as the only parameter in the URL. All parameters are included in the configuration.

Configuration parameters: conf

With a configuration string in the conf parameter, further user-specific parameters can be incorporated into the process. If a webhook is used, all data will be forwarded to the webhook via a POST request after the transaction has been completed. The conf parameter should always appear alone in the URL, because it contains the data that are transferred to the core. If an action parameter is written into the URL, the Conf-URL is generated automatically and forwarding takes place.

Data Check

With every configuration, data is prepared in the background that is transmitted by the transaction. In order to view the data, the parameter datacheck can be added into the URL. All parameters used will be displayed. This parameter is only intended for test purposes.

User-specific parameters

Any number of user-specific parameters can be transferred. All data are recorded in one and the system-relevant data is added. All data together are contained in the QR code. The more data is written, the larger the QR code, resp. the more difficult it is to read it. We recommend keeping the data as lean as possible. Parameters can be transferred via GET request as already described above. Or they are sent via POST request to the conf url. GET and POST requests must be sent to the configuration url https://gudix.net/conf. The necessary configuration is returned in JSON format.


is integrated in the url parameter and is a base64 encoding of the transmitted parameters


is the URL where the reader can make or receive his payment


The URL under which the QR code is generated, downloaded or transferred directly to the payment page.


If the webhook URL is a valid URL, the recipient will receive all the data supplied via a POST request. So it is possible that customer e-mail addresses, article numbers, etc. are built into the QR code. If an item is sold, the payee receives the necessary notification. If no webook is specified, the payee receives a notification in Telegram when the system can find a Telegram Chatid. The notification can be completely deactivated with the webhook "" (set webhook field, but without value).


The root ID is the partner ID in the background that "infects" the payee. A cookie is saved to recognize the initiant. If the reader purchases nuts in the Exchange at a later date, the initiant is rewarded with provisioned nuts. This process runs automatically in the background. Up to 8 commission levels are supported, depending on the initiant's package.


With this URL, the reader will be forwarded to the appropriate point after the payment process. This variable is particularly suitable for online payments.

Configuration URL example GET


results in:

    "conf": "eyJhY3Rpb24iOiJnZXQiLCJhZ2VudCI6OTgyMzkwMDUyLCJhbW91bnQiOiIxNTAwIn0=",
    "url": "https://gudix.net/payment?conf=eyJhY3Rpb24iOiJnZXQiLCJhZ2VudCI6OTgyMzkwMDUyLCJhbW91bnQiOiIxNTAwIn0=",
    "qr": "https://chart.apis.google.com/chart?chs=500x500&cht=qr&chld=M&chl=https://gudix.net/payment?conf=eyJhY3Rpb24iOiJnZXQiLCJhZ2VudCI6OTgyMzkwMDUyLCJhbW91bnQiOiIxNTAwIn0="