SpinQavo.
EXPLORE WITH PERSPECTIVE

Payment Gateway

A technical layer communicating transaction information between a merchant and payment systems, distinct from settlement.

Concept and usage

A technical layer communicating transaction information between a merchant and payment systems, distinct from settlement.[1][2]

In context

A payment gateway is a technical layer that transmits transaction data between a merchant system and payment processing. It may secure data or call a processor, while the complete movement of funds can involve acquiring, issuing, clearing and bank accounts.[1][2]

Common confusion

A gateway is not automatically a payment provider, bank, card network or custodian of funds. Providers combine gateway, processor and service-provider functions differently, so use the documented function rather than the label.[1][2]

Example

A merchant may use a gateway to request authorization and later capture a payment before clearing and settlement. That sequence describes particular API flows; it is not a universal order for every transfer or wallet payment.[1][2]

Keep exploring

FoundationPayments: deposit and withdrawal are separate capabilitiesA service can accept one funding method and use another payout route. Payment instrument support, currency, identity checks and recipient conditions should be confirmed independently. A logo cannot describe the entire movement of funds.Deeper analysisThe payment journey behind the screenA payment button hides a chain of systems: the user interface, platform ledger, payment service and settlement network. A submitted request is not the same as settled funds. Understanding these boundaries is more useful than recognizing a familiar payment logo.Related contextPayment technology: why status needs precisionA payment can pass through authorization, network processing, settlement and account credit. One completed label covering all stages can mislead users. This is a recurring design problem across digital payment products.

Glossary

Compare perspectivesPayment ProviderRelated contextDepositCompare perspectivesWithdrawal

Sources and scope

  1. Payment Intents APIStripe DocumentationChecked:

    An example of one provider’s payment state model, not a universal payment lifecycle.

  2. Getting Started with VisaNet Connect — Acceptance APIsVisa DeveloperChecked:

    Describes authorization, capture, clearing and settlement in a specific VisaNet Connect API flow; access and availability have additional conditions.