A payment gateway acts between the merchant experience, the customer, the approved payment method and the financial institutions involved in authorization and settlement. The exact parties vary, but the operational stages remain recognizable.
1. Initiation
The merchant creates a payment with an order reference, amount and currency. The customer selects an available method. Availability may depend on the merchant profile, customer location, transaction currency and acquiring setup.
2. Authentication and authorization
Required payment details and authentication are collected through the approved surface. The request travels through the gateway and acquiring route for a decision. An approval means the transaction can proceed; it is not the same as final settlement.
3. Event confirmation
The merchant system should rely on an authoritative server-to-server event, verify its integrity and match the expected amount, currency and reference. A customer returning to a success page is useful for experience, but it is not sufficient proof for fulfilment.
4. Settlement
Approved funds follow the settlement arrangement recorded in the merchant schedule. Currency, payout timing, reserves, holidays and cross-border conditions can affect when money reaches the merchant account.
5. Reconciliation and exceptions
Finance connects transaction references to orders and payouts. Support needs the same reference when handling a refund, failed payment or dispute. A clear lifecycle prevents teams from maintaining conflicting versions of payment truth.
Questions to settle before launch
- Which methods and currencies are approved?
- What business and website documents are required?
- Which event is authoritative for fulfilment?
- How are refunds, disputes and failed payments handled?
- What is the settlement currency and payout cadence?
- Which reports or references support reconciliation?