NXT Integration — Animated One‑Pager Demo

High‑level process flow Sources → Laravel engine ↔ Stripe (webhooks) → Blackbaud SKY API → RE NXT → Constant Contact

Main websitesource

Standard donation journeys (appeals, campaigns, landing pages).

Dataform + utm + consent

OutputDonation intent

Mobile appsource

App giving, Apple Pay / wallet flows, saved details.

Dataidentity + consent

OutputDonation intent

Event givingsource

Sponsorships, ticket add‑ons, event pages.

Dataevent + team metadata

OutputDonation intent

Team pagessource

Fundraisers, tribute pages, peer‑to‑peer.

Datafundraiser ID

OutputDonation intent

Other journeyssource

QR codes, third‑party embeds, micro‑sites.

Datasource + motivation

OutputDonation intent

Laravel donation enginesystem

Captures donor data, validates consent, sets idempotency keys, queues sync jobs.

Recordsdonations + donors

StoresNXT IDs (linking)

Stripepayments

Authorises & confirms payment success. No card data sent to NXT.

Keypayment_intent

Refstripe_charge_id

Raiser’s Edge NXTsystem of record

Matches/creates Constituents and writes Gifts with consistent mapping rules.

ObjectsConstituent + Gift

APIBlackbaud SKY

Retry queue & auditreliability

If NXT rejects/timeout: donation still completes, job retries safely (idempotent refs).

Idempotencydonation_id + stripe_ref

Statussynced / retrying / needs review

Constant Contactcomms

Automations triggered from clean CRM data (thank‑you, first‑time donor, re‑engage).

ChannelsEmail + SMS (consent)

TriggerGift/Consent updates

API call /

Live simulation near real‑time CRM writes with safe retries

Donations created

Payments succeeded

NXT synced

Retry queue

Where API calls go matching → create/update constituent → create gift → consent/comms

Constituent matching rules (highest confidence first)

1) Stored NXT constituent_id in the donation engine → direct link
2) Email match (optionally confirm name) → update missing fields safely
3) Fallback: name + postcode/address (if agreed)
4) No match → create new constituent + optional notification for review

Gift fields typically sent to NXT

Amount, currency, date/time • one‑off vs recurring • fund/designation • source/prompt • motivation • payment method • donation_id + stripe_reference (for idempotency) • URL + UTM fields • consent flags + timestamps.