How DAF Connect works.
Corporate giving programs that process more than a dozen non-profit partners per year need a repeatable, defensible intake process. DAF Connect replaces ad-hoc PDF forms, manual EIN lookups, and scattered email threads with a single embedded workflow — from application to reviewer decision.
I. The embed
Enterprise admins paste a single script tag and iframe snippet into any web page — a Drupal intranet, a Sharepoint site, a hand-coded giving landing page. There is no backend to configure on your side. The iframe auto-resizes to its container via a small postMessage listener. The embed is built, but production does not yet allow the form to be framed on another site — it renders in your page once the edge header configuration is deployed. Until then, the same form is available today at your hosted onboarding URL, which you can link to from any page.
From the Embed Manager dashboard, admins set the enterprise brand colors, logo, and intro copy that non-profits see when they open the form. Required fields, optional fields, and up to 10 custom questions are configurable. Domain allowlisting restricts which origins can embed the iframe.
<iframe src="https://daf-connect.com/embed/demo-acme-corp" style="width: 100%; min-height: 800px; border: 0; border-radius: 8px; display: block;" allow="clipboard-write; camera; microphone" title="Non-profit onboarding" ></iframe> <script src="https://daf-connect.com/embed-resizer.js" async></script>
II. Collection and verification
Non-profits work through an 11-step intake form: legal name, company verification (EIN, address, contact), banking details, signer identity, mission, leadership, financials, custom questions, documents, review, and submission. People screening runs reviewer-side, in the verification pipeline, rather than as a step the applicant fills in. A human-verification challenge presents the moment the form opens, and the form auto-saves drafts so applicants can return to finish later. Required fields are validated before each step advances.
Once a submission is filed — through the embed, the hosted intake link or the nonprofit portal — its move to submitted starts the verification pipeline automatically, and a reviewer can re-run it from the console at any time. The checks that run today: IRS 501(c)(3) status lookup, EIN format validation, OFAC SDN screening, HHS OIG exclusion screening, document validation, IRS registry data, AI-driven web research, applicant IP intelligence, drift detection, and a composite trust score. Further checks are built and switch on when enabled for your platform or account: SAM.gov debarment screening and document virus scanning (each waiting on its API key), entity-graph ring checks (once the platform hashing key is set), and bank account ownership verification through Stripe Financial Connections (switched on per customer).
- IRS 501(c)(3)
- EIN format
- OFAC SDN
- HHS OIG
- Documents
- IRS registry data
- Web research
- IP intelligence
- Drift
- Trust score
III. Review and decision
Reviewers see a verified profile: trust score, IRS status, OFAC result, document validation, and a risk tier. They can inspect uploaded documents directly in the browser, add internal annotations, and request replacement files from the non-profit — all without leaving the dashboard.
Every decision — approve, reject, or request more information — requires a written reason. That reason is stored in the audit log, visible to the non-profit in their submission status page, and retrievable by your compliance team at any time.
- IRS 501(c)(3)Active · Pub 78 listed
- OFAC screeningClear — no SDN match
- DocumentsValidated · virus-scanned
- Bank ownershipAccount title matches legal name
- Risk tierLow · ACH eligible
What we don't do.
- Your rules stay yours
We don't write your grant program rules. Your eligibility criteria, dollar amounts, and approval workflows are yours to define.
- We never touch the money
We don't disburse funds. Your existing payments stack — ACH, wire, check — handles disbursement. We only provide the compliance layer.
- Inputs, not verdicts
We don't make approval decisions. The trust score and AI recommendation are inputs to your team's judgment, not a substitute for it.
- Tenant data stays isolated
We don't share applicant data across enterprises. Each tenant's data is isolated at the query level.