Transaction Data Mapping
Detailed field mapping for transactions and gifts between WeGive and DonorPerfect systems.
Transaction Data Mapping
This document details how donation transactions are mapped between WeGive and DonorPerfect, including one-time gifts, recurring donations, and tribute gifts.
DonorPerfect Table Reference
Primary Table: dpgift (Gift Records)
WeGive Model: Transaction
Sync Direction: WeGive → DonorPerfect (Push Only)
Core Transaction Fields
Primary Identifiers
Financial Information
Amount Processing
Critical: WeGive stores amounts in cents (integer), DonorPerfect uses dollars (decimal). Automatic conversion and fee handling applied.
| WeGive Field | DonorPerfect Field | Calculation | Notes |
|---|---|---|---|
amount | @amount | (amount - fee) / 100 | Net donation amount in dollars |
fee | Not directly mapped | Used in calculation | Processing fee deducted |
destination.currency | @currency | Direct mapping | Currency code (e.g., ‘USD’) |
Amount Calculation Examples
Date and Timing
| WeGive Field | DonorPerfect Field | Format | Notes |
|---|---|---|---|
created_at | @gift_date | MM/DD/YYYY | Transaction processing date |
Date Format: DonorPerfect requires MM/DD/YYYY format. Other formats will cause sync failures.
Fund and Campaign Attribution
Fund Designation
Gift Types and Classifications
Recurring Donation Handling
Tribute and Memorial Gifts
Gift Narrative and Notes
Automatic Gift Description
Data Flow Process
Transaction Sync Workflow
Transaction Created
New donation processed in WeGive system
Donor Validation
Verify donor exists in DonorPerfect (create if needed)
Amount Calculation
Calculate net amount after fee deduction
Gift Record Creation
Create gift record in DonorPerfect dpgift table
ID Assignment
Store DonorPerfect gift ID back in WeGive
Error Handling
Transaction Sync Errors: Failed transactions are automatically retried with exponential backoff.
| Error Type | Cause | Resolution |
|---|---|---|
| Invalid Donor | Donor doesn’t exist in DonorPerfect | Auto-create donor, retry transaction |
| Invalid GL Code | Fund GL code not found | Create GL code, retry transaction |
| Amount Validation | Negative or zero amount | Skip transaction, log error |
| Date Format | Invalid date format | Correct format, retry |
| API Timeout | DonorPerfect API unavailable | Retry with backoff delay |
API Operations
DonorPerfect Gift Creation
Query Operations
Sync Configuration
Transaction Sync Settings
Performance Considerations
High Volume Processing
- Batch processing for multiple transactions
- Rate limiting to prevent API overload
- Queue management for peak periods
- Automatic retry for failed syncs
Error Recovery
- Failed transactions automatically retry
- Exponential backoff prevents system overload
- Manual retry options in dashboard
- Comprehensive error logging
Data Quality and Validation
Pre-Sync Validation
Monitoring and Reporting
Troubleshooting
Common Transaction Sync Issues
Related Documentation
Donor Mapping
Learn how donor records are synchronized
Recurring Donations
Understand recurring gift and pledge mapping
Fund Management
GL code and fund designation mapping
Configuration Guide
Configure transaction sync settings
For additional help with transaction data mapping, contact our support team at [email protected].