Occasionally, we send transaction messages to the Payee. If the Payee was online, this worked properly via the client. If the client was null, it uses the agentID to try to send a message which can be received offline. However, when we wrote this, we were only sending messages to the payer and when we added in the offline option, we just pulled the PayerID from the transaction, forgetting that we sometimes message the Payee. This fixes this by adding a variant of the messaging function which takes the ID. When we are messaging the payee, we supply the id to override the default behavior.
Occasionally, we send transaction messages to the Payee. If the Payee was online, this worked properly via the client. If the client was null, it uses the agentID to try to send a message which can be received offline. However, when we wrote this, we were only sending messages to the payer and when we added in the offline option, we just pulled the PayerID from the transaction, forgetting that we sometimes message the Payee. This fixes this by adding a variant of the messaging function which takes the ID. When we are messaging the payee, we supply the id to override the default behavior.