Create
Your site or app creates a payment session with the order reference and approved payment choices.
Operational checkout for businesses in Pakistan
Turn every checkout into an operation your team can control
EPS is a commercial payment gateway in Pakistan for online merchant checkout, payment status, refunds, and settlement visibility—one connection from customer action to finance-team record.
Pakistan coverage for approved merchants may include JazzCash, Easypaisa, NayaPay, Raast, and Bank Alfalah routes. Method availability, fees, settlement timing, and production approval are confirmed during onboarding.
One connection, four operational outcomes
CheckoutCreate a controlled customer payment session.
StatusReturn an explicit result to the order.
RefundsKeep reversals attached to the transaction.
SettlementGive finance teams a reconcilable record.
The operational route
How a payment gateway in Pakistan moves an order
Merchants need the payment result to remain useful after the customer leaves checkout. EPS keeps the order, transaction, refund, and settlement story connected. Read the merchant payment gateway guide.
Authorize
The customer completes the selected flow and the transaction returns an approved, pending, failed, or declined state.
Confirm
Your server verifies the result before an order is marked paid, fulfilled, or held for review.
Reconcile
Transactions, refunds, and the applicable settlement record remain available to the merchant operation.
Merchant control
A payment result your order system can actually use
A clear state model helps customer support, operations, engineering, and finance look at the same transaction without guessing what happened.
See the integration paths
Order reference: EPS-DEMO-1042
Example only
- Session created
- Checkout can open CREATED
- Customer action
- Payment is being evaluated PENDING
- Server confirmation
- Order may be marked paid APPROVED
- After payment
- Refund stays linked to the order REFUNDED
One integration
Different payment choices, one operating record
Customer methods can differ while the merchant-facing lifecycle stays consistent: authorize, confirm, reconcile, and support.
Integration options
Hosted checkout and payment gateway API integration
Choose the lightest integration that returns a reliable order state. Move to server APIs and callbacks when reconciliation, refunds, or platform workflows require more control.
- HostedRedirect customers to a controlled checkout and receive them back with an order reference.
- Payment pageUse an approved hosted payment page while the merchant backend creates and verifies each transaction.
- APICreate sessions server-side, verify status, and process asynchronous updates.
{
"order_reference": "ORDER-1042",
"amount": "12500.00",
"currency": "PKR",
"return_url": "https://merchant.example/return",
"callback_url": "https://merchant.example/payment-status"
}
Evaluate the service
The commercial detail lives on the right page
Pricing, integration effort, risk controls, and business-model fit should be reviewed directly—not hidden behind generic feature promises.
Understand what shapes the merchant quote
Methods, volume, refunds, implementation scope, and settlement requirements are reviewed together.
Review pricing inputsMap checkout to the way your business fulfills
An ecommerce order, school fee, booking, and platform payment do not create the same operating work.
Find your operating modelConfirm controls before production access
Credentials, signed events, role boundaries, test cases, and incident paths are part of go-live readiness.
Review the control model
Security by operating design
Keep payment decisions on the server side
The merchant integration should verify transaction state before fulfillment, protect credentials, keep event evidence, and separate test activity from production access.
Read the security approach- 1Protected transport
Use HTTPS and controlled endpoints for every payment request and callback.
- 2Signed server events
Verify the source and integrity of payment-status updates before changing an order.
- 3Least-privilege access
Limit production credentials to the systems and people that genuinely require them.
Merchant questions
Ask the operational question first
Concise answers about eligibility, payment methods, integrations, pricing, settlement, refunds, security, and onboarding.
What does a payment gateway in Pakistan do?
EPS answers
A payment gateway in Pakistan connects a merchant checkout to approved payment routes, returns a transaction status to the order, and provides the references needed for refunds, settlement, and reconciliation. EPS offers this as a commercial merchant service rather than a consulting product.
Is EPS a commercial payment service or a consultancy?
EPS answers
EPS is presented as a commercial payment-gateway service. The site is designed to move eligible businesses from evaluation to merchant onboarding, not to sell advisory reports.
Which businesses can request merchant access?
EPS answers
Ecommerce stores, service businesses, education providers, retailers, platforms, and other registered businesses can request a review. Final eligibility depends on the business model, documents, KYC and AML review, and required payment methods.
Which payment methods can be connected?
EPS answers
For Pakistan, approved merchant projects may enable JazzCash and Easypaisa wallet flows, the NayaPay e-wallet, Raast instant transfers, and account-based routes through banks such as Bank Alfalah. The exact method mix is confirmed for each merchant before launch.
How can a website or app integrate EPS?
EPS answers
A merchant can start with a hosted payment page or connect through server-side APIs. The backend creates the payment, verifies status, and processes signed postbacks before an order is fulfilled.
Does hosted checkout still require a backend?
EPS answers
Yes. The merchant backend uses the approved API key and project ID to create and verify payments, while signed postbacks provide asynchronous status updates.
How are gateway fees calculated?
EPS answers
Pricing is quoted after the team reviews payment methods, expected volume, refund needs, integration work, and settlement requirements. No public rate is promised before that review.
When are transactions settled?
EPS answers
Settlement timing depends on the approved merchant profile, payment method, banking route, risk controls, weekends, and holidays. The applicable schedule is documented in the merchant offer.
How do refunds and failed payments appear?
EPS answers
The integration is designed around explicit payment states so the merchant can distinguish approved, pending, failed, and refunded transactions and keep order handling aligned.
What security controls are included?
EPS answers
The service design uses encrypted transport, signed server requests, controlled credentials, event logs, and integration testing. Any formal certification or scheme eligibility is confirmed separately during onboarding.
What happens after I request access?
EPS answers
The EPS team reviews the company, website, products, preferred payment methods, integration route, and expected volume, then returns the next onboarding and technical steps.
Bring your checkout and operating questions
Tell EPS how your business sells, fulfills, refunds, and reconciles. The merchant team will map the next commercial and technical steps.