---
title: "Legacy update score"
method: POST
path: "/update-score"
tags: ["Compatibility"]
---

# Legacy update score

`POST /update-score`

Legacy compatibility route. New integrations should use /update-gateway-score.

## Request body

- LegacyUpdateScoreRequest — Legacy score-feedback payload built from full internal transaction objects. This is NOT the `/update-gateway-score` shape. `txn_detail` and `txn_card_info` must each carry a `partitionKey` key (value may be null), and their `id` fields are numeric strings.
  - `txn_detail` object, required — Full internal transaction object.
    - `partitionKey` string, nullable, required — Required key. May be null.
    - `id` string, required — Numeric string. Must be present and parse as an integer - the conversion unwraps the parsed value, so a missing or non-numeric id panics the handler instead of returning a 4xx.
    - `netAmount` number, double, required
    - `currency` string, required
  - `txn_card_info` object, required — Full internal card/payment-method object.
    - `partitionKey` string, nullable, required — Required key. May be null.
    - `id` string, required — Numeric string.
    - `txnId` string
    - `txnDetailId` string — Numeric string.
  - `log_message` string, required
  - `enforce_dynaic_routing_failure` boolean, nullable
  - `gateway_reference_id` string, nullable
  - `txn_latency` object, nullable
    - `gatewayLatency` number, double, nullable

## Response `200`

OK

- string — Bare JSON string, not an object.

---

[API](https://skmtc.net/juspay/apis/decision-engine.md) · [All operations](https://skmtc.net/juspay/apis/decision-engine/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/juspay/decision-engine/versions/36e7a0972ee6/schema)