Review how EFFA handles payments, data, and platform access.

Once the employer approves an invoice, our payment processor collects the payment, EFFA's small transaction fee is deducted, and the rest is transferred to the school. EFFA gives both organizations a shared record of invoice and payment status.

Payments are processed through Stripe. EFFA keeps payment references and limited account-display information to connect the payment with its invoice and status. Full bank account details are handled through the payment provider.

Bank authorization supports payment of invoices approved by your authorized team. The authorization terms are shown during bank linking. Contact EFFA at inquiry@effa.io to request revocation for future debits; payments already in progress require separate review.

Your teams can follow payment status in EFFA. Processing and receipt depend on the payment method, bank timing, weekends, holidays, and standard payment-rail timing. A payment being approved or processing does not mean the school has received the funds.

Schools pay a transaction fee on direct-bill settlement. The standard rate is 3.5%, netted from the payout. Employers pay EFFA nothing and fund only the tuition they choose to fund.

EFFA uses organization and contact information, employee and school records, partnership terms, eligibility information, and invoice/payment records to coordinate employer-funded education. Depending on the workflow, records may also include program and course information, grades, benefit limits, and employee inquiry details. Provide only the information needed for the workflow; do not include Social Security numbers or full bank account details in messages or uploaded documents.

EFFA uses service providers for hosting, payments, communications, monitoring, storage, uploads, rate limiting, and selected AI-assisted document processing. The current provider inventory is supplied during security review with each provider's role and applicable access conditions.

Provider-issued trust materials may be available for review where the provider makes them available and where access conditions permit. EFFA distinguishes vendor-issued materials from EFFA-owned security documentation and does not present vendor reports as EFFA's own SOC assessment.

EFFA records indicate a HECVAT questionnaire was completed on June 1, 2026. Qualified security and procurement reviewers can request it through the Trust Center; availability, version, and access conditions are confirmed before sharing.

EFFA is designed to support schools that use service providers for employer-sponsored billing. Schools decide how they satisfy their FERPA obligations, including whether EFFA fits within their 'school official' framework for a given engagement. EFFA does not make that determination on a school's behalf, but we can walk your school, legal, or compliance team through the data we receive, how it is used, and how the workflow is structured.

EFFA supports employer education-assistance workflows, but we do not determine tax treatment. Whether a payment qualifies under IRC §127 depends on the employer's own education-assistance plan and tax position. We do not represent that any payment is automatically tax-free or provide tax advice. We can provide the transaction records your finance, benefits, or tax team needs to make that determination.

When an authorized finance user links a bank account, they authorize ACH debits only for invoices your team has approved. EFFA does not initiate payment for unapproved invoices. The authorization can be revoked for future debits by contacting your EFFA contact or inquiry@effa.io. The exact authorization language is shown during bank linking and recorded with the authorization. Payments are processed through Stripe; EFFA does not store full bank account numbers.

EFFA's platform terms govern use of the platform. Commercial terms between schools and employers are formalized separately through the partnership workflow. Your organization can request relevant materials for legal, security, or procurement review.