{"section":"known-issues","requestedLocale":"en","requestedSlug":"legacy-antifrauds-cannot-complete-a-request-when-the-accountid-is-missing","locale":"en","slug":"legacy-antifrauds-cannot-complete-a-request-when-the-accountid-is-missing","path":"docs/en/known-issues/Payments/legacy-antifrauds-cannot-complete-a-request-when-the-accountid-is-missing.md","branch":"main","content":"## Summary\n\n\nThere's an issue with approving some transactions that are related to our legacy anti-fraud connectors. This issue arises when the system fails to make the necessary request due to the absence of the accountId, which is required to retrieve payment information from the account database. You can verify this by examining the \"/payment\" route, where you will find the node \"usedAccountId\" with a value of \"False\" in such cases.\n\n**\\{**\"name\": \"usedAccountId\",\"value\": \"False\"**\\}**\n\nTypically, the message found in the anti-fraud response is \"Object reference not set to an instance of an object,\" which prevents the transaction from being approved.\n\nFurthermore, this problem is commonly observed when a user removes their own card from the MyAccount page immediately after placing an order.\n\n\n#### Simulation\n\n\nFollow the aforementioned step, which involves deleting a card immediately after placing an order utilizing a legacy Antifraud.\n\n\n#### Workaround\n\n\nOpen a ticket for Product support team."}