PayPal has introduced a new API version, and very soon they are deprecating the version of API that we use currently.

Accounts connected before 10th of March might encounter errors after switching to the new API, if you notice this, you are welcome to ask the end users to reconnect the account.

Note - if you reconnect the account after they have errored out, you will not be paying both requisitions, as opposed to if you reconnect beforehand

Changes that might have a potential impact on user experience due to the switch:

Two-Step Authorization

• Authorization is now a two-step process. 

• In the first step, we obtain the encrypted "account_id" of PayPal customer. 

• In the second step, a separate authorization is created with the required scopes to access account data. 

• Potentially it will be necessary to authorize twice for the end user. 

Details response is no longer dynamic

• PayPal has completely removed the /details endpoint.

• We will use the data from the banks /accounts endpoint, to return it in our /details response, this means that these values will be hardcoded and will not change dynamically (however in, most cases the details never change, hence this is unlikely to have any impact on your processes)
  
  

Changes to the /balances Endpoint

• The bank no longer returns "reserved" balances.

• Only interimAvailable balances will now be accessible.

Uncertainty Around Currency Conversion & Fees

• Previously, General currency conversion transactions and secondary transactions were not returned via PayPal—this was expected behavior. The bank has not provided clarity on whether this has changed.

• Currency exchange transactions will not be returned, as this data has been moved to the transaction detail endpoint, which we do not support and will not support in the foreseeable future, as this would necessitate making a separate API request for each transaction.

• The recent API update moved fee data to the transaction detail endpoint as well. However, after our requests, some fee details appear to have been moved back to the main transaction endpoint. Due to sandbox limitations, we cannot test these scenarios locally, so potential changes should be kept in mind.

Changes to the /transactions endpoint

• The returned fields in /transactions have been changed by the bank, we have assigned as much information as possible the Berlin-Group standard to provide unified experience. 
  
  

Final notes

We understand not all of the upcoming changes are desired, and apologise for the inconvenience. Despite GoCardless voicing our concerns to PayPal, this has been their decision.