> ## 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.

# Transaction Data Mapping

> Detailed field mapping for gifts/transactions between WeGive and StudioEnterprise

# Transaction Data Mapping

This page covers how WeGive Transactions map to StudioEnterprise Gifts.

**StudioEnterprise Object**: Gift (transaction/document record)
**Sync Direction**: Bidirectional (pull on by default; push optional, off
by default, create-only)

## Core Identity Fields

| WeGive Field | StudioEnterprise Field | Notes |
| - | - | - |
| `donor_direct_id` | Document Number | Primary correlation key — StudioEnterprise has no separate "Gift ID," the Document Number is the identifier |

## Push Behavior

<Note>
  **Only settled gifts are pushed.** A transaction is only sent to
  StudioEnterprise once its WeGive status is "success" — pending, failed, or
  otherwise unsettled transactions are never pushed.
</Note>

* Gifts are sent to StudioEnterprise as **already-processed** — WeGive does
  not ask StudioEnterprise to charge the donor. Payment processing happens
  entirely within WeGive.
* **Once pushed, a gift is treated as immutable.** WeGive does not update a
  transaction record after it's been successfully synced.
* Before pushing a new gift, the integration first pushes the donor account
  (if not already synced) and resolves the campaign/fund references, so the
  gift can reference real StudioEnterprise IDs.
* A refund on an already-synced gift is sent as its own separate
  follow-up sync (a full refund), rather than modifying the original gift
  record.

## Fields Sent on Push

| WeGive Concept | StudioEnterprise Field | Notes |
| - | - | - |
| Donor | Account | Resolved/created first if not already synced |
| Amount(s) / designations | Donations | One or more donation lines |
| Payment details | Payments | Payment method line |
| Campaign | Source | Resolved from the transaction's campaign, or the configured default Source Code |
| Currency | Currency | Set per-integration configuration |
| Tax status | `isTaxExempt` | Inverse of WeGive's tax-deductible flag |
| Contact method | Fixed to `WEB` | All WeGive-originated gifts are marked as web-originated |

<Note>
  Gifts pushed from WeGive are grouped into a batch at push time (StudioEnterprise's
  own batch-import mechanism). If the push fails, WeGive cleans up the
  empty batch rather than leaving a stray batch record behind.
</Note>

## Pull Behavior

On pull, gift/transaction records are read at the designation-line grain
and grouped by Document Number (one WeGive transaction may correspond to
multiple designation lines in StudioEnterprise). Each transaction record
carries references back to:

* The Account (donor) that gave the gift
* The Project (fund) designation
* The Source Code (campaign) attribution
* The parent recurring plan, if this gift was produced by a sustaining/recurring plan

## Payment Method Mapping

StudioEnterprise represents payment types with short codes. WeGive maps
these into its own payment-method categories (check, card, cash,
bank/ACH-style debit, wallet payment types, and other/adjustment types).
The exact mapping is confirmed against your organization's own
StudioEnterprise configuration during setup, since payment-type vocabularies
can vary by customer.

## Not Yet Supported

<AccordionGroup>
  <Accordion title="Split-tender payments">
    A single gift paid across more than one payment method on the
    StudioEnterprise side is not yet represented — the primary payment method
    is used. Planned for a future phase.
  </Accordion>

  <Accordion title="Multi-fund gift allocations">
    A single gift split across multiple fund designations is not yet supported
    in the DonorDirect sync.
  </Accordion>

  <Accordion title="Transaction status is still being finalized">
    StudioEnterprise's own gift-status semantics (what precisely counts as
    "completed" versus other states) are still being confirmed as part of this
    integration's rollout.
  </Accordion>
</AccordionGroup>

## Related Documentation

<CardGroup cols={2}>
  <Card title="Recurring Donation Mapping" href="/external/onboarding/donordirect/data-mapping/recurring-donation">
    See how recurring plans link to the gifts they produce
  </Card>

  <Card title="Donor Mapping" href="/external/onboarding/donordirect/data-mapping/donor">
    Learn how donor accounts are resolved before a gift is pushed
  </Card>
</CardGroup>

For additional help with transaction mapping, contact our support team at
[support@wegive.com](mailto:support@wegive.com).


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