The transaction notifications sent by PayPal will slightly change. We need to adapt our application to be able to process them. Please refer to the [investigation documentation](https://docs.google.com/document/d/1UzOKLG9mk9kWO3wRKZKGBMevnVJc3qdVYNNY9nb-u8o/edit#heading=h.qeqkx356gbyr) for more details.
**Acceptance Criteria**
- Payment notifications for recurring payments (both from legacy and API) can be processed by our application.
**Implementation Notes**
- The transaction types (`txn_type`) for recurrring payments will be:
- `recurring_payment_profile_created` (you can ignore this, it might get relevant later when we handle memberships)
- `recurring_payment`
- The transaction type (`txn_type`) for recurrring payments will be `cart`
- The Fundraising Application needs to be changed to handle those new transaction types.
- Create a new service class (e.g. `ConfirmationUseCaseDispatcher`) for looking up donation/membership ID and type using IPN data: It should look at the transaction type to determine the name of the ID field (`recurring_payment_id` for `recurring_payment`, `txn_id` for `cart` ), use `payment_paypal_identifier` to get a payment id, `payment_id` field in donation and membership tables to get to the type (donation/membership) and the entity id. Create a matching use case:
- throw a "not implemented" exception for memberships
- Prepare the `cart` case, in the service class. It won't do anything yet, but we can use the code when we implement {T344839}
- Do the current lookup of the donation (by Id) for all other `txn_type` values
- Construct the use cases with a "lenient" authorizer implementation that always returns `true` for `systemCanModifydonation`: You can ignore the `updateToken`, we have other means to make the end point secure and if the donation/membership doesn't exist, the use case will throw an exception anyway
- Add test cases in `HandlePayPalPaymentNotificationRouteTest` that check the new payment data
- `recurring_payment` & matching `recurring_payment_id` for donations should be handled
- `recurring_payment` & non-matching `recurring_payment_id` should be dropped (and logged)