I have seen so many comments and posts from people suffering from the PAB.DE.0009 error, and so have I. After 5+ hours of phone calls (including waiting time) and my trial and error, I have finally resolved this issue. This post is to share my method and to report a glitch I'd like to report to ATO.
The problem I had is that when you try to link ATO to myGov, you will be asked to agree to their terms and conditions. Then, you will move to Step 2, where you put your information like name, TFN, address, etc. As my profile on the ATO's record was old and incorrect, I suddenly got a PAB.DE.0009 error after failing a few attempts. Whenever I tried again, it did not even let me put my information in Step 2.
What you should do:
- Call 1800 467 033. It is the ATO's identity-related line. Compare yourself to your profile on the ATO's record. If there is a discrepancy and you have a PAB.DE.0009 error, there must be an extra security layer, which you need to ask them to remove.
- Wait several days for your record to be updated, and then call them again to get a linking code. It expires in 24 hours.
- On the same day, log in on myGov. Go to My account -> Account settings and disconnect Digital Identity. I realised that if you disconnect Digitial Identity, you will be prompted to input your information in Step 2. For me, I was connected to Digital Identity only, but you may disconnect Passkeys or myGov PIN, only if disconnecting Digital Identity does not work. I changed this setting so that when I tried to log in, I received a code via message.
- Now, go to Step 2! You will be prompted to input your information. You need to put your name and birthday correctly, but you put the wrong TFN and wrong address. If you put all the correct information, you will still receive the PAB.DE.0009 error and will not be prompted to proceed. Now, you click the Next button.
- You already put the wrong information, so you will now see a Use a linking code option below. Click that, input the linking code, and then you are all done. Congratulations!
Now to ATO,
I am not a professional software engineer, nor do I work in this industry. However, I have learnt web development for personal interest and here is what I have found based on that. It may not be an error or a glitch, but it may be worth looking at.
It seems that when a user enters their name, DOB, TFN, and address in Step 2 and clicks the Next button, a POST method named 'tfn' is triggered with the payload of that user information. However, as I explained, those with this PAB.DE.0009 error are not prompted to input their information and cannot proceed further from Step 2. That is, once these users check the agreement tick box in Step 1 and click the Next button to proceed to Step 2, this 'tfn' POST method is automatically triggered with 'null' values for answerID "Tfn" and "FullAddress", resulting in the 422 status code. I was confirmed that my security layer was removed but I still had this same issue.