Details
-
Type:
Sub-task
-
Status: Done/Fixed
-
Priority:
Major
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.2.0
-
Fix Version/s: 4.2.0
-
Component/s: CiviContribute, CiviMember
-
Labels:None
Description
- If the associated processor supports changes to subscription amount and number of installments via api, then recurring contribution initial notification, as well as subsequent receipts should include a separate link to "Edit Recurring Contribution Amount or Installments". Link includes checksum and loads an edit form with fields to update "Recurring Contribution Amount" and "Number of Installments" (both are pre-filled).
- Add same link (but w/o checksum) to Contact Dashboard - recurring contribution selector if supported by associated processor.
- If processor request succeeds, insert an Activity record:
- Add new activity type - "Update Recurring Contribution"
- Activity source contact is logged in / authenticated via checksum user (which should be the donor). Target is also the donor.
- Activity description should include original "processor_id" and any "update" tracking transaction id's received from processor
- Send update notification to donor. We can use same message template as for back-office edit.
