If I understood well reading their announcement (but English is not my best), it effects only Website Payments PRO and not Website Payments. The difference is that with website payments PRO you must have your own merchant account and payments are done in your own site. In PRO there is no redirection to PayPal that's why they want the access to their API to be SHA-256. For this reason there is that "Merchant.....". But again I can be mistaken.
|