Webservices

Outbound SCT Inst payment request received via SOAP services, ReST web services or via J-SON over JMS from the bank’s channels is processed in Oracle Banking Payments. The system automatically creates an Outbound SCT Inst payment transaction for a web service request received.

If the Transaction branch code is received but no Host code then Host code is identified and populated in the transaction based on the Transaction branch code.

Instead of the fields of Creditor Account IBAN, Creditor Account Name and Creditor Bank Code being present in the request, SSI label may be present.

If the End to End ID value is not received in the request then this field in the transaction is set to Transaction Reference Number.

Instruction date, if not provided will be considered as current date.

On receiving and parsing of a payment request via ReST web services or via J-SON over JMS, the system performs validations for the following mandatory fields:

Network code
Transaction Branch
Source Reference Number
Debtor Account Number
Creditor IBAN - This field may be empty if SSI label is present
Creditor Account Name - This field may be empty if SSI label is present
Transfer Currency
Transfer Amount

Note:

Creditor Bank Code is not mandatory in the request as the Creditor Bank BIC can be derived from the Creditor IBAN available. All transaction field level validations applicable to user interface is applicable to requests received through web services too.

Parent topic: Outbound Faster Payments Transaction Processes