Boost recurring donations this giving season with the new upsell prompt!The following is a table showing the data mapping of a donation transaction from the Donations app to the payment processor and Salesforce Nonprofit Cloud. When sending data to Salesforce Nonprofit Cloud, Soapbox uses the Business Process API created by Salesforce which routes that data to the destination objects and checks for duplicates based on the Duplicate Rules your org has in place.
When Nonprofit Cloud's Business Process API processes the donation data sent by Soapbox, the following objects are the destination for the data:
- Person Account: Information about the donor
- Gift Transaction: Information about the donation transaction
- Payment Instrument: Information about the payment method used to process the donation.
- Gift Commitment, if a recurring donation
- Gift Commitment Schedule, if a recurring donation
- Gift Transaction Designations: child record created for Gift Transaction record, if a Designation has been selected by the administrator or donor
| Data | Salesforce Nonprofit Cloud | Payment Processor |
|---|---|---|
| Contact Information: First Name |
Yes - To Business Process API & mapped to new Person Account. Does not update existing Person Account. | No |
| Contact Information: Last Name |
Yes - To Business Process API & mapped to new Person Account. Does not update existing Person Account. | No |
| Contact Information: Email Address |
Yes - To Business Process API & mapped to new Person Account. Does not update existing Person Account. | Yes |
| Contact Information: Phone, if enabled |
Yes - To Business Process API & mapped to new Person Account. Does not update existing Person Account. | No |
| Contact Information: Organization, if enabled |
Yes - To Business Process API & mapped to new Organization Account. Does not update Organization Account, if matching Organization Account exists. If Organization is populated, Gift Type on Gift Transaction record is "Organizational/Household" or "Individual" if it is not. |
No |
| Custom Fields #1 - 4, if enabled | No | No |
| Anonymous, if enabled | Not supported by Business Process API at this time | No |
| Newsletter Sign Up, if enabled | Not supported by Business Process API at this time | No |
| Amount | Yes - To Business Process API & mapped to Current Amount and Original Amount on Gift Transaction. In addition, for initial recurring donations, mapped to Transaction Amount on Gift Commitment Schedule. |
Yes |
| Cover the Transaction Fee Amount | Yes - To Business Process API & mapped to Donor Cover Amount on Gift Transaction | No |
| Payment Frequency | Yes - To Business Process API for initial recurring donations & mapped to Transaction Period on Gift Commitment Schedule. If donation is one-time, no Gift Commitment or Gift Commitment Schedule will be created. |
Yes |
| Campaign | Yes - To Business Process API & saved as Campaign on Gift Transaction record | No |
| Outreach Source Code | Yes - To Business Process API & saved as Outreach Source Code on Gift Transaction record | No |
| Tribute Type (In Honor or In Memory), if enabled | Not supported by Business Process API at this time | No |
| Tribute Name, if enabled | Not supported by Business Process API at this time | No |
| Notification Type, if enabled | Not supported by Business Process API at this time | No |
| Notification First Name, if enabled | Not supported by Business Process API at this time | No |
| Notification Last Name, if enabled | Not supported by Business Process API at this time | No |
| Notification Email, if enabled | Not supported by Business Process API at this time | No |
| Notification Mailing Address, if enabled | Not supported by Business Process API at this time | No |
| Notification Mailing City, if enabled | Not supported by Business Process API at this time | No |
| Notification Mailing State, if enabled | Not supported by Business Process API at this time | No |
| Notification Mailing Postal Code, if enabled | Not supported by Business Process API at this time | No |
| Notification Mailing Country, if enabled | Not supported by Business Process API at this time | No |
| Notification Message, if enabled | Not supported by Business Process API at this time | No |
| Payment Form: Form of Payment |
Yes - To Business Process API & mapped to Type on Payment Instrument | Yes, if credit card |
| Payment Form: First Name |
Yes - To Business Process API & mapped to Account Holder Name on Payment Instrument | Yes |
| Payment Form: Last Name |
Yes - To Business Process API & mapped to Account Holder Name on Payment Instrument | Yes |
| Payment Form: Credit Card Brand, Credit Card Number, Expiration Date, and Security Code |
Yes - To Business Process API & mapped to Card Brand, Expiry Month, Expiry Year, and Last 4 on Payment Instrument | Yes |
| Payment Form: Billing Address |
No | Yes |
| Transaction Description | Not supported by Business Process API at this time | Yes, except for Braintree which doesn't capture Transaction Description |
| Transaction ID | Yes - To Business Process API and mapped to Gateway Reference on Gift Transaction | Yes. Generated by payment processor. |
| Subscription ID | Yes - To Business Process API and mapped to Gateway Reference on Payment Instrument | Yes. Generated by payment processor. |
| Transaction Date | Yes - To Business Process API & mapped to Transaction Due Date and Transaction Completion Date on Gift Transaction. In addition, for initial recurring donations, mapped to Start Date on Gift Commitment Schedule. |
Yes |
| Custom Salesforce Nonprofit Cloud Fields: Account object | Yes - To Business Process API and mapped to corresponding field on Account/Person Account. Does not update existing Account/Person Account. | No |
| Custom Salesforce Nonprofit Cloud Fields: Gift Transaction object | Yes - To Business Process API and mapped to corresponding field on Gift Transaction | No |
| Transaction Status | Yes - To Business Process API & mapped to Status on Gift Transaction | Yes. Generated by payment processor. |
| IP Address | No | No |
| Payment Processor | Yes - To Business Process API & mapped to Payment Processor Name on Payment Instrument as "Soapbox Engage" | No |
| Payment Gateway (e.g., Stripe, Authorize.net, etc) | Yes - To Business Process API & mapped to Gateway Name on Payment Instrument | N/A |