Syndicated Loan
Syndicated or club loans are substantial credit facilities provided by a group of lenders to a single borrower. Below are the service operations for creating syndicated loan arrangements.
-
Creates a club facility with facility details along with the details of participating lenders
-
Creates a club drawing arrangement with drawdown details along with the details of participating lenders
-
Creates a funded share transfer for a facility when participant details are passed. Share of a funding participant is transferred to another funding participant in a club facility and underlying drawings
Transfer Risk Share
POSTCreates a risk share transfer for a facility when participant details are passed. The risk of the own bank in a facility is mitigated by selling a portion risk to another financial institution
-
Creates a funded share transfer for a drawing under a facility when participant details are passed. Share of a funding participant is transferred to another funding participant in a standalone club loan
-
Creates a risk share transfer for a drawing under a facility when participant details are passed. The risk of the own bank in a loan is mitigated by selling a portion risk to another financial institution
-
Retrieves club facilities, drawings and deal
Create a Payment Order
You can create a payment order for the below payment products by inputting the payment order product and other mandatory fields like debit account, amount, beneficiary IBAN, and so on in Temenos Transact for various scenarios like loan disbursement, merchant fee processing, prepay, and loan repayment.
Create Payment Order
POSTCreate the payment order in Transact for various scenarios like loan disbursement, merchant fee processing, prepay and loan repayment
-
Initate a new instant payment order. This API can be called in validate or commit mode. Former validates and responds back with status (and errors if any). Latter validates and commits if there are no validation errors.
Initiate Recall
You can initiate recall when a completed payment needs to be reversed. It can be requested either by the bank or the customer with appropriate reasons.
-
Create a recall in response to a bank operator's request for a payment that has been previously sent out. Recall can be initiated for a specific payment reference and requires reason (code) for recall.
-
Create a recall in response to a customer's request for a payment that has been previously sent out. Recall can be initiated for a specific payment reference and requires reason (code) for recall.
Accept or Reject Recall
You can initiate recall when a completed payment needs to be reversed. This recall requested by the bank or customer can be either accepted or rejected stating appropriate reasons.
Accept Recall
PUTRespond to a recall request for a payment that was made previously. Positive (Acceptance - Willing to Return Funds) or Negative (Rejection - Unwilling to Return Funds) responses are acceptable, but they must be accompanied by a reason (code).
Reject Recall
PUTRespond to a recall request for a payment that was made previously. Positive (Acceptance - Willing to Return Funds) or Negative (Rejection - Unwilling to Return Funds) responses are acceptable, but they must be accompanied by a reason (code).
Fetch Information
You can fetch information related to payment order.
-
Retrieves all type of payment transactions
-
Retrieves audit trail which contains information on the lifecycle of a payment. Details can be retrieved for a specific payment or for all payments in the system.
-
Retrieve the status of payment order for a given order id
-
Retrieves the history of all cases associated with a specific payment
-
Retrieve completed payments that are eligible for recall
-
Retrieve the status of an outward recall requests sent for completed payments