Direct Answer
A payment processor handles the technical exchange of payment information. In card payments, processing services support authorization, clearing or settlement: the decision, transaction-data exchange and financial completion stages. This technical role is distinct from providing the merchant's card-acceptance relationship or the customer's card. One provider may combine processing with other payment services.
Source: Visa Developer, “Glossary” (VisaNet processor and authorization definitions); Visa, “Payments: understanding the components and solutions” (High-level gateway and processor roles only); Stripe, “Payment processor vs. merchant acquirer: How they differ and how they work together” (Example of combined processing/acquiring services; not all-provider capability); Authorize.net Developer, “Payment Transactions” (Provider technical lifecycle, underwriting and dispute representation), accessed 2026-09-03.
The processor's technical role
The processor handles payment messages, rather than selling the goods or issuing the customer's card. Visa's developer glossary defines its processor role around authorization, clearing, settlement and related processing services. In that glossary, the processor connects directly to VisaNet. That connection requirement is Visa-specific, not a definition of every provider's architecture.
Source: Visa Developer, “Glossary” (VisaNet processor and authorization definitions), accessed 2026-09-03.
- Authorization asks whether a transaction is approved or declined.
- Clearing exchanges and processes the transaction data used before financial settlement.
- Settlement completes the relevant financial obligations. A processor can support that process without being the merchant's acquiring institution.
Source: Visa Developer, “Glossary” (VisaNet processor and authorization definitions); Authorize.net Developer, “Payment Transactions” (Provider technical lifecycle, underwriting and dispute representation); Stripe, “Payment processor vs. merchant acquirer: How they differ and how they work together” (Example of combined processing/acquiring services; not all-provider capability), accessed 2026-09-03.
A function is not necessarily a separate company
The gateway provides the checkout connection, while the acquiring relationship enables merchant card acceptance. Processing is the technical transaction-handling function between the relevant systems. These distinctions do not mean a merchant needs a different vendor for each function. A provider can package acquiring and processing together.
Source: Visa, “Payments: understanding the components and solutions” (High-level gateway and processor roles only); Stripe, “Payment processor vs. merchant acquirer: How they differ and how they work together” (Example of combined processing/acquiring services; not all-provider capability), accessed 2026-09-03.
Illustrative example: trace the failed step
Imagine a support ticket says, “The processor accepted the request, but the payment failed.” Those observations can coexist. In Adyen's documented online flow, a successful Hypertext Transfer Protocol (HTTP) web response can still contain an unsuccessful payment result. For this hypothetical ticket, first separate successful request handling from the payment's business outcome. Do not diagnose an issuer rejection from the web status alone.
Source: Adyen Documentation, “Refusal reasons” (Adyen online-payment HTTP versus business-result distinction), accessed 2026-09-03.
A transaction-triage worksheet
The following is a suggested investigation order. Apply your own provider's status definitions; these are not universal error codes.
Question | Evidence to inspect |
|---|---|
Was the request handled? | The request identifier and technical response. |
Was the payment approved? | The payment-result field, separate from the web response. |
Is more information expected? | The provider's later status notifications. |
Was capture required? | The configured capture flow and capture record. |
Is the question about receipt of funds? | The settlement and funding records, not authorization alone. |
Source: Adyen Documentation, “Refusal reasons” (Adyen online-payment HTTP versus business-result distinction); Adyen Documentation, “Result codes” (Adyen result states and order-state guidance); Authorize.net Developer, “Payment Transactions” (Provider technical lifecycle, underwriting and dispute representation), accessed 2026-09-03.
Prepare a useful support handoff
For an investigation, record the provider's transaction reference, request time, payment status and relevant later events. State what you expected and what actually appeared. Keep approval, capture and funding questions separate. This is an editorial troubleshooting suggestion based on the different stages, not a substitute for the provider's incident procedure.
Source: Authorize.net Developer, “Payment Transactions” (Provider technical lifecycle, underwriting and dispute representation); Adyen Documentation, “Result codes” (Adyen result states and order-state guidance), accessed 2026-09-03.
Do not infer the cause from a failure label
Also avoid treating every failed transaction as a processor outage. An issuer can decline after reviewing account or risk signals, and the returned explanation may be limited. Conversely, a technical response alone does not establish an issuer decision. Diagnose from the available evidence instead of the word “failed.”
Source: Stripe Documentation, “Card declines” (Stripe's issuer-decline evidence and cardholder follow-up guidance); Adyen Documentation, “Refusal reasons” (Adyen online-payment HTTP versus business-result distinction), accessed 2026-09-03.
Follow the adjacent roles
Compare payment gateway, merchant acquirer and issuing bank to name the right function in a support or integration discussion.
Editorial note: AI-assisted educational content prepared for HaiPay. It is not investment, legal or tax advice. The cited sources explain the concepts; your provider agreement and applicable rules govern your arrangement.
FAQ
Sometimes a provider supplies both functions, but the terms are not interchangeable. Processing concerns transaction handling; acquiring concerns the merchant's card-acceptance relationship. Confirm which services and entities are named in your arrangement.
Source: Stripe, “Payment processor vs. merchant acquirer: How they differ and how they work together” (Example of combined processing/acquiring services; not all-provider capability), accessed 2026-09-03.
Processing systems carry authorization requests and responses. The card issuer, or a network service acting on its behalf where applicable, supplies the card authorization decision. Do not equate a technically accepted request with an approved payment.
Source: Visa Developer, “Glossary” (VisaNet processor and authorization definitions); Adyen Documentation, “Refusal reasons” (Adyen online-payment HTTP versus business-result distinction), accessed 2026-09-03.
Not by itself. A response can describe a technical request or an authorization stage. In card flows with separate capture, the approved payment still needs capture before settlement. Use the provider's payment-state and funding records to identify the event.
Source: Authorize.net Developer, “Payment Transactions” (Provider technical lifecycle, underwriting and dispute representation); Adyen Documentation, “Refusal reasons” (Adyen online-payment HTTP versus business-result distinction), accessed 2026-09-03.
A useful starting packet includes the transaction reference, request time, reported payment status, expected outcome and relevant later events. Say whether the issue concerns request handling, authorization, capture or funding. Follow the provider's support procedure for any additional information.
Source: Authorize.net Developer, “Payment Transactions” (Provider technical lifecycle, underwriting and dispute representation); Adyen Documentation, “Result codes” (Adyen result states and order-state guidance), accessed 2026-09-03.
Sources
Related terms
Acquiring and settlement
Payment Gateway
A payment gateway is technology that passes payment information from a business's checkout to the systems that process the transaction.
Acquiring and settlement
Merchant Acquirer
A merchant acquirer is a payment service provider that contracts with businesses to accept and process card payments on behalf of participating card networks.
Acquiring and settlement
Issuing Bank
An issuing bank provides payment cards to customers and manages the accounts used for those cards throughout authorization, clearing, and settlement.
Acquiring and settlement
Card Payment Clearing
Card payment clearing exchanges final transaction details so the institutions serving the merchant and cardholder can calculate what they owe.
Usage Guide
Read GuidePayment Roles
Merchant Acquiring Explained: Acquirer vs Processor vs Acquiring Bank vs PayFac
Need help mapping your payment stack?
Launch a branded hosted payment page without building checkout from scratch.
Contact Us