Upload From a Subscriber (FUL)
The FUL order type is used to upload data to a bank.
- Data Transfer
The user sends the upload (FUL) request to the bank. FUL is a bank-technical upload order type.
The EBICS Order Authorization service handles incoming order requests for the bank-technical upload order type. If an order has obtained the number of signatures required, this service forwards the order to the subscriber upload mailbox. Otherwise, this service retains the order data in the database until all the required number of signatures is obtained.
The handleEBICSRequest business process receives a user's request. If the user's request contains the last segment of the order data, it invokes the EBICSOrderAuthorizationProcessing business process asynchronously to unpack the order data and generate the following files:
- .DAT - Contains the unpacked order data in a user's upload mailbox
- .SIG - Contains the signature of the order data in a user's upload mailbox
- .PRM - Contains the order parameters in the user's upload mailbox
- .PSR - Contains a status report of asynchronous processing in the user's download mailbox
A user initiates a transaction by submitting the requests containing information about the incoming order. Based on this information, the EBICS Server verifies the order type, performs the message replay test, verifies message authentication, and checks user authorization before accepting the request.
After successful verification of the order data, the bank generates a transaction ID and includes the ID in its response to the user.
Processing Data Transfer
When more than one segment is required to transfer order data, the bank performs message authentication, verifies the transaction, verifies the segment number and size. After the EBICS Server receives the last segment of the order data, the complete order data is forwarded to the EBICSOrderAuthorizationProcessing business process asynchronously and the transaction ends.
The EBICSOrderAuthorizationProcessing business process unpacks the order data and forwards it to the user upload mailbox. The EBICSOrderAuthorizationProcessing business process generates post processing report (PSR) and routes it to the user's download mailbox. This business process also generates the .SIG and .PRM files to be forwarded to the user's upload mailbox. An .err file is generated when EBICSOrderAuthorizationProcessing business process encounters an error, for example, an invalid electronic signature. Use the .err file to inspect an invalid order data file, if necessary.