Pause, resume and end sponsorships
Open a sponsorship detail and verify the sponsor, target, commitment and period before choosing a status action. You need sponsorship management authority; commands use the current version.
Actions
| Action | Procedure | Result |
|---|---|---|
| Pause | Open ACTIVE sponsorship; choose Pause and follow the displayed prompt | PAUSED; history retained |
| Resume | Open PAUSED sponsorship; confirm beneficiary is still sponsorable; choose Resume | ACTIVE if eligible |
| End | Choose End and supply the required reason | ENDED; terminal record with reason and retained history |
Reload detail after success. A paused beneficiary sponsorship whose target is no longer sponsorable cannot resume; transfer or end it. Ending does not delete the record, refund money or cancel a bank mandate. There is no ordinary reopen transition.
Dates and money are separate
The commitment's start/end describe its period. Do not assume reaching the end date automatically runs a status change, collects a final payment or creates a reminder. Status actions are explicit in the current workflow.
Example: A sponsor asks to pause GBP 30 monthly support. Pausing records the relationship decision. Staff must separately handle any external standing-order arrangement through their approved process; this application does not contact the bank.
Changing commitment details
The backend supports a versioned sponsorship change request for fund, amount, currency, frequency, dates and notes, with a required reason. The current browser detail does not provide a general commitment-edit form. It provides status, transfer and sponsor-update actions. Do not describe a missing browser Edit commitment action as available.
For an approved integration/support change, the existing API is PUT /api/v1/charity/sponsorships/{id} and uses the current version plus the complete required change fields. Sponsor and target are not editable through that request. Target changes use transfer to a facility/programme; do not overwrite historical relationships.
Recovery
If another user changed the record, reload the actual state/version and reconcile before retrying. If a response is lost, inspect current detail/history before another status action. If End is refused for a missing reason, provide the actual approved explanation; a blank prompt is not a successful end.
Ended sponsorship history stays intact. Existing sponsor updates have their own status rules; ending is not a promise that every previously drafted or approved update is automatically withdrawn or blocked. Review outstanding communications separately under the organisation's process.