As per the new CyberSource structure for processing MADA transactions, the dsReferenceNumber is required in the authorization request.
However, the ValidateAuthenticationResults response returned by the .NET Standard SDK does not contain the dsReferenceNumber. We have verified through internal SDK logs that this value is present in the underlying REST API HTTP response, but it is not exposed through the SDK response model.
Due to this limitation, we are unable to pass the dsReferenceNumber in the subsequent authorization request. We request that this field be added to the ValidateAuthenticationResults response model in the SDK so that it is available for downstream authorization processing.
As per the new CyberSource structure for processing MADA transactions, the dsReferenceNumber is required in the authorization request.
However, the ValidateAuthenticationResults response returned by the .NET Standard SDK does not contain the dsReferenceNumber. We have verified through internal SDK logs that this value is present in the underlying REST API HTTP response, but it is not exposed through the SDK response model.
Due to this limitation, we are unable to pass the dsReferenceNumber in the subsequent authorization request. We request that this field be added to the ValidateAuthenticationResults response model in the SDK so that it is available for downstream authorization processing.