# Communication

# Introduction

There are several ways of connecting your system to Pagero Network.

Depending on transaction volume and technical requirements, our solutions range from very basic, manual ones to fully automated solutions integrated directly with your ERP system.

For clarity, we bundle our communication solutions in the following three categories: Basic, Advanced and Enterprise.

NOTE: Not all supported/available communication options are listed here, only the most commonly used solutions which we encourage and recommend.

# What's included?

Here is a general overview of what's included in our Basic, Advanced and Enterprise connectivity offerings.

Feature	Basic	Advanced	Enterprise
Basic, semi-manual solutions for sending/receiving e-documents	✅	✅	✅
Basic secure authentication methods	✅	✅	✅
Standardized attachment handling	✅	✅	✅
Advanced communication protocols (SFTP, HTTP)		✅	✅
Advanced authentication methods (OAuth2)		✅	✅
Enterprise, customized communication protocols (AS2, cXML, 3rd party APIs)			✅
Enterprise authentication methods (OAuth2, client certificates)			✅
Customized attachment handling			✅
Customized envelope- and/or batching handling			✅
Technical receipts/acknowledgements			✅
Customized protocol settings			✅
Pre-processing service/s			✅

Our Advanced connectivity offerings follows a set of predefined settings which we believe are "sensible defaults" to ensure the quickest setup process and as little maintenance as possible.

If you need further customization options, please check out our Enterprise Connectivity and/or our Integration toolkit offerings which allows you to explore our full range of customizable integrations options.

For more granular details, please visit the full HTTPS or SFTP sections, respectively.

# Choosing a communication type

# Recommendations

We recommend the following in order of most preferred to least preferred:

HTTPS: This communication type is superior for sending files over the internet due to its robust encryption, wider accessibility, and seamless integration with web-based workflows, offering a more secure and user-friendly experience compared to other protocols like SFTP.
Pagero-run SFTP: This communication type is extremely simple to set up and requires no ongoing maintenance. Outbound file processing is event-driven, and we processes files instantly upon receipt. Pagero-run SFTP scales virtually infinitely. However, many larger organizations are unwilling to connect to external SFTP servers and require that Pagero connect to their server instead.

# Basic communication

Our most basic communication offering is:

Document Upload: Upload files by dragging and dropping them onto our web based upload interface.
Pagero Connect: A desktop client with a graphical user interface.

Basic communication

basic/

# Advanced communication

Our advanced communication offerings include:

Document Upload - Advanced: Upload multiple files at once by dragging and dropping them onto our web based upload interface.
HTTPS: Hypertext Transfer Protocol Secure
SFTP: SSH File Transfer Protocol

These solutions offer a high level of automatation and security. Suited for companies that have access to and utilizes an integration application.

Advanced communication

advanced/

# Enterprise communication

We also offer several other communication solutions that could be utilized to connect to Pagero Network, a selection of these solutions is presented below.

APIs: REST based Application Programming Interfaces
AS2: Applicability Statement 2
cXML: Synchronous cXML request-response handling over HTTPS.
Pagero Server Connect: Fully automated application installed locally.

These are ideal solutions for systems which doesn't support any of the protocols mentioned in advanced communication.

Enterprise communication

enterprise/

If you wish to know what else we can offer, please contact us.

# REST APIs

We offer a full set of REST APIs as well, that allows applications to integrate with our platform Pagero Online even more seamlessly.

For more information on these, please see the separate REST APIs section:

REST APIs

../partners/apis/