Notification of an Alert Status Update

The notification of an Alert's status update will push a notification to the merchants system that an alert has had its status updated. The merchant must opt in to receive these notifications This will happen when the status field of an alert has changed, if any other field is updated and the status remains the same, it will not send a notification.

The merchant must provide TxShield with the URL that they want the status update notifications sent to. This must be a https URL. The merchant can also, and it's also strongly recommended, that they protect the endpoint with a long lived bearer token that they provide to TxAlert.

POST https://{merchant_supplied_url}

The data in this call is sent as x-www-form-urlencoded data.

Request Body

Name	Type	Description
alert_id	String	Alert ID from TxShield.
status	String	Status of the transaction. - RESOLVED - DECLINED - WIP - RDR_DELETE. See status page for details.
reason_code	String	reason code that was updated. In case of RDR_DELETE, the reason_code will be empty Refer table below
merchant_update_on	String	Date when the update was received from merchant(not available for RDR Delete)
outcome_updated_on	String	Date when provider was updated successfully(not available for RDR Delete)

Example

Headers

Accept: application/json
Content-Type: application/x-www-form-urlencoded
Authorization: {BEARER_TOKEN_VALUE_TO_BE_GIVEN_BY_THE_MERCHANT}

Data - full

The full data set being sent. The data in this call is sent as x-www-form-urlencoded data.

action=statusupdate&alert_id=1000&status=wip&reason_code=000.001