Move checkout into a cleared record
A commercial payment gateway in Pakistan for businesses that need a controlled route from customer payment to verified order status and settlement operations.
Apply for merchant accessAccept Build a customer payment flow.
Verify Confirm status on the server.
Operate Keep refunds and records connected.
One commercial service
Payment is a route, not a button
A useful gateway keeps the customer experience and the merchant record aligned. The transaction should enter through an approved flow, return an explicit state, and remain traceable when support or finance reviews it later.
This service is designed for eligible ecommerce stores, online services, subscription businesses, and platforms in Pakistan. Available payment methods, onboarding documents, fees, and settlement timing are confirmed for each merchant.
Transaction lifecycle
Four states your operation can follow
Customers see a payment experience. Your team needs a reliable sequence behind it.
- 01
Create
Open a hosted checkout, payment link, or API payment session with an order reference.
- 02
Authorize
Present the approved route and receive a pending, approved, declined, or failed response.
- 03
Verify
Confirm the result on the server before your order system marks a purchase as paid.
- 04
Reconcile
Keep transactions, refunds, and the applicable settlement record attached to the merchant operation.
Ways to collect
Choose the entry point that fits the sale
A single merchant may need more than one payment entry point. Each option should still return a result that the business can verify and support.
Hosted payment links
Create a payment request for invoices, remote orders, or sales conversations without building a complete checkout.
Website and app checkout
Connect a hosted flow, ecommerce platform, or server API to the order lifecycle.
Recurring payment operations
Plan repeat collection, customer authorization, retries, cancellation, and account status as one system.
Payment status
Let the server decide what paid means
A browser redirect is useful for the customer, but it should not be the only source of truth for fulfilment. Your backend should verify the payment state and handle later events without guessing.
Explore integration pathsSESSIONCreatedCheckout may open
PAYMENTPendingWait for a verified outcome
ORDERApprovedFulfil after server confirmation
AFTERCARERefundedKeep the reversal linked
Integration discipline
Reduce avoidable payment ambiguity
Good security copy should describe controls, not imply certifications that have not been supplied. The intended integration model uses encrypted transport, controlled credentials, server verification, event validation, and practical test cases.
- Keep secret credentials away from browser code.
- Verify payment status before fulfilment.
- Store event references for support and reconciliation.
- Test success, failure, pending, retry, and refund paths.
Commercial fit
Pricing starts with the payment route
Fees depend on the merchant category, approved payment methods, expected volume, refund profile, integration work, and settlement needs. A scoped proposal is more useful than a public number that may not apply.
See how pricing is preparedFAQ
Questions before the merchant review
Clear answers about the commercial scope, integration, pricing, settlement, and onboarding.
Is this a commercial payment gateway service?
Yes. The site presents a merchant payment service for checkout, payment links, recurring billing, transaction status, and settlement operations. It is not a payment consulting practice.
Which businesses can apply for merchant access?
Registered ecommerce stores, service providers, subscription businesses, and platforms can apply. Eligibility depends on the business model, products, website, documents, expected volume, and risk review.
Which payment methods can be connected?
The intended scope covers approved card, bank, account, wallet, and link based payment flows. The exact mix is confirmed for each merchant during onboarding and is not promised before review.
How can my website or app integrate?
A merchant can use hosted checkout, share payment links, connect an ecommerce flow, or plan a server API integration with verified payment status updates.
Are Shopify and WooCommerce integrations available?
Shopify and WooCommerce requirements can be reviewed during onboarding. Plugin availability, checkout behavior, order status mapping, and production approval are confirmed for the merchant before launch.
How is pricing calculated?
A proposal is prepared after reviewing payment methods, business category, expected volume, refunds, integration route, and settlement requirements. The site does not publish a rate that may not apply.
When will funds settle?
Settlement timing depends on the approved merchant profile, payment route, banking arrangements, risk controls, weekends, and holidays. The applicable schedule is documented in the merchant offer.
How are failed and pending transactions handled?
The integration is designed around explicit transaction states. Your order system can keep a payment pending, mark a verified approval as paid, or ask the customer to retry after a failed attempt.
What security controls are part of the integration?
The service design uses encrypted transport, controlled credentials, server side verification, signed event handling where applicable, and event records. Any formal certification is confirmed separately, not implied by this website.
What happens after I submit the merchant form?
The team reviews your company, website, products, preferred payment flow, integration needs, and expected volume. You then receive the applicable commercial, document, and technical next steps.
Merchant onboarding
Bring your website and payment flow
Tell us what you sell, how customers pay, and where the payment result needs to go.
Start the merchant application