When retrieving KYC documents using the MangoPay SDK, the RefusedReasonMessage field is not populated correctly. This field returns an incorrect or null value in several instances even when the KYC document has been refused for a specific reason. This issue is critical as it prevents us from properly informing users about the reasons for their KYC document rejections.
Steps to Reproduce:
Submit a KYC document that will likely be refused (e.g., Registration proof has Expired).
Could you wait for the document to be processed and a refusal decision to be made?
Retrieve the KYC document using the MangoPay SDK.
Observe that the RefusedReasonMessage is incorrect (Refused Reason) or null.
In the dashboard, it shows the proper reason but when fetching via sdk it's giving Refused Reason instead if the actual reason.
When retrieving KYC documents using the MangoPay SDK, the RefusedReasonMessage field is not populated correctly. This field returns an incorrect or null value in several instances even when the KYC document has been refused for a specific reason. This issue is critical as it prevents us from properly informing users about the reasons for their KYC document rejections.
Steps to Reproduce:
Submit a KYC document that will likely be refused (e.g., Registration proof has Expired). Could you wait for the document to be processed and a refusal decision to be made? Retrieve the KYC document using the MangoPay SDK. Observe that the RefusedReasonMessage is incorrect (Refused Reason) or null.
In the dashboard, it shows the proper reason but when fetching via sdk it's giving Refused Reason instead if the actual reason.