Why is AlphaCommerceHub unable to detect `Method` automatically by `MerchantTxnID` and responds «No routing available for the supplied parameters» to a PayPal's `PaymentStatus` request if `Method` is not provided?

Extensions AlphaCommerceHub
, , , , ,
1

Request

{
    "Header": {
        "MerchantID": "ANTERIOR001",
        "TransactionType": "PaymentStatus",
        "UserID": "<...>",
        "Version": "2"
    },
    "Transaction": {
        "MerchantTxnID": "1208L.769"
    }
}

Response

{
    "Banks": null,
    "Country": null,
    "DocumentResults": null,
    "EmailChecks": null,
    "FraudChecks": null,
    "GeoChecks": null,
    "ProviderResps": {
        "ProviderResp": []
    },
    "Result": {
        "custom1": null,
        "custom2": null,
        "custom3": null,
        "custom4": null,
        "custom5": null,
        "MerchantID": "ANTERIOR001",
        "MerchantTxnID": "1208L.769",
        "ResponseCode": "1064",
        "ResponseMessage": "No routing available for the supplied parameters. Please review routing parameter configuration",
        "ResponseTimestamp": "08122017053903"
    },
    "ShippingService": null,
    "TaxResultLines": null
}
2

This is the current behaviour. For our duplicate checking in theory a customer could try one payment method which was unsuccessful, get returned to the payment page and choose another payment method. Both could use the PaymentStatus txntype. On the same txnid we would not know which payment processor to route to. We will review behaviour