Main.Invoicing.invoice-service.Implementation guide.Technical reference.PayEx Connect (API) - PayEx Connect (API)

Page of - last modified by Fredrik Nilsson on 2023/03/24 09:42

PayEx Connect (API)

Fredrik Nilsson

2023/03/24 09:42

Table of Contents

Overview

Structure of this documentation

The implementation manual

The sample service manual

The external services manual

N.B. This page describes legacy API integration that are still in use but is not implemented for new customers. Implementation guide for PayEx Invoice Service API:s is found here

PayEx Connect API enables integrated access to PayEx services in a controlled and secure manner. This documentation targets technical system integrators and developers implementing the PayEx Connect API, that enable customers to access legacy services in a controlled and secure manner.

Overview

PayEx Connect use standard 128 bit SSL encryption to secure the communication channel. Client authentication is managed through UsernameTokens and IP filtering.

The only protocol supported is Http Soap. Http Get and Http post is not allowed.

The picture below gives an architectual overview.

PayEx Connect authenticates the client using a UsernameToken security token. The SOAP message is not encrypted or digitally signed, the transportation is secured and encrypted through SSL. Microsoft Asp.Net clients can use the UsernameOverTransportAssertion defined in WSE 3.0 to create and manage UsenameTokens.

Structure of this documentation

This documentation contains several parts, as described below.

The implementation manual

Learn what you need to do prior to integrating a system with PayEx Connect. This section cover necessary prerequisites, implementation, security and error handling.

The sample service manual

This manual cover web methods used in sample scenarios.

The external services manual

This manual covers integration with PayEx Invoice Services.

Learn about following methods:

Get Invoice Information

Get Invoice document in the format of PDF

Get Customer Information

Register invoice/customer action