How to Build a Nonprofit Compliance Check Into a Fintech or Donation Platform

Q: Can I include OFAC screening in the same request?

Yes. Use `ofac_status` alongside the IRS-related fields.

Q: Which fields help with conflicting or stale IRS data?

Use the source-specific dates and `irs_bmf_pub78_conflict` within its documented private-foundation scope.

Direct answer

Build the nonprofit compliance check at the point where the platform receives, stores or acts on a nonprofit EIN.

Use Pactman Nonprofit Check Plus API to confirm organization identity, evaluate the BMF and Pub. 78 signals required by the transaction, review revocation and reinstatement history, and inspect ofac_status. Keep source fields traceable and let the fintech or donation platform produce the final compliance outcome from documented rules.

Recommended verification flow

Normalize the nonprofit EIN.
Call the Nonprofit Check Plus API.
Confirm ein and organization_name.
Evaluate bmf_status and BMF classification.
Evaluate pub78_verified and contribution fields when the transaction requires them.
Review foundation classification when relevant.
Check revocation and reinstatement fields.
Review ofac_status.
Check source freshness and conflicts.
Apply the platform's allow, review or stop policy and retain the source signals needed for audit.

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
Identity fields	`ein`, `organization_name` and source-specific identity fields identify the nonprofit.	Ensure the compliance result belongs to the intended organization.
`bmf_status` / BMF classification	Supplies IRS organization and exemption context.	Apply the platform's tax-status rules.
`pub78_verified` / `organization_types`	Supplies Pub. 78 and contribution context.	Apply deductibility or charitable-recipient rules when required.
Foundation fields	Supplies foundation classification.	Apply product-specific treatment for public charities or private foundations.
Revocation fields	Supplies revocation and reinstatement history.	Route historical or unresolved revocation according to policy.
`ofac_status`	Supplies organization-level sanctions screening.	Apply OFAC review separately from IRS status.
Source dates / `irs_bmf_pub78_conflict`	Supplies freshness and documented private-foundation conflict context.	Route stale or conflicting records for review.

Example decision logic

A fintech or donation workflow might:

resolve the intended nonprofit by EIN;
evaluate the IRS fields required for the transaction;
check revocation and reinstatement;
screen OFAC;
preserve source dates and conflict signals;
return an application-level allow, review or stop outcome; and
use the bulk endpoint for scheduled or portfolio-level checks.

The same organization-level schema is available in the supplied single and bulk examples, so the platform can share one policy engine across interactive and batch checks.

Important: The current API does not define one universal compliance_passed field. The final decision belongs to the platform's policy layer.

Why use a consolidated nonprofit verification API?

Fintech and donation products often need several compliance dimensions inside a single transaction or onboarding flow.

Pactman lets the platform consume those dimensions through one consistent response model.

One normalized response

Receive organization identity, IRS status, contribution, revocation and OFAC signals together.

Separate source signals

Keep each compliance dimension traceable to the field that supports it.

Reusable compliance rules

Share one policy engine across checkout, onboarding, grants, disbursements and recurring reviews.

Developer-friendly automation

Use single-EIN checks for interactive flows and bulk checks for portfolios or scheduled monitoring.

Frequently asked questions

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

No. The current schema returns source signals that the platform combines according to its own policy.

Can I include OFAC screening in the same request?

Yes. Use ofac_status alongside the IRS-related fields.

Can the same compliance rules run in bulk?

Yes. The bulk endpoint returns the same current organization-level field model for each result and accepts up to 50 EINs per request.

Which fields help with conflicting or stale IRS data?

Use the source-specific dates and irs_bmf_pub78_conflict within its documented private-foundation scope.

Next step

Map the platform's compliance rules to Pactman's source fields, keep the final application decision separate, and reuse the same policy engine for single and bulk nonprofit checks.

Ready to embed nonprofit compliance?

Use Pactman Nonprofit Check Plus API to place IRS, revocation and OFAC checks directly inside fintech and donation workflows.

Get an API Key →