Do customers need a wallet app to pay with Raast?

No. Customers can pay from participating bank apps and wallets that support Raast. Exact availability depends on the customer's bank and the merchant project's enabled methods.

How fast do Raast funds settle?

Raast is built for real-time payment confirmation. Settlement timing to the merchant account still follows the project configuration and provider schedule confirmed during onboarding.

Is a browser success page enough to mark an order paid?

No. Confirm the payment with a signed server notification or a server-side status check before fulfilment.

Can Raast run beside JazzCash, Easypaisa, and cards?

Yes, when those routes are approved for the merchant project. Raast is one acceptance rail inside the same checkout and reporting layer.

What is needed to go live with Raast?

Merchant review, business documents, settlement account details, enabled payment methods, sandbox testing, and production activation after the test evidence is accepted.

Raast payment gateway

Raast payment gateway for Pakistan merchants — accept instant bank payments at checkout

Q: What is a Raast payment gateway?

A Raast payment gateway lets a merchant accept Person-to-Merchant payments over Pakistan's national instant payment rail through checkout, Request to Pay, or QR, then return a clear payment status to the order system.

Enable Raast P2M on hosted checkout, Request to Pay, and QR so customers can pay from participating bank apps while your team keeps settlement reports, refunds, and signed payment confirmation in one merchant flow.

Request Raast merchant access See how Raast works

Checkout Raast Request to Pay Static & dynamic QR

Pakistan shop counter with a bank-app Request to Pay approval and a printed PKR receipt — Raast at the counter: customer approves in a bank app, merchant keeps the receipt and order linked.

SpeedInstant payment result

Customers pay from a bank app and the checkout receives a clear success, failure, or pending state.

Cost profileLower-fee rail vs cards

Raast is positioned for account-based merchant payments with project-specific commercial terms.

ReachParticipating Pakistani banks

Accept payments from customers whose banks and wallets support Raast for the enabled route.

Definition

What is a Raast payment gateway?

Raast is Pakistan's national instant payment system. A Raast payment gateway is the merchant layer that lets your store or app accept Person-to-Merchant (P2M) payments over that rail — then returns a reliable status into order, finance, and support tools.

Customers typically pay with a Raast ID, IBAN, Request to Pay prompt, or QR from a participating bank or wallet app. Your business does not need the customer to enter card details for a Raast route.

Customer → Checkout / QR / RTP → Raast rail → Bank or wallet app → Merchant confirmation

Merchant outcomes

Why Pakistani businesses accept Raast

Settlement

Real-time payment confirmation

Raast is designed for instant end-to-end digital payments. Your operations team sees a clear transaction result instead of waiting on a slow card-style authorization loop.

Commercial

Lower fees than card rails

Account-based Raast acceptance is commonly used to reduce card MDR pressure. Exact merchant fees stay project-specific and are confirmed during onboarding.

Coverage

Works across participating banks

Customers can pay from bank apps that support Raast, so acceptance is not locked to one wallet brand at the counter or checkout.

Channels

QR codes and payment requests

Use checkout Raast, static QR for counters, dynamic QR for unique amounts, and Request to Pay when the project enables those modes.

Acceptance modes

How Raast payment acceptance works

Each Raast mode gets its own merchant desk still — Request to Pay, static QR, dynamic QR — while checkout confirmation stays the same discipline across all of them.

Clothing shop counter with fabric bolts and a smartphone Request to Pay screen

Request to Pay (Now)

Send an immediate payment request. The customer approves in their bank or wallet app and the merchant receives a near-instant result for fulfilment.

Tidy accounts desk with ledger, calendar, and a scheduled payment request

Request to Pay (Later)

Issue a timed request for invoices, deferred collections, or flexible due dates when the enabled Raast mode supports later payment.

Neighborhood shop glass counter with a laminated static Raast QR placard

Static QR payments

Print or display one merchant QR for repeated counter sales. The customer enters the amount and pays from a participating app.

Warehouse packing table with a tablet showing a unique dynamic QR for one order

Dynamic QR payments

Generate a unique QR per order or amount for online and remote sales where a one-time code improves matching accuracy.

Hosted checkout can present Raast beside approved wallets and bank routes. In every channel, verify the signed postback before marking the order paid.

Go-live path

Accept Raast on your checkout in three steps

Keep the path operational: merchant readiness first, then enablement, then live customer payments with status checks.

Complete merchant onboarding and KYC review

Confirm settlement account and PKR project settings

Enable Raast on the approved method list

Connect hosted checkout, QR, or Request to Pay

Test success, fail, pending, and duplicate postbacks

Go live and monitor settlement reports

