Martin, status update, i was able to figure out the issue. It seems a bit counter intuitive from other smart contracts I have interacted with thus far. (for others who may have the same question here is what I did) in the command i had to replace the contract call address with my own, when usually other contracts calls address i interacted with in the past was the SC address its self. here is the working erdpy command: erdpy --verbose contract call erd1cm4fukzun6t96nfwv4wf8np7pc27egawjxfwnhlqr8qjdlf8k7hqpxa0c6 --function="MultiESDTNFTTransfer" --arguments 0x00000000000000000500e7283876b9cebf5e885a63795bc8271543a5acfb7ceb 0x02 0x5745474c442d643763366262 0x 0x0de0b6b3a7640000 0x4d45582d646332383963 0x 0x9fab2ed1405aa15810e5 0x6164644c6971756964697479 0x0dbd2fc137a30000 0x9e126e59661c48b0c90b --chain="D" --pem="/home/anon/Desktop/elrond-dev/maiar.erdpy.demo/test.pem" --gas-limit=80000000 --proxy="https://devnet-gateway.elrond.com" --recall-nonce --send when this one is the one i was furiously trying that failed: erdpy --verbose contract call erd1qqqqqqqqqqqqqpgquu5rsa4ee6l4azz6vdu4hjp8z4p6tt8m0n4suht3dy --function="MultiESDTNFTTransfer" --arguments 0xc6ea9e585c9e965d4d2e655c93cc3e0e15eca3ae9192e9dfe019c126fd27b7ae 0x02 0x5745474c442d643763366262 0x 0x0de0b6b3a7640000 0x4d45582d646332383963 0x 0x9fab2ed1405aa15810e5 0x6164644c6971756964697479 0x0dbd2fc137a30000 0x9e126e59661c48b0c90b --chain="D" --pem="/home/anon/Desktop/elrond-dev/maiar.erdpy.demo/test.pem" --gas-limit=80000000 --proxy="https://devnet-gateway.elrond.com" --recall-nonce --send notice the difference in the address used after "erdpy --verbose contract call " I replaced the SC address with my own and this was able to pass the sender and receiver address to the same, which i am assuming is how this SC was programmed to see when used, correct?