Pledge - WeGive Documentation

NPC represents pledges as GiftCommitment records with a FormalCommitmentType, distinguishing them from open-ended recurring commitments. No custom object is required.

GiftCommitment fields

WeGive field	NPC field	Sync	Notes
`donor.name`	`Name`	→	Generated as `Donor Name - Pledge`.
	`FormalCommitmentType`	→	Always `Written`.
`status`	`Status`	↔	Uses the commitment status mapping. Default `Active`.

GiftCommitmentSchedule fields

WeGive field	NPC field	Sync
`total_amount`	`TransactionAmount`	↔
`start_date`	`StartDate`	↔
`end_date`	`EndDate`	↔

Linkage (create-only)

WeGive field	NPC field	Notes
`donor.npc_id`	`DonorId`	Account ID of the supporter or company.
`campaign.npc_id`	`CampaignId`
`npc_id`	`Id`	Stored on the WeGive pledge.

Designation

A pledge has a single fund. It syncs as one 100 percent GiftDefaultDesignation regardless of the Fund allocations setting.

WeGive field	NPC `GiftDefaultDesignation` field
`fund.npc_id`	`GiftDesignationId`
100	`AllocatedPercentage`
`npc_id`	`ParentRecordId`

Pledge payments

Payments against a pledge are standard GiftTransaction records linked to the parent commitment through GiftCommitmentId. They follow the Gift Transaction mapping.

Pull behavior

Pledges are pulled from GiftCommitment where FormalCommitmentType is set. Recurring plans are pulled where RecurrenceType is set. A commitment can carry both.

​GiftCommitment fields

​GiftCommitmentSchedule fields

​Linkage (create-only)

​Designation

​Pledge payments

​Pull behavior