Start with a transaction-boundary review
Use a transaction-state and responsibility map as the first decision artifact for a card-payment approach. Instead of comparing provider names first, record each transition from authorization through settlement, the party responsible for it, the status your systems can observe, and the response required when the outcome is unresolved.
Authorization, capture, clearing, and settlement are distinct stages. Authorization reserves funds, capture places the authorized transaction into the clearing file, clearing finalizes net positions between the parties, and settlement is when the money arrives. An approved authorization is therefore not the same state as a captured transaction or settled funds.
Use that distinction to frame the evaluation:
- State: What does each status mean in your order, ledger, and payment records?
- Boundary owner: Which internal team or external party owns the next transition?
- Permitted action: What can happen at that state, and what must wait?
- Confirmation: Which processor record or settlement report can confirm the state?
- Uncertainty response: What status check, escalation, or delayed action applies when the expected response does not arrive?
The map becomes a decision method when every row connects a state to an owner and a confirming record. Use it to examine the parties, integrations, failure paths, controls, and commercial terms without treating an authorization approval as evidence that the later stages are complete.
Assign responsibility at each payment boundary
Populate the responsibility side of the map by tracing the parties involved in a card payment. The cardholder initiates the payment. The business provides the goods or services and is the party whose proceeds are ultimately directed to its bank account. The merchant acquirer processes payments for the business and routes them through the card network to the issuer. The payment processor moves transaction information among the business, network, and issuer.
The card network carries the transaction between the acquiring and issuing sides. The issuer is the institution connected to the cardholder’s account. These roles describe the operating path, even when a single commercial provider presents several functions through one integration.
The merchant acquirer and payment processor have historically been separate entities, although some payment providers perform both functions. That distinction matters when you assign responsibility for support, transaction status, settlement information, disputes, and integration behavior.
For each role, record four boundary details:
- What information does this party receive or return?
- Which transaction state does this party influence or confirm?
- What does your team do when the expected response is delayed or unclear?
- Who owns the operational conversation when the problem crosses a boundary?
This turns the party map into an ownership test rather than a list of industry terms.
Treat the provider name as only one entry in the responsibility record. Record the functions included in the arrangement, the functions that remain with your team or another party, and the transaction states each function can confirm.
Treat authorization as a reservation, not a completed payment
Authorization is the stage at which the issuing bank places a hold on the cardholder’s funds; the money is reserved rather than transferred. Your order flow should therefore represent an authorization approval as an intermediate state, not as proof that your business has collected the funds.
An authorization approval does not guarantee capture because the card could be cancelled or the account could be closed before collection. Authorization rate and capture rate also measure different things. Keep those measures separate when you assess operational performance, because combining them can hide where a transaction stopped.
The hold also has a time boundary. Most issuers release an authorization hold after 7–30 days if capture does not follow. Treat that range as a documented operating consideration rather than as a universal deadline for every card, issuer, or transaction context.
Your requirements should make the distinction usable in practice:
- Store authorization approval separately from capture confirmation.
- Record the intended capture action and the conditions under which it may occur.
- Show transactions that remain authorized without capture.
- Define what your team does when the expected collection window is approaching.
- Report authorization and capture rates as separate measures.
The direct evaluation question is simple: can your order, payment, and finance records show the difference between funds being reserved and funds being collected? If they cannot, clarify that state model before comparing providers.

