paypal - Is the Payout (REST api) functionality meant to replace Mass Pay (classic merchant api)? -
it appears though newish payout
(including batch) endpoints more or less match older masspay
functionality. fee structures seem match up, payouts
having advantage transfers within us. of events logged masspay
. appears practical purposes payouts
meant replace masspay
.
what haven't been able find definitive statement paypal effect. have looked announcement when payouts
introduced, through technical , general support documentation, , in every place think of.
obviously, lack of such statement on own. doesn't seem should case.
has seen official statement can refer to? or, if paypal folks listening, such statement possible?
something along lines of, "paypal encouraging developers build new systems needing masspay functionality using payout endpoints of rest api"
thanks!
the payouts api brand new rest-based api replaces mass payments classic apis. payouts has more features compared mass payments.
businesses need send disbursements 500 recipients in single api call use payouts api.
these new api’s close product gap between paypal payouts capabilities, , our new crop of competitors. , crucially new payouts api’s solve numerous product problems inherent in mass payments apis
what payouts api have on mass payments api:
- us , ca domestic pricing - $0.25 usd flat fee domestic payouts, , $0.32 cad ca domestic payouts
- send 500 payouts in single api call
- duplicate checking – paypal can check duplicate payout requests
- new single payout capability – paypal return transaction status directly in payouts call response -1:1 mapping of entire batch’s requests – retrieve via api call status of each request in batch, when ever want, how want
- on-demand reporting – allows query payouts time, status or recipient
what doesn’t payouts have?
payouts not allow manual file uploading.
https://developer.paypal.com/docs/integration/direct/payouts-overview/
Comments
Post a Comment