title: Is the Payout (REST api) functionality meant to replace Mass Pay (classic merchant api)?
body: <p>It appears as though the newish <code>payout</code> (including batch) endpoints more or less match up with the older <code>MassPay</code> functionality. The fee structures seem to match up, with <code>payouts</code> having an advantage for transfers within the US. Even some of the events get logged as <code>MassPay</code>. It appears for all practical purposes that <code>payouts</code> is meant to replace <code>MassPay</code>.</p>
  
  <p>What I haven't been able to find is a definitive statement from PayPal to that effect. I have looked for an announcement from when <code>payouts</code> was introduced, through technical and general support documentation, and generally in every place I could think of.</p>
  
  <p>Obviously, the LACK of such a statement could say something all on its own. It just doesn't seem like it should be the case. </p>
  
  <p>Has anyone seen an official statement that I can refer to? Or, if PayPal folks are listening, is such a statement possible?</p>
  
  <p>Something along the lines of, "PayPal is encouraging developers to build new systems needing MassPay functionality using the Payout endpoints of the REST API"</p>
  
  <p>Thanks!</p>