Connect to Inyett

Congratulations on a good choice! Now it’s time to connect to Inyett.

1. Select the connection type
You choose one of the methods that best suits below.

2. Settings
Once you have selected the method, we will set the necessary settings and send the instructions to you.

3. Connect!
You configure against the type of connection you have selected using our instructions.

4. Test and verify
We test and verify that everything works.

Integration with transmission via SFTP

Recommended
Connection via SFTP to our server to submit payment files.

Here we create an account on our server that you as a customer can connect to with your username and password. Connection takes place directly to the root folder where the payment file is uploaded.

The only thing that needs to be configured is an integration that takes copies of the payment files.

Inyett Encrypt Service 

In-house developed Windows service that works as a simple file protection. Monitors a specified folder and transmits copies of payment files via an encrypted communication channel.

The service requires four things to work:
1. Must run on a Windows operating system.

2. The server on which the service is running must have the correct .NET version installed (.NET 3.5.).

3. The service must have full rights to the folders / paths used.

4. The service must have port 22 open for https://ftp.inyett.se.

In the service configuration file, you specify which paths to use, which files to locate and which license key to use. You get this key from us.

Visma Autopay

With our standard integration for Autopay, payment transactions are transferred via a full connection between Visma Autopay and Inyett.

Activation is performed in Visma Autopay, as well as on the customer’s profile at Inyett.

After activation, payment data is transferred to Inyett for analysis.

Webbservice

Simple web-based service for transferring payment files.

Connect to the address / URL:
https://import.inyett.com

The method is called “/ FileUpload” and requires three parameters:

key
Customer unique key

filename
Name of the payment file

file
The payment file

The API also requires a license key called X-Api-Key which is sent to you.

The set requires an integration that connects to the address and transfers copies of payment files via the above method.

xLedger

With the help of our standard integration for xLedger, payment transactions are transferred via a complete connection between xLedger and Inyett.

Activation is performed on the customer’s profile on Inyett with unit time from xLedger and activation on xLedger on the customer’s account.

After activation, payment data is transferred to Inyett for analysis.