Sterling B2B Integrator - Order Submission

Upload Order

Order initialization

A user initiates an upload transaction with the bank by submitting an upload (FUL) order request. The EBICS Client Runtime component verifies the authorization level of the user and the number of required signatures to process the order. If the required criteria are met, then the order is processed and sent to the bank system. Else, the order is stored in the database and the Pending tasks page on EBICS Client dashboard interface is updated with the pending order details. When an EBICS Client user with pending orders (signing or submitting) logs in to the EBICS Client dashboard interface, the Pending tasks page opens prompting the user to sign or submit the order.

Order processing

Download Order

Order initialization

A user initiates a download transaction with the bank by submitting a download (FDL) order request. The EBICS Client Runtime component verifies the authorization level of the user. If the required criteria are met, then the order is processed and sent to the bank system.

Order processing

Acknowledgement

After receiving the last segment of the order data from the bank, the client initiates the last phase, the acknowledgement request, to indicate that the data transfer is successful. If the bank receives a positive acknowledgement (receipt code=0) from the client, the bank moves the downloaded messages from the user download mailbox to the user archive mailbox. If the bank receives a negative acknowledgement from the client, the bank retains the downloaded messages in the user’s download mailbox.

Order Packaging

The order data is packaged according to the specified signing, compression, encryption, and encoding settings. For example, if the order type is FUL, the FULPackingHandler is invoked.

Order Data Segmentation

As per EBICS specifications for data transfer, the size of a compressed file, encrypted, and encoded order data must be less than or equal to 1-MB. If the size exceeds 1 MB after compression, encryption and encoding, then the order data is segmented such that each segment does not exceed the fixed 1-MB size. The segments are then transmitted sequentially in a consecutive order in individual EBICS messages.

Order Unpacking

Order unpacking involves decoding, decryption, decompression, and verification of the order data. It also involves logging orders for which the security operations have failed and the reasons for failure.

Segment Concatenation

The recipient system (server or client) executes the algorithmic computations in reverse order to recover the original order data. The data segments are sequentially appended, decoded, decrypted, and expanded to obtain the original order data.