AM/TA/Inv - Mark Payment Batch as Settled

Details

/external/v1/payment/batch-settlearrow-up-right

Synopsis

Mark Payment Batch as Settled

put

This route is used to trigger the process to mark a list of payments of a given security as settled. It will also trigger the settlement of all the associated entities (if needed). It triggers an asynchronous process that will persist this information on the blockchain, which can be monitored using the "Transactions API" endpoints. This endpoint can be invoked if the security is in one of the following statuses: ["active","completed","approved_revert_to_active","closed","cancel_in_progress","canceled","refund_in_progress"]. This endpoint can be invoked by organizations that have at least one of the following roles on this security: ["issuer","service_provider","investor"]. This endpoint can't be invoked if the security is restricted. This endpoint can be called by applications with access to scope "managePayment".

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
  • : managePayment
Authorizations
OAuth2clientCredentialsRequired
Token URL:
Body
Responses
chevron-right
200

Successfully triggered the process to mark payments as settled.The "processId" and "orchestrationId" properties can be used on the "Transactions API" to monitor the status of this asynchronous process.

application/json
processIdstringRequired

This is used to uniquely identity a transaction process on this system.

Example: 2159457f-0167-4e93-a969-9cf0db05e0bf
orchestrationIdstringRequired

The orchestration id. It is used to uniquely identity a group of transactions that are being orchestrated following an action request.If a processId was passed as an input to the action, it will be returned on this property.

Example: 2159457f-0167-4e93-a969-9cf0db05e0bf
put
/external/v1/payment/batch-settle

Last updated

Was this helpful?