How to Automate Charity Verification for a Donor-Advised Fund Platform

Recommended verification flow

1. Normalize the recipient EIN.
2. Call the Nonprofit Check Plus API.
3. Confirm ein and organization_name.
4. Review pub78_verified.
5. Review organization_type, deductibility_limitation and deductibility_status_description.
6. Review foundation classification fields.
7. Check revocation_code, revocation_date and reinstatement_date.
8. Review ofac_status.
9. Review source freshness and conflict signals.
10. Apply the DAF platform's approve, review or stop policy.

Example request(s)

curl --request GET \
  --url https://entities.pactman.org/api/entities/nonprofitcheck/v1/us/ein/YOUR_EIN \
  --header 'Authorization: Bearer YOUR_API_KEY'

Implementation note: The endpoint name above reflects the Pactman single-EIN Nonprofit Check endpoint used in Pactman's Production/Customer Environment.

curl --request POST \
  --url https://entities.pactman.org/api/entities/nonprofitcheckbulk/v1/us/eins \
  --header 'accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '[
    "YOUR_EIN_1",
    "YOUR_EIN_2",
    "YOUR_EIN_3",
    "YOUR_EIN_4",
    "YOUR_EIN_5"
  ]'

Implementation note: The endpoint name above reflects the Pactman bulk-EIN Nonprofit Check endpoint used in Pactman's Production/Customer Environment. You can have at most 50 EINs in a bulk-EIN Nonprofit Check endpoint request.

What your application should evaluate

Example decision logic

A DAF workflow might:

• resolve the recipient by EIN;
• require the Pub. 78 and contribution signals relevant to the platform;
• evaluate foundation type;
• review revocation and reinstatement;
• screen OFAC;
• preserve source dates and conflicts; and
• produce the platform's approval or review outcome from documented rules.

For scheduled portfolio or grantee-list reviews, the bulk endpoint can apply the same logic to up to 50 EINs per request.

Important: The current API does not contain a daf_eligible field. DAF eligibility is a platform decision based on the returned source fields and the platform's own policy.

Why use a consolidated nonprofit verification API?

DAF workflows can require charity identity, deductibility context, foundation classification, revocation and sanctions screening.

Pactman returns those dimensions in one response.

One normalized response

Evaluate recipient identity and compliance signals without separate source integrations.

Separate source signals

Keep Pub. 78, foundation, revocation and OFAC evidence distinct.

Reusable compliance rules

Apply the same charity-review policy across contribution recommendations and recurring recipient checks.

Developer-friendly automation

Turn EIN-based charity checks into deterministic workflow steps and bulk review jobs.

Frequently asked questions

Does Pactman return a daf_eligible field?

No. The current supplied schema returns source signals, not a DAF-specific approval result.

Which fields should I use for Pub. 78 contribution context?

Use pub78_verified and the fields inside organization_types.

Should foundation classification be kept separate?

Yes. Use the foundation-specific fields instead of inferring foundation type solely from Pub. 78 or BMF subsection.

Can OFAC screening run in the same request?

Yes. ofac_status is returned alongside the IRS-related fields.

Related Pactman artifacts

• How to Check Whether Donations to a Nonprofit Are Tax Deductible
• How to Combine IRS Verification and OFAC Screening in One API Workflow
• How to Build a Nonprofit Compliance Check Into a Fintech or Donation Platform

Next step

Map the DAF platform's recipient policy to Pactman's identity, Pub. 78, foundation, revocation and OFAC fields, then reuse the same rules for single and bulk checks.