> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Billing Addresses Flow From Checkout to Your CRM

> Explains how a donor's billing address is collected during checkout (controlled by the ask_full_billing_address setting), stored on the donor record, and automatically synced to connected CRMs like Salesforce NPSP or Nonprofit Cloud.

# How Billing Addresses Flow From Checkout to Your CRM

When a donor completes a gift through your checkout, the billing address they provide follows an automatic path: it is saved to the donor's record in WeGive and then pushed to any connected CRM integration.

## Controlling whether the full address is collected

Each checkout has a **"Ask Full Billing Address"** toggle in its settings. This controls what the donor sees:

* **On** — The checkout shows a complete billing address form: name, street address, city, state, zip/postal code, and country.
* **Off (default for checkouts)** — The checkout shows only the donor's name and zip/postal code. Street, city, state, and country fields are not displayed.

You can find this setting in the checkout's Billing settings section in your dashboard. Pledge create forms default to collecting the full billing address.

If you need complete address data for tax receipting, CRM sync, or mailing purposes, turn this toggle on.

## What happens after the donor submits

Once the donor completes their gift:

1. **The address is saved** to the donor's billing address record in WeGive. Each donor can have one billing address and one mailing address.

2. **CRM sync fires automatically** — WeGive detects the address change and pushes the updated donor data to every connected CRM integration. You do not need to manually trigger a sync.

3. **The address appears on the CRM contact record** — the exact field mapping depends on your CRM:

### Salesforce (NPSP)

WeGive maps addresses to Salesforce Contact fields:

| WeGive | Salesforce Contact |
| - | - |
| Mailing address | Mailing Address fields (MailingStreet, MailingCity, MailingPostalCode) |
| Billing address | Other Address fields (OtherStreet, OtherCity, OtherPostalCode) |

State and country fields sync through your configured mapping rules rather than by default, because Salesforce picklist settings vary by organization.

If your organization uses NPSP household accounts, the Contact address propagates to the household Account automatically through NPSP's built-in address management. WeGive writes to the Contact, and NPSP handles the household-level propagation.

### Nonprofit Cloud (NPC)

Address fields on NPC Person Accounts sync through your configured mapping rules. Household membership is managed via the Account parent-child hierarchy.

## Common questions

**Why is the billing address missing on some donations?**
Check whether the checkout that collected the gift has "Ask Full Billing Address" turned on. If it is off, the checkout only collects name and zip — the full street/city/state fields are not presented to the donor.

**Does updating an address in WeGive push to Salesforce?**
Yes. Any change to a donor's billing or mailing address in WeGive automatically triggers a CRM sync to all connected integrations.

**Does the address sync work in both directions?**
Address data syncs from WeGive to your CRM when addresses change in WeGive. Addresses also import from your CRM to WeGive during scheduled sync pulls. However, household-level changes made in WeGive do not push back to Salesforce (household sync is pull-only from Salesforce to WeGive).

**Why does my donor's `updated_at` timestamp not reflect an address change?**
Address records are stored separately from the donor record. An address-only change updates the address itself but does not bump the donor record's last-modified timestamp. CRM sync still fires correctly regardless of this — the sync is triggered by the address change, not by the donor timestamp.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.