A borrower's automated ACH payment lands in the wrong loan account. The processor's settlement file doesn't match the gateway's transaction log, and the controller needs to know who owns the reconciliation before the morning's work moves on. For a Church Extension Fund, that's not a vocabulary problem. It's a control problem that touches borrower accounts, investor records, cash, and the audit trail.
Payment processing and a payment gateway perform different jobs in the same transaction chain. The gateway captures and transmits payment information. Processing covers the wider work of authorizing transactions, settling funds, handling returns and disputes, and reconciling activity to the books. Understanding that boundary helps finance leaders assess vendor proposals, renegotiate agreements, and decide how to add payment methods without creating more manual work.
| Question | Payment gateway | Payment processing |
|---|---|---|
| Primary role | Securely captures and transmits payment information | Routes transactions, coordinates financial activity, and supports settlement |
| Where it appears | Checkout, payment form, or point-of-sale interface | Behind the payment interface, across financial institutions and networks |
| Typical CEF concern | Data capture, checkout experience, and connection uptime | Settlement, returns, disputes, reconciliation, and ledger posting |
| Who remains accountable | The CEF still oversees the vendor and implementation | The CEF still owns its accounting, controls, and audit evidence |
Why This Distinction Matters in a CEF
In a CEF finance office, a payment is never just a successful checkout message. The team must know which borrower or investor account should change, whether the bank settled the funds, and how the transaction will appear in the general ledger. When those records don't line up, staff need a clear answer about which vendor owns which part of the process, and which controls remain the CEF's responsibility.
That question matters across a Church Extension Fund's work. Borrowers make loan payments, investors purchase notes, and donors may contribute to a ministry or building campaign. Each payment may enter through a different interface, but the CEF still needs reliable posting, cash visibility, exception handling, and documentation.
A gateway may show that it received a payment request. That doesn't prove funds settled, nor does it establish that the payment was applied to the correct loan or investor account. The processor may handle network communication and settlement, but the CEF must still match payment activity to its internal records and resolve discrepancies.
For the board: A payment vendor can operate part of the transaction, but the CEF remains accountable for its books, controls, and evidence.
Generic fintech comparisons often stop at checkout and transaction routing. CEF leaders need a broader view that includes loan servicing, investor note programs, cash management, audit preparation, and the work required to keep records consistent across disconnected systems. That's the lens to use before selecting a vendor or expanding into card acceptance.
Defining Payment Processing and the Payment Gateway
A payment gateway is the technology layer that captures payment details from a website, mobile application, or point-of-sale system, secures them, and transmits an authorization request to the acquiring bank or processor. In practical terms, it's the payment terminal at the digital front door. It normally doesn't move or settle the funds itself.
Payment processing is the broader financial and operational function. It includes authorization and communication among the merchant, acquirer, card network, and issuing bank, then continues through clearing, settlement, funding, refunds, disputes, and reconciliation. A single vendor may offer both gateway and processing services, but the functions remain distinct.
The division has been part of online commerce for decades. Authorize.Net was founded in 1994, and CyberSource followed in 1996 as online businesses needed web-compatible payment acceptance (Adyen's overview of payment-industry history). The names may appear together in one contract today, but the handoff between secure data capture and financial processing still matters.
Follow a card payment through the chain
A card transaction typically moves through these stages:
- The borrower, investor, or donor enters payment information in the CEF's checkout form.
- The gateway securely captures the information and transmits an authorization request.
- The processor routes the request through the card network to the issuing bank, which approves or declines it.
- The processor returns the decision through the gateway to the CEF's payment interface.
- If the transaction is approved and captured, the processor coordinates clearing and settlement with the acquiring institution.
- The CEF receives settlement information and must reconcile it to the correct account and ledger entries.
The distinction matters just as much for ACH. A gateway can initiate a bank payment, but the processing and ledger environment must still validate the transaction, post it to the right loan or investor account, reconcile settlement, manage exceptions, and preserve an auditable record. For a concise overview of the general distinction, see this guide to gateway and processor roles for direct-to-consumer brands.
Comparing Their Roles Across Control Domains
A vendor may present gateway and processing as one integrated service. That can simplify operations, but it doesn't change who must oversee each control. The gateway generally owns secure data capture and the customer-facing payment connection. The processor handles authorization routing, settlement, and much of the dispute and reserve machinery. The CEF remains responsible for its accounting records, internal controls, and evidence that the money was handled properly.
The table assigns operational roles, not legal liability. Contracts, payment rails, and provider arrangements vary. Finance leaders should document the actual allocation in their own agreements and procedures.
Control ownership across the payment chain
| Control Domain | Payment Gateway | Payment Processor | CEF Responsibility |
|---|---|---|---|
| Uptime and connectivity | Maintains the payment interface and transmission connection | Maintains transaction routing and network connectivity | Monitor service performance, escalation paths, and failed-payment queues |
| Data security and PCI scope | Secures captured payment data and may provide tokenization | Protects data handled within its processing environment | Confirm the implementation, vendor evidence, and applicable PCI requirements |
| Authorization and declines | Sends the request and presents the response | Routes authorization requests and returns issuer decisions | Set policies for declines, retries, and communication with the payer |
| Settlement and funding | May report transaction activity, but normally doesn't settle funds | Coordinates settlement and provides settlement reporting | Match deposits and fees to bank activity and accounting records |
| Refunds and disputes | May provide tools for submitting or tracking requests | Handles processing workflows and may set operational requirements | Approve refunds, collect evidence, and manage borrower or investor communication |
| Fraud screening | May apply checkout security checks | May apply transaction monitoring and risk controls | Define risk appetite, review exceptions, and document escalation |
| ACH returns and exceptions | Captures or transmits payment instructions | Supports processing and return reporting | Identify the affected account, reverse or correct entries, and retain evidence |
| Reconciliation | Provides gateway transaction logs | Provides settlement and processor records | Own the match between payment activity, bank deposits, subledgers, and the general ledger |
For finance leaders, reconciliation is not a task to assign vaguely to “the vendor.” A gateway log and processor settlement report serve different purposes, and neither automatically proves that the CEF posted a payment correctly. The institution needs a repeatable process for matching the records and investigating exceptions.
Fraud and disputes make the ownership question sharper. Regulatory material reports that non-card payment fraud rose 271% from 2020 to 2024, and suspicious-activity reports related to check, ACH, and wire fraud increased 489% from 2014 to 2024. Merchant chargeback losses increased 30% in 2023 compared with 2022, according to the Federal Reserve's regulatory material. These figures reinforce the operational point: outsourcing payment connectivity doesn't outsource the CEF's governance responsibility.
Cost Structures and Settlement Rails Compared
A card processing fee isn't one indivisible charge. The merchant discount rate typically combines interchange, paid to the card-issuing bank; a network assessment, paid to the card network; and the processor or acquirer's charges. Those components behave differently in a vendor negotiation, so ask for an itemized breakdown rather than treating the quoted rate as a single price.
The Congressional Research Service reports that network fees are typically about 0.1%–0.2% of a transaction, while commonly advertised processor pricing from major providers is approximately 2.6%–2.9% plus $0.10–$0.30 per transaction. Processor charges may be negotiable, unlike interchange and many network fees. Those figures are a benchmark, not a quote for a CEF; the actual contract and payment mix determine the charges. See the Congressional Research Service's payment-card overview.
Match the rail to the payment
Card payments offer a familiar checkout option, but the CEF should look beyond the gateway fee. Card costs also reflect issuer, network, acquirer, processor, fraud controls, and settlement services. The gateway is one technical access point within that wider cost chain.
ACH is often a better fit for recurring loan payments and investor transactions. Its pricing is commonly structured as a per-transaction charge rather than a percentage of the payment value, and settlement follows a defined batch schedule rather than card-style immediate authorization and funding. ACH returns also require dedicated procedures: a returned debit must be identified, tied to the right account, and handled in the subledger and cash records. For a practical overview of this rail, see ACH payment types and their uses.
For planning purposes, compare the full operating cost, not just the visible technology charge. Include authorization, network participation, settlement reporting, returns, exception handling, and staff time spent reconciling payment records. The right rail depends on the purpose of the payment and the CEF's ability to manage the records it creates.
Security, PCI Scope, and Regulatory Considerations
The way a payment page reaches a customer affects the CEF's card-data environment. Under the PCI Security Standards Council's guidance, eligibility for the e-commerce SAQ A framework requires the entire payment page delivered to the customer's browser to originate directly from a PCI DSS-validated third-party service provider. The customer may be redirected to the provider's page, or the provider's page may be embedded in an iframe. See the PCI Security Standards Council's SAQ A guidance.
If the CEF's own website generates the payment page that collects cardholder data before sending it to a processor, the CEF's environment has a more direct role in handling that information. A hosted or embedded third-party page can reduce the systems exposed to card data, but it doesn't remove the need to check the implementation, maintain vendor oversight, and retain appropriate evidence.
Track the financial and compliance controls
Card acceptance costs also depend on the card and issuer. Under Federal Reserve Regulation II, the maximum interchange fee for covered debit issuers is $0.21 plus 0.05% of the transaction value, with a possible $0.01 fraud-prevention adjustment for eligible issuers. The rule doesn't apply universally. Certain reloadable general-use prepaid cards and debit cards issued under government-administered payment programs are exempt from the interchange standard. The Federal Reserve's Regulation II interchange information is a useful reference when forecasting recurring card activity.
For a faith-based financial institution, the practical control file should show who approved the vendor, what services the vendor performs, how the payment page is configured, and how the CEF verifies that its actual setup aligns with the applicable requirements. Retain transaction records and exception documentation in a way that supports internal review and external audit. A durable audit trail helps staff explain what happened, who acted, and how the resulting entry reached the books. CEF finance teams can also use this guide to audit-trail requirements to assess their documentation practices.
CEF Workflows in Practice
Consider a card gift made through a CEF's giving portal for a church-building campaign. The gateway captures the card information and may tokenize it, while the processor routes the authorization request and coordinates settlement. Once the settlement report arrives, finance staff must match the gross gift, processing fee, and net bank deposit to the donor record and campaign pledge ledger.
The failure mode is often in the accounting handoff. If the team posts only the net deposit as campaign income, it may lose visibility into the gross gift and the fee charged. If the payment is associated with the wrong donor or pledge, the gift record and financial report can diverge. The gateway can confirm that a payment was submitted, but the CEF still needs a consistent method to reconcile the processor's report to its bank account and internal records.
Follow an ACH investment through an exception
Now consider a church member purchasing an investor note through an online portal. The gateway captures the bank details, and the processor originates the ACH debit. If the bank returns the payment because the account is closed, the CEF must identify the affected purchase, reverse any related accounting treatment, restore the note's availability as appropriate, and document the exception for review.
That sequence is why ACH return handling should be defined before launch. Finance and investor-services staff need to know where return notices arrive, who investigates them, how account balances are corrected, and when the member is contacted. The entry should flow through to the investor record and supporting statements rather than stopping at a bank report.
These workflows depend on reliable cash application, not merely successful payment capture. A CEF can assess its current process with this overview of cash application automation. The key test is whether payment activity reaches the right borrower, investor, or donor record and remains traceable through the accounting system.
Single Provider vs Multi-Provider Orchestration
The more consequential architecture decision may be whether to use one processor or route payments across several. Research cited in the 2025 Merchant Payment Ecosystem report found that 56% of payment and technology decision-makers preferred working with multiple processors, rising to 64% among predominantly online merchants. The report also described payment orchestration as a way to connect several providers through one API (Merchant Payment Ecosystem report).
That preference isn't a reason for every CEF to add providers. Multi-provider routing can create options for uptime, geographic acceptance, authorization handling, and negotiations. It can also split settlement files, dispute workflows, fraud signals, vendor oversight, and reconciliation across different systems. A CEF with limited capacity to monitor those records may take on more operational risk than the additional route removes.
Resilience has a price: Every additional provider adds another set of reports, exceptions, contacts, and controls to manage.
New payment rails aren't automatically safer. The Federal Reserve's analysis of pay-by-bank cites 2023 FTC data in which bank transfers and cryptocurrency generated the highest loss amounts, while cards and payment apps generated more fraud reports. That's a reminder to evaluate controls and loss exposure by rail rather than assuming bank-based payments eliminate fraud risk.
Before adopting orchestration, ask whether your team can monitor provider performance and reconcile activity consistently across systems. The total cost includes transaction charges, vendor review, exception handling, audit trails, returns, and staff time. For a CEF with straightforward payment needs and a lean finance team, a single well-governed provider may be the better operational choice. Add redundancy only when the CEF can control the complexity that comes with it.
Decision Checklist and Implementation Sequencing
Use the next vendor review to establish who owns each step, what evidence the CEF receives, and how the payment connects to loan servicing, investor records, cash, and the general ledger. Ask vendors to show actual reports and exception workflows, not only a checkout demonstration.
CEF vendor review checklist
| Evaluation Area | Question to Ask | What Good Looks Like |
|---|---|---|
| Control ownership | Who handles capture, authorization, settlement, disputes, returns, and reconciliation? | Named responsibilities in the contract and internal procedures |
| PCI evidence | What supports the proposed SAQ eligibility and page-delivery design? | Current vendor documentation and an implementation that matches the documented setup |
| Settlement files | How are files delivered, and can finance staff identify gross, fees, net deposits, and exceptions? | Consistent reports that can be matched to bank activity and accounting records |
| ACH returns | Where do return notices arrive, and how are corrections applied to the borrower or investor account? | A documented queue, assigned owner, and traceable correction process |
| Disputes and reserves | How are chargebacks communicated, and what reserve policy applies? | Clear timelines, evidence requirements, and contract terms |
| Uptime and escalation | What service commitments apply, and whom does the CEF contact during an outage? | Written commitments and an escalation path staff can use |
| Ledger integration | How does payment activity reach loan servicing and the general ledger? | Reconciled entries without routine manual rekeying |
Plan implementation in a controlled sequence. Begin with discovery of payment types, current records, and unresolved exceptions. Follow with data migration and validation, then parallel processing so staff can compare new outputs with existing records before relying on the new flow. Test reconciliation, train the people who handle payments and exceptions, and cut over only after the team can explain how every material transaction reaches the books.
The checklist is vendor-agnostic. The right choice depends on whether the CEF is card-heavy or ACH-heavy, whether staff can absorb multi-provider reconciliation, and whether the loan-servicing and general-ledger platforms can consume settlement files without routine manual intervention. Treat gateway and processor selection as a platform decision: evaluate the payment interface, processing arrangement, accounting workflow, and audit evidence together.
CEFCore provides a financial management platform for Church Extension Funds that connects loan management, investor notes, general ledger, cash and ACH operations, reporting, and CRM. If your team is reviewing how payment activity flows into servicing and accounting, visit CEFCore to learn about its platform and implementation approach.
