How to Add OFAC Screening to a Nonprofit Verification Workflow

Direct answer

Add OFAC screening as a separate step in the nonprofit verification decision layer.

After confirming ein and organization_name, inspect ofac_status. Then evaluate IRS BMF, Pub. 78 and revocation signals independently. Your application can combine policy outcomes, but the underlying source signals should remain separate.

Recommended verification flow

Normalize the EIN.
Call the Nonprofit Check Plus API.
Confirm ein and organization_name.
Evaluate BMF status.
Evaluate Pub. 78 status when relevant.
Evaluate revocation and reinstatement fields.
Read ofac_status.
Apply your OFAC policy.
Combine policy outcomes without merging source fields.
Store source-level results needed for audit or review.

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

Signal	Why it matters	Typical application decision
`ofac_status`	Supplies organization-level OFAC screening status.	Continue, review or stop according to your sanctions policy.
`bmf_status`	Supplies BMF presence.	Evaluate tax-status context separately.
`pub78_verified`	Supplies Pub. 78 presence.	Evaluate contribution context separately.
`revocation_code` / `revocation_date` / `reinstatement_date`	Supplies revocation history.	Apply revocation policy independently of OFAC.
Organization identity	`ein` and `organization_name` bind the screening result to the intended nonprofit.	Confirm identity before policy evaluation.

Example decision logic

A combined workflow might:

verify organization identity;
evaluate IRS eligibility according to the use case;
inspect ofac_status;
route OFAC concerns independently;
preserve revocation and contribution signals; and
produce an application-level outcome from documented rules.

Important: Do not reduce IRS and OFAC results to one opaque field before retaining the source signals your policy needs.

Why use a consolidated nonprofit verification API?

A consolidated response reduces integration overhead while still preserving source boundaries.

One normalized response

Receive IRS and OFAC signals from one API call.

Separate source signals

Keep sanctions screening distinct from tax-status and deductibility checks.

Reusable compliance rules

Apply the same workflow across donations, grants and fintech onboarding.

Developer-friendly automation

Trigger review or block actions from explicit source fields.

Frequently asked questions

Which field should drive the OFAC step?

Use ofac_status.

Should OFAC be evaluated before or after IRS checks?

The supplied files do not mandate a universal order. Keep both as explicit workflow steps.

Can OFAC status replace nonprofit IRS verification?

No. They answer different questions.

Does the current API provide one universal compliance pass/fail field?

No. The supplied schema exposes separate source fields.

Next step

Add ofac_status to your decision layer, preserve IRS signals independently, and combine only the policy outcomes your workflow requires.

Ready to add OFAC screening to your workflow?

Use Pactman Nonprofit Check Plus API to place OFAC status beside IRS nonprofit verification signals.

Get an API Key →