eosio.token contract, the
transfer action makes the sender pay for the RAM if a new account has to be created for the receiver. I would like to make a contract where is the issuer of the token the one that always pays. What permissions would the issuer need to set in order to allow the table
emplace method call to receive her as ram payer albeit her not being involved in the current transaction?
Looks like the 3rd party must be signing the transaction, there is no way to delegate the permission if I'm reading this right
So either one of the accounts which have a signature in transaction can pay for RAM (see Ariel's answer), or contract account itself can pay for it. Source.