Sterling B2B Integrator - Submitting orders

An order type defines the nature of an EBICS transaction.

EBICS Client supports the following order types:
Key management order type
This order type is used for uploading or downloading technical information such as bank key, user initialization, key management, cancellation of orders, VEU, and so on. Key management order type is also called System order type.
Bank-technical order type
This order type is used for various upload and download transactions that happen between a subscriber and a bank. The contract signed between a bank and a partner specifies the order types the users can submit. The bank configures the order types using the Sterling B2B Integrator EBICS Banking Server. Bank-technical orders are classified as Upload orders (FUL) and Download orders (FDL). You can upload an order payload, that is submit an order to a bank using an upload order. A download order allows you to download a report or statement from the bank.
Key Management Order Types
The following table lists the supported upload key management order types:
Table 1. Upload Key management order types
Upload Key management order type
Description
INIUsed in subscriber initialization. Sends the bank-technical public certificate of a customer to the EBICS Banking Server. The order data is compressed and base64-encoded.
HIAUsed to transmit user public certificates for identification and authentication, and encryption within the framework of subscriber initialization. The order data is compressed and base64-encoded.
H3KUsed to transmit user public certificates for Electronic Signature, identification and authentication, and encryption to enable the user to initiate transactions with the bank.
PUBUsed to update customer’s certificates. Sends the bank-technical public certificate of the customer for updating the EBICS Banking Server. The order data is signed, compressed, encrypted, and base64-encoded.
HCAUsed to update customer’s certificate. Sends the following certificates for updating the EBICS Banking Server:
  • Identification and authentication public certificate
  • Encryption public certificate
The order data is signed, compressed, encrypted, and base64-encoded.
HCSUsed to update customer’s certificate. Sends the following certificates for updating the EBICS Banking Server:
  • Bank-technical public certificate
  • Identification and authentication public certificate
  • Encryption public certificate
The order data is signed, compressed, encrypted, and base64-encoded.
SPRUsed to suspend a user’s access authorization. Only the electronic signature of the EBICS Client user is sent. The order data is a blank character. The signature is compressed, encrypted, and base64 encoded as in regular upload.
YCTUsed to upload credit transfer initiation.
XCTUsed to upload credit transfer initiation.
YDDUsed to upload direct debit initiation.
The following table lists the supported download key management order types:
Table 2. Download Key management order types
Download Key management order type
Description
HPBUsed to download bank public certificates from the EBICS Banking Server. The order data is compressed, encrypted, and base64-encoded. The response message and the order data are not signed.
HPDUsed to download bank parameters from the EBICS Banking Server. The order data is signed, compressed, encrypted, and base64-encoded.
HEVUsed to download information about supported EBICS versions.
HKDUsed to download information about a partner and associated subscribers. The order data is compressed and base64-encoded.
HTDUsed to download information about a subscriber and associated partner. The order data is compressed and base64-encoded.
XTXUsed to download payment status report for credit transfer.
Submitting distributed signature (VEU)

EBICS Client supports Distributed Electronic Signature (VEU). VEU is a feature that allows orders to be authorized by multiple subscribers.. The File Format attribute identifies the type of file that is uploaded or downloaded. The file format attribute is required as part of the order details.

The following table lists the supported upload VEU order types:
Table 3. Download VEU order types
Download VEU order types
Description
HVUUsed to download VEU overview. In the HVU request, the subscriber optionally submits a list of order types for which the subscriber is authorized as a signatory. The order data is compressed and base64-encoded.
HVDUsed to retrieve the state of an order that is currently in VEU processing and for which the subscriber is authorized as a signatory. With HVD, the hash value of the order is retrieved. The order data is compressed and base64-encoded.
HVZUsed to download VEU overview with additional information. In the HVZ request, the subscriber optionally submits a list of order types for which the subscriber is authorized as a signatory. HVZ response order data contains the complete information of HVU response order data and HVD response order data, except the display file element. The order data is compressed and base64-encoded.
HVTUsed to retrieve transaction details about an order from VEU processing. The order data is compressed and base64-encoded.
The following table lists the supported download VEU order types:
Table 4. Upload VEU order types
Upload VEU order types
Description
HVEUsed to add a bank-technical signature for authorization to an order for VEU processing. The order data is compressed and base64-encoded.
HVSUsed to permanently cancel an existing order from VEU processing. The subscriber sends an HVS request to cancel an order and delivers the bank-technical signature required for cancellation through the hash value of the order data. The HVS response does not contain any VEU-specific data.

Previous Topic

Sterling B2B Integrator - Managing certificates and keys for users

Parent Topic

Sterling B2B Integrator - EBICS Client Architecture and Key Features

Next Topic

Sterling B2B Integrator -Pending Signatures