FeeAccount is causing "The given account is owned by a different program than expected"

[maxsap]

I am not sure if this is the best place to report this issue, I tried searching for feeAccount related issues here and did not find anything, so excuse me if I missed it.

• I am trying to add a fee on top of the swap.
• I am using the v6 swap API and specifying the feeAccount parameter which is the public key of the wallet receiving the fees
• The swaps work fine if I do not specify the feeAccount, but fail if I do example https://solscan.io/tx/2aHgpigFGEJJn4rWNoKWKj5uuiNmT5YoaMJUapp3TVidrV7xSTzKpFYfturGEjwoaTNGVqRcPoC64Lzst5G9xoCT

Initially I though this has to do with ATA missing hence as you can see in the transaction above I am trying to alter the resulted transaction and add the necessary instructions.

The docs are saying Fee token account, it can be either the input mint or the output mint for ExactIn and only the input mint for ExactOut, it is derived using the seeds = ["referral_ata", referral_account, mint] and the REFER4ZgmyYx9c6He5XfaTMiGfdLwRnkV4RPp9t9iF3 referral contract (only pass in if you set a feeBps and make sure that the feeAccount has been created). It doesn't support Token2022 tokens.

which is not really clear to me what it means.

So the questions that I have is:

• what are those referral accouts mentioned in the docs mean? where can I find them
• can I specify my own address for getting the fees or can someone please point me to an example of how to do that?

[contribution-hub]

Reach out to the Support page Portal to report your request and get more details by initiating a live chat with an agent through the chat button on the platform. Access the portal here: Support Portal.

@maxsap
Note: Click the chat button to start a conversation with an agent for assistance.