nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JustGiving-NXT Implementation?

Debi Spencer

Hi quickly seeking resource who has implemented JustGiving with NXT and can provide some input. We have NXT but never use it and prefer database view so NXT batch will be new. I feel documentation is lacking in several areas such as gift field mapping. Also interested in your choice of payment processor--BBMS vs Blackbaud Giving vs Blackbaud Giving Checkout and why. We use BBMS today to process Luminate and database gifts. thank you!

Find more posts tagged with

Comments

Alex Wong

@Debi Spencer
very similar to us.

We use Luminate Online as the main donation platform, we bring those gift in with Import-O-Matic but using custom code as our org demands gift coding to be very specific that normal import profile doesn't handle. (i.e. gift coding of campaign, gift subtype, and reference will depend on constituent code that designate which of the 25 chapters we have gets credit).

Not sure what you mean by Blackbaud Giving and Blackbaud Giving Checkout, we use BBMS as the payment processor for all of our Blackbaud platform: Online Express (for event registration, starting to transition to RE NXT Event Registration), RE NXT Event Registration, Luminate Online, and JustGiving.

JustGiving > RE NXT integration is nice and bad at the same time. RE NXT webview gift batch is not up to par yet (even though we should be getting some major enhancement to this shortly). There is default campaign, fund, appeal, package that can be set, and then there is override that can be done on PER JustGiving Campaign perspective. Note: JustGiving Campaign are campaigns created internally, vs JustGiving Fundraising Page is donor initiated. Meaning you have no way to control JustGiving Fundraising Page's campaign, fund, appeal, package. In both cases, you are not going to be able to specify other defaults: Gift Subtype, Reference, Gift Attribute/Custom Fields. Currently, I use Power Automate that will modified all of the JustGiving gifts as they get created when the webview batch is approved. There is a learning curve to do this though and not many do this.

Keith Wilson

@Debi Spencer We have JustGiving integrated with NXT. We already used BBMS for gift processing so it made the most sense to keep BBMS as the gift processor for JG. I am not well versed on the Blackbaud Giving Fund vs Blackbaud Checkout, but I know those offer advantages as to platform and processing fees and how/when funds are disbursed to your org.

As for gifts coming into Web View batch, there will be a slightly different processing but it is fairly easy to figure out. One thing to note here though, is you cannot get a Batch Commit Control Report from a web view batch--but seriously, do you really need those?? ?

For data purposes, NXT offers Constituent Data Review for online gifts to avoid creating duplicate records, however, JustGiving transactions will not go through Data Review and may create a duplicate record if the embedded matching criteria fails to identify the existing constituent. Just be sure to do routine data clean ups to identify those duplicates--which you are probably already doing.