Configuring Interchange for Electronic Signature

Only read this topic if you are using Interchange as the communication layer for Electronic Signature.

Installing Interchange

Install Axway Interchange as described in the Axway 5 Suite Installation and Prerequisites Guide.

Note: Interchange must be installed with a license key intended for non FIPS compliance usage.

Configuring Interchange for Electronic Signature

This section explains how to configure Interchange for Electronic Signature. The information provided is just an example. You need to adapt this according to your own requirements. For full details about creating objects, refer to the Axway Interchange Administrator's Guide.

1. From the Interchange Start menu folder, launch the Admin shortcut.
2. In the System Management menu, create a Trading Engine (TE).
3. Run the Trading Engine.
4. Create a community. The Routing ID corresponds to the EBICS CustomerId of the remote Bank.
5. Define certificate usage. In the community definition, the signing certificate corresponds to the EBICS identification and authentication certificate. The encryption certificate corresponds to the EBICS encryption certificate.
6. Set up an integration pickup exchange for picking up messages from integration.
   This corresponds to the entry point where files to be sent in EBICS are deposited. This depends on the way Interchange is integrated to the back-end. Examples are: a simple directory scan, an integration through Integrator, an incoming PeSIT message, ...
7. Set up an integration delivery exchange for routing received messages to integration.
   Delivery exchange for routing received messages to integration corresponds to the way to retrieve messages fetched in EBICS. Those files must go to the back-end (Integrator for example).
8. Set up a pickup/delivery exchange. In order to communicate with a bank using EBICS, the message protocol must be set to EBICS.
9. Configure Inline processing. Note that this step is important for integration with Electronic Signature.
10. Create a partner for the community. The partner corresponds to the EBICS Bank that you want to exchange with. The Routing ID corresponds to the EBICS HostId of the remote Bank.
11. Set up EBICS communication between the community and the partner:
    • In Partner detail, set up a delivery exchange. In order to communicate with a bank using EBICS, the message protocol must be set to EBICS.
    • EBICS Bank Settings: Choose the protocol version of the bank (France is H003).
    • Choose Signature version. Electronic Signature handles only A005 signature version.
    • Configure the HTTP settings: Enter the URL of the remote EBICS bank.
    • Delivery exchange name: Enter a meaningful name for this delivery exchange.
    • Save your delivery exchange.
12. Import SSL certificate of the remote EBICS Server:
    • Go to your community, click certificates, and SSL trusted root certificates.
    • Add this SSL certificate.

For more information about configuring Interchange, refer to the Axway Interchange documentation.

Sending EBICS requests using MMD files

In Interchange, MMD XML files can be used as an alternative to inline processing.

In order to use this method, you need to create a File system-type Integration pickup and place the XML files in the location defined for the pickup. Interchange will parse the files and trigger the send or fetch EBICS request.

MMD XML file examples

Send

where:

From is the EBICS HostId of the Bank.

To is the EBICS customerID.

message.waitUpdate is "true" if the send has to go via Electronic Signature.

ebics.action is the EBICS request action type (send or fetch)

ebics.orderType is the full EBICS order type.

ebics.domain is the domain of the payload. The domain is the organizational entity within a company.

ebics.sender is the sender of the payload. The sender is the application that initiates a payment flow.

ebics.amount is the global amount of the payment that is displayed in the Electronic Signature UI (optional). If a value is specified here it will override the amount parsed from the payload.

ebics.operationNb is the number of operation of the given payment file. This value is displayed in the Electronic Signature UI (optional). If a value is specified here it will override the number of operations parsed from the payload.

ebics.user.userId is the EBICS userID of the transport user (optional).

message.comment is any business information that might help the treasurers to sign a payment. This value is displayed in the Electronic Signature UI (optional).

Payload id is the id of the payload, this parameter is mandatory.

Location type is the location and type of payload

Fetch

where:

From is the EBICS HostId of the Bank.

To is the EBICS customerID.

message.waitUpdate is "true" if the send has to go via Electronic Signature.

ebics.action is the EBICS request action type (send or fetch)

ebics.orderType is the full EBICS order type.

ebics.user.userId is the EBICS userID of the transport user.

Related topics

Inline processing for Interchange/Electronic Signature integration

Configuring Electronic Signature