[BUG] ACI connector, Capture (CP) returns "Something went wrong" "HE_00" but CP is successful at ACI

[supportstreampayments]

Bug Description

Capture from Hyperswitch to ACI returns "Something went wrong" "HE_00" but CP is successful

• Screenshot from ACI

• Screenshot from Hyperswitch

• Screenshot from Hyperswitch API

Expected Behavior

The response from Capture should be approved

Actual Behavior

The API returns

And from the Hyperswith Sandbox log could be seen

Log Details
Request
Response
Merchant Id

"merchant_1755167395"

Payment Id

"pay_XmBhZqKOe4e9vM12bopN"

Connector Name

"aci"

Request Id

"0199a4f2-b6cd-78f1-a485-b8b410120e68"

Error

"{"error":"Failed to deserialize connector response"}"

Latency

336

Method

"POST"

Steps To Reproduce

Steps to reproduce

1. Process a Authorization (PA) transaction to ACI - "capture_method": "manual" - parameter from Hyperswitch

POST https://sandbox.hyperswitch.io/payments

{
  "amount": 200,
  "currency": "EUR",
  "capture_method": "manual",
  "confirm": true,
    "profile_id": "pro_tfNL5gntC4xv8IwYWlST",
  "connector": ["aci"],
  "payment_method": "card",
  "payment_method_data": {
    "card": {
      "card_number": "4000003800000446",
      "card_exp_month": "12",
      "card_exp_year": "2026",
       "card_holder_name": "joseph Doe",
      "card_cvc": "123"
    }
  }

}

Response

{
    "payment_id": "pay_XmBhZqKOe4e9vM12bopN",
    "merchant_id": "merchant_1755167395",
    "status": "requires_capture",
    "amount": 200,
    "net_amount": 200,
.....

3. Try to do a Capture

POST https://sandbox.hyperswitch.io/payments/pay_XmBhZqKOe4e9vM12bopN/capture
Request

{
  "amount_to_capture": 200,
    "connector": ["aci"],

  "currency": "EUR"
}

Response

{
    "error": {
        "type": "api",
        "message": "Something went wrong",
        "code": "HE_00"
    }
}

Context For The Bug

No response

Environment

Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the x-request-id response header to help us debug your issue.

If not (or if building/running locally), please provide the following details:

1. Operating System or Linux distribution:
2. Rust version (output of rustc --version): ``
3. App version (output of cargo r --features vergen -- --version): ``

Have you spent some time checking if this bug has been raised before?

• I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit a PR?

None

[Anurag-05-prog]

Hi @supportstreampayments, this issue has already been addressed in PR #9502, but the fix does not seem to be deployed to the sandbox environment yet.