// Enable Raast on a hosted checkout session
createOrder()
  .then(order => ppg.checkout.create({
    amount: order.total,
    currency: "PKR",
    orderReference: order.id,
    methods: ["raast"],
    returnUrl: "/payment/return"
  }))
  .then(result => verifyPaymentStatus(result.reference))
  .then(status => updateOrder(status));

// Keep API credentials on the server.
// Validate the signed postback before fulfilment.

Developer tools

How to integrate Raast with your store

Hosted checkout

Start with a hosted payment page that can present Raast when the merchant project enables it. This reduces sensitive payment handling inside your own frontend.

API and webhooks

Create the payment from your backend, attach an order reference, and listen for signed status updates. Treat redirects as customer UX, not as the only source of truth.

QR and payment links

Use static or dynamic QR for in-person and remote collection, or payment links when the storefront is light. Keep every channel tied to the same merchant reporting view.

Platform plugins

Ecommerce plugins or custom store backends can expose Raast when the project configuration and integration path support them. Confirm availability before promising a platform go-live date.

Method comparison

Raast vs wallets and cards

Raast is an account-based national rail. Wallets and cards remain useful — and can sit beside Raast in the same gateway when approved for the project.

Decision area	Raast	JazzCash / Easypaisa	Cards
Customer experience	Pay from a participating bank or wallet app via checkout, RTP, or QR.	Customer pays inside a wallet ecosystem or wallet QR flow.	Customer enters card details or uses a tokenized card checkout.
Merchant fit	Strong for PKR ecommerce, invoices, and counter QR with instant confirmation.	Strong where wallet users already dominate the buyer mix.	Useful for card-holding buyers and some cross-border card cases.
Cost shape	Usually positioned below card MDR; exact fees are project-specific.	Wallet MDR and limits depend on the enabled wallet route.	Typically higher MDR and card-network rules.
Data on merchant servers	No card PAN handling on a pure Raast route.	Wallet credentials stay with the wallet provider flow.	Card data handling depends on hosted vs direct integration.
Hardware	Not required for QR or checkout Raast.	Not required for standard wallet QR and online wallet flows.	Optional POS hardware only for in-person card acceptance.

Operations gap closed

Security, settlement, and confirmation before fulfilment

Finance desk with a stamped settlement statement and a laptop status log for payment references — Settlement paper and status log stay together — mark paid only after the signed confirmation lands.

Competitor Raast pages talk about instant payments and lower fees. They rarely spell out the merchant control points after the customer taps pay. That is where chargebacks, duplicate notifications, and premature fulfilment create real loss.

Use bank-grade transport on the provider path, keep API secrets on the server, and treat security as process: signed postbacks, idempotent order updates, refund records, and settlement exports finance can reconcile.

Before marking an order paid, verify the signed server notification or run a server-side status check. A browser thank-you page alone is not enough — especially when a customer closes the tab after approving the Raast request.

During onboarding, confirm settlement schedule, refund handling, transaction limits, and which Raast modes are live for the project: checkout, RTP now, RTP later, static QR, or dynamic QR.

Search questions

Raast payment gateway FAQs

What is a Raast payment gateway?

It is merchant checkout and acceptance infrastructure for Pakistan's Raast rail. It lets businesses collect P2M payments through checkout, Request to Pay, or QR and return a usable payment status to the order system.

Do customers need a special wallet app to pay via Raast?

No. Customers can pay from participating bank apps and wallets that support Raast. Availability still depends on the customer's institution and the merchant project's enabled methods.

How much does Raast cost merchants?

Commercial terms are project-specific. Raast is typically positioned as a lower-fee alternative to cards, but fees, caps, and settlement conditions are confirmed during merchant onboarding rather than published as a universal rate card.

How fast does the money arrive?

Raast confirms payments in real time for the customer flow. Settlement into the merchant account follows the schedule and account setup attached to the approved project.

Is additional hardware required for Raast QR?

No POS machine is required for standard Raast QR acceptance. A phone, printed QR, or checkout screen is enough when the merchant mode is enabled.

Can freelancers and invoice-led businesses use Raast?

Yes, when the merchant project enables payment links, Request to Pay, or QR collection. Ask during onboarding which channels are available for non-storefront sales.

How do refunds work on Raast?

Refunds follow the provider and rail rules for the original payment. Keep refund initiation and status inside merchant reporting, and wait for the signed status update before changing the order record.

Can Raast sit beside JazzCash, Easypaisa, and cards?

Yes. When those methods are approved, the same gateway can present Raast next to wallets and cards so buyers choose the rail they already use.

Next step

Ready to enable Raast on your checkout?

Tell us about your storefront or invoice flow, expected monthly volume, and whether you need checkout Raast, QR, Request to Pay, or a mix. We will map the onboarding checklist and integration path for your PKR project.

Start Raast onboarding Back to platform overview