Migration
Migration of accounts involves the process of updating and transitioning the account from an older or existing account. Below are the service operations and their APIs involved in the process.
Migrate Accounts
POSTMigration of a legacy system account contract to the given account product by providing the original contract date, account name, statement, payment frequency and start date, etc.
Migrate Bills
PUTCaptures the bill information of the account such as bill id, property names, bill amount etc. This is used to migrate the bills of a legacy contract which is migrated from other system & update the bill details
Migrate Balances
PUTCaptures the balance details of the account such as balance type, due amount etc. This is used to migrate the balances of a legacy contract which is migrated from other system & update the balance details
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