Separate capture, clearing, and settlement
Capture, clearing, and settlement are separate parts of the payment lifecycle, so your reporting should not collapse them into one completed status. Capture places the authorized transaction into the clearing file. Clearing finalizes the net positions between the parties. Settlement is the stage at which the money arrives.
That sequence gives you three different questions to ask about any transaction:
- Capture: Did your system instruct the acquiring side to place the authorized transaction into the clearing process?
- Clearing: Was the transaction included in the process that finalizes what the parties owe one another?
- Settlement: Did the expected funds arrive, and can you connect that receipt to the originating transaction?
Capture timing can affect interchange costs because some acquirers apply different rates depending on how quickly capture occurs after authorization. Include capture timing in the requirements and commercial discussion instead of treating it as an implementation detail.
Your reconciliation design should preserve the identifiers and timestamps needed to connect the order, authorization, capture instruction, clearing result, and settlement record. The exact fields depend on the arrangement you evaluate, but the requirement is stable: each transition should remain explainable. A transaction marked captured should not silently stand in for a settled amount, and a settlement report should not be treated as a substitute for the preceding transaction history.
Build a state-and-owner trace
Build a state-and-owner trace rather than treating the transaction lifecycle as a static diagram. The parties involved include the cardholder, business, merchant acquirer, payment processor, card network, and issuer, while authorization, capture, clearing, and settlement describe different stages. The trace connects each stage to the party, system record, and operating response that belong in the evaluation.
Define the minimum state record your teams need to inspect. It should identify the transaction, show its current state, preserve relevant transition times, and indicate the responsible boundary. Add the status returned by the payment service and the status held by your own systems so that differences can be found rather than silently overwritten.
Use the trace to test five requirements:
- State record: Represent authorization, capture, clearing, and settlement as distinct states with explicit transitions.
- Request identity: Define how repeated requests are recognized when the first outcome is uncertain.
- Confirmation path: Set how internal records are compared with processor responses and settlement reporting.
- Exception path: Identify the state changes, failures, delays, and ownership handoffs that need operational visibility.
- Responsibility record: Connect each response, correction, escalation, and customer-facing status to the party that owns it.
The merchant acquirer and payment processor may be separate entities or may be combined by a payment provider. Your responsibility map should reflect the arrangement you are actually evaluating, not an assumed industry diagram.
Use one representative transaction path as the review test. Trace it from the initial request through settlement, then separately trace a request that never reaches the processing service and a timeout whose status is unknown. If the state, owner, confirming record, or next response is missing at any branch, keep that boundary open in the requirements record.

