Corporate B2B-API
Corporate Matching FAQ
Part I: Employee & Donor FAQ
What does the Corporate Matching Gateway do for me as a donor?
It connects your personal donation directly to your employer's matching funds in real time — doubling your impact without sharing your identity, cause preferences, or giving history with your employer.
Who pays the $14.99/month Impact License?
Either you or your employer. The Impact License is $14.99/month — full platform access with priority matching, impact reporting, and giving history — active for 30 days. An annual option is available at $149.00/year — active for 12 months and includes two months free. Some enterprises sponsor the seat license for their workforce as part of their CSR program. Check with your HR team or activate individually at checkout.
How do I receive my tax receipt?
You receive a 501(c)(3) tax receipt for your direct donation from the recipient organization. Your employer receives a separate corporate donation receipt for the matched portion directly from the nonprofit/NGO's payment processor.
How fast does the match reach the nonprofit/NGO?
Matching funds clear in real time through our gateway protocol — not the 60 to 90 day delay typical of traditional corporate matching platforms.
Is my personal data ever shared with my employer?
No. The platform is built on a Double-Blind Zero-Trust architecture. Your name, email, cause selections, and transaction history are never transmitted to corporate systems.
What if my company isn't a GIVE→ALIGN corporate partner yet?
Matching funds always come from your employer — the Impact License and the $6.00 Corporate Matching Gateway Upgrade never include matching money on their own. If your company isn't an approved partner yet, use the free Employer Match Check on the pricing page to nominate them: we contact your company directly and, true to the Zero-Trust mandate, your name is never included.
Part II: Enterprise CSR, Legal & Security FAQ
What is the GIVE→ALIGN Corporate Matching Gateway?
A lightweight middleware layer that connects enterprise matching funds directly to verified donor contributions. It enables employees to double their philanthropic impact using corporate matching dollars without exposing individual identity or preference data to the employer.
How does Zero-Trust architecture protect our organization?
Every match request requires a valid short-lived cryptographic token. The platform never trusts any network call — internal or external — until verified. No persistent session state is maintained. No PII is stored or transmitted.
Does this require integration into our HR or payroll systems?
No. The platform uses secure PWA link routing and standardized API webhooks. Eligibility is verified via cryptographic tokens, not employee directory data, eliminating IT procurement cycles.
Can we set custom matching rules and caps?
Yes. Enterprise administrators can define 1:1, 2:1, or custom matching ratios, set annual per-employee limits, and restrict matches to specific vetted nonprofit/NGO categories through the administrative portal.
How do we handle year-end tax reporting?
The platform exports aggregate corporate giving ledgers with single-click reporting for tax filings, backed by a real-time regulatory verification audit log.
How does the platform verify that nonprofits/NGOs are legitimate?
Before any corporate match is authorized, the middleware executes automated real-time calls against federal tax-exempt status verification databases. If an organization's status is inactive or invalid, the match is automatically rejected.
Does GIVE→ALIGN hold matching funds in escrow?
No. The gateway acts strictly as a real-time clearance bridge. Validated matches are dispatched directly from the corporate matching ledger to the nonprofit/NGO's verified payment gateway. We never hold funds.
What does the corporate admin dashboard show?
Aggregate-only data: total matching capital deployed, verified nonprofit/NGO recipient counts, impact category metrics, and remaining budget. Individual employee names, giving preferences, and transaction histories are excluded from all administrative endpoints.