Merchant guide
How a payment gateway in Pakistan moves an online payment
A practical explanation of checkout, authentication, authorization, confirmation, settlement, reconciliation, payment methods, integration routes, and merchant selection criteria.
This guide explains the operating model. To evaluate EPS as a service, review pricing, integrations, and merchant onboarding.
What a gateway does
A payment gateway in Pakistan connects a merchant checkout with the banking, processor, card, account, wallet, QR, or other approved payment route used to evaluate the transaction. It gives the customer a way to pay and gives the merchant a reference and result that can be attached to the order.
The gateway is not the same thing as every payment method it can expose. A wallet is a customer payment method. A bank account route is another. The gateway is the merchant-facing layer that creates the payment attempt, coordinates the selected route, and returns the state.
The payment lifecycle
- Initiation: the merchant creates a payment session with the amount, currency, order reference, and return or callback information.
- Customer authentication: the selected payment route may ask the customer to verify the transaction.
- Authorization: the applicable financial route evaluates the request and returns an approved, declined, failed, or pending state.
- Merchant confirmation: the merchant server verifies the payment state before fulfilling the order.
- Settlement: approved funds move according to the merchant agreement, method, banking route, risk conditions, weekends, and holidays.
- Reconciliation: the merchant connects the gateway reference, order, refund, and settlement record.
A customer-facing “payment complete” screen is useful, but it should not be the only source of truth. The browser can be closed or interrupted, so the merchant server should verify the result independently.
Payment methods and customer context
Search and competitor evidence for this topic consistently emphasizes card payments, account or banking routes, mobile wallets, QR flows, payment links, and ecommerce checkout. The correct mix depends on the merchant’s customers, order value, device use, refund needs, and operational ability to reconcile each method.
| Method family | Merchant question | Operating consideration |
|---|---|---|
| Cards | Which customers and transaction types are eligible? | Authentication, disputes, refunds, and method-specific pricing. |
| Account-based | How is the customer redirected or confirmed? | Reference matching, status timing, and settlement records. |
| Wallets | Which wallet route fits the target customer? | Mobile handoff, customer confirmation, and refund support. |
| QR or link | Where does the order begin? | Chat, counter, social, invoice, expiry, and reference matching. |
Hosted checkout, ecommerce, and API integration
A hosted checkout can reduce frontend exposure and shorten implementation. Ecommerce integrations connect gateway state to a platform order. An API-led integration gives a custom website, app, or platform more control over session creation, server verification, callbacks, refunds, and internal reporting.
Regardless of route, test approved, pending, failed, declined, abandoned, duplicate-callback, wrong-amount, and refund cases before production launch.
How a merchant should compare gateway services
- Business eligibility and required company documents
- Payment methods suited to the customer and order
- Hosted, ecommerce, API, mobile, QR, or payment-link integration
- Transaction pricing, setup scope, and refund terms
- Settlement schedule, reports, bank requirements, and exception handling
- Credential, callback, fraud, dispute, and incident controls
- Implementation support and live-transaction escalation
Do not select a gateway only from a headline transaction rate. A lower rate can become operationally expensive when payment status, refunds, reconciliation, or support does not fit the business.
Payment gateway FAQ
Does every gateway support the same payment methods?
No. Method availability depends on the provider stack, merchant profile, customer flow, region, integration route, and current commercial approval.
Can a merchant launch with hosted checkout first?
Often, yes. A merchant can start with a hosted payment session and add deeper server integration when callbacks, refunds, reconciliation, or platform workflows require it.
Is settlement the same as payment approval?
No. Approval is the transaction decision returned during the payment flow. Settlement is the later movement and reporting of approved funds under the merchant agreement.
What should happen if a callback arrives twice?
The merchant system should process events idempotently so the same approved transaction cannot fulfill an order or grant access twice.