Handle timeouts and unknown outcomes safely
A timeout is not automatically the same as a decline, and a request that never reaches the processing service is not the same as a transaction whose final status is unknown. Your failure model should keep those branches separate.
Visa Acceptance Solutions documents one scenario in which a network, DNS, or TLS failure prevents an authorization request from reaching the service. In that scenario, no transaction record is created there and no downstream authorization is submitted. Your team can treat that as a request-delivery failure within the documented boundary, subject to the service arrangement and the facts of the incident.
Visa Acceptance Solutions also documents a different scenario: a timeout occurs before the processor, network, or issuer responds. The service returns 151 or ETIMEOUT, the transaction status is unknown, and an automatic authorization reversal might be triggered. The documented action for that scenario is not to retry immediately; wait for the processing window and perform a status lookup.
Turn those distinctions into an operational branch:
- Record whether the request reached the relevant processing service.
- If the documented timeout condition applies, mark the outcome as unknown rather than successful or declined.
- Do not retry immediately in that timeout scenario.
- Wait for the processing window and perform a status lookup.
- Record the returned status and decide the next permitted action.
Your requirements should name the service boundary, response codes, lookup method, waiting rule, and owner for each branch. Do not let a generic retry policy decide what happens to an authorization whose status has not been established.
Compare commercial terms after the boundary review
Use the completed state-and-owner trace as the comparison frame for commercial terms. Payment providers use different pricing approaches, including quote-based, custom, published-plan, standard, and product-specific pricing. The exact integration, hardware terms, pricing, and support owner should be confirmed for a specific arrangement.
Complete the comparison in four boundary groups:
- State coverage: Which authorization, capture, clearing, settlement, refund, and dispute flows must be supported?
- System boundary: Which systems initiate requests, receive statuses, maintain the business record, and connect settled funds to transactions?
- Control ownership: Which security, reliability, compliance, reconciliation, and incident responsibilities belong to your organization, the payment provider, the acquirer, or another specialist?
- Commercial boundary: Which pricing components, support responsibilities, integration work, and hardware terms are included?
The purpose is to compare a defined transaction flow and responsibility model, not to predict a universal processing cost. Keep the state, ownership, and commercial boundaries together when reviewing an arrangement.
To make that review auditable, create one evaluation row for each required capability or control. Record the lifecycle state it affects, the party expected to perform it, the internal system that must represent it, the record that would confirm it, and the question still open. For commercial items, add the exact term to be confirmed and the owner who must validate it. This avoids scoring a price or feature without showing which transaction boundary it supports.
Ask the relevant provider or internal owner to confirm the exact integration, hardware terms, pricing, and support owner for the arrangement. Mark each answer as confirmed, open, or dependent on specialist review. Do not convert an unconfirmed answer into a provider ranking or implementation assumption. If the answer changes the state model, reconciliation path, or incident response, return it to the requirements record before selecting the next step. The resulting comparison is traceable: each decision points to a defined state, responsibility, confirming record, or unresolved question. That record also shows whether the next action is clarification, technical design, or qualified professional review.
Run the boundary review before comparing providers
Apply the state-and-owner trace before using a provider comparison. Provider pricing can be quote-based, custom, published, standard, or product-specific, and the exact integration, hardware terms, pricing, and support owner require confirmation for the arrangement you are considering.
Run the review in three passes. First, establish the transaction states and parties. Next, test uncertain outcomes and reconciliation. Finally, record the commercial and specialist-review boundaries.
- State pass: Which payment types, channels, currencies, capture patterns, refunds, and disputes must the design support, and how are authorization, capture, clearing, and settlement represented separately?
- Party pass: Which functions belong to the merchant acquirer, processor, network, issuer, provider, and internal teams at each state boundary?
- Integration pass: Which applications send payment requests, receive status changes, reconcile outcomes, and connect settled amounts to originating transactions?
- Uncertainty pass: What happens when a request never reaches the processing service, times out, produces an unknown status, or conflicts with an internal record?
- Control pass: Who owns monitoring, status lookup, reconciliation, incident handling, customer-facing updates, security, and compliance questions?
- Commercial pass: What are the pricing components, contract conditions, hardware terms, integration assumptions, and support responsibilities?
- Change pass: How will changes to the integration, transaction flow, or provider arrangement be reviewed and recorded?
Mark each answer as defined, open, or dependent on professional review. Keep an open state, missing owner, or unconfirmed record visible instead of treating it as resolved. The resulting boundary record identifies the next evaluation question and the party needed to answer it.
Decide where external engineering support fits
External engineering support fits around a defined software boundary, not around an undefined payment decision. Consider it when your team needs help documenting integrations, separating transaction states, connecting payment data to existing systems, improving observability, handling legacy constraints, or preparing reconciliation and reporting requirements.
Start by writing down the work that remains after the payment responsibilities are mapped. A useful scope can include:
- the systems that initiate or receive payment events;
- the transaction states that must be stored and displayed;
- the interfaces and data flows that need to be understood;
- the timeout and unknown-status branches that need implementation;
- the reconciliation records that need to connect operational and financial views;
- the tests, runbooks, and ownership records needed for handoff.
Keep the boundaries explicit. Engineering support can address software design, integration, implementation, testing, and technical documentation within the agreed scope. It should not silently become the owner of payment approval, legal interpretation, compliance judgment, commercial terms, or financial policy.
Use a responsibility brief before bringing in outside capacity. Name the business decision still to be made, the software work already defined, the systems involved, the internal owner, the external deliverable, and the acceptance condition. If the work cannot be described at that level, clarify the payment and operating requirements first. If it can, you have a bounded basis for evaluating engineering support.
Carry the boundary record into the next evaluation
Carry a completed transaction-state and responsibility map into the next evaluation. Record the meaning of authorization, capture, clearing, and settlement; identify the party responsible at each boundary; connect each state to a confirming record; and document the response to an uncertain outcome. For the documented timeout scenario, do not retry immediately; wait for the processing window and perform a status lookup.
Add the unresolved commercial and operating boundaries to the same record. Payment providers use different pricing approaches, and the exact integration, hardware terms, pricing, and support owner should be confirmed for the arrangement you are considering. Keep those items alongside the state and ownership decisions.
Use this guide for planning and evaluation. A qualified payments, legal, compliance, or financial professional should decide questions that depend on your business, jurisdiction, or specific obligations. Once the boundary record shows the open decisions, you can define the software work that needs engineering support and move to the next conversation with a more precise scope.