All resources

Pay-in & Payout APIs in Pakistan: How Money Moves In and Out (2026)

Every business moves money in two directions. A pay-in API collects payments from customers — cards, Raast, JazzCash, easypaisa. A payout API sends money out — to gig workers, vendors, sellers or staff. Marketplaces, ride-hailing apps and platforms need both sides working together. This guide explains how pay-in and payout APIs work in Pakistan, the rails behind each, and what to look for when you combine them.

The two halves of a payment flow

Think of your business as a pipe that money flows through. On one end, customers pay you — that is pay-in (also called collection or acquiring). On the other end, you pay people — suppliers, riders, sellers, employees — that is payout (also called disbursement).

A pay-in API is what a payment gateway exposes to developers: create a payment, redirect the customer to checkout, receive a webhook when it succeeds. A payout API is the reverse: submit a transfer instruction, the provider pushes funds to the recipient's bank account or wallet, and a webhook confirms delivery.

For a simple online store, pay-in alone is enough. But the moment your business model involves paying many people — a marketplace splitting revenue with sellers, a gig platform paying riders weekly — you need both halves.

How a pay-in API works in Pakistan

That is the collection side. Rapid Gateway's developer guide walks through the exact flow with code samples.

  1. Your backend creates a payment via the gateway's API — amount, currency (PKR), the methods you accept.
  2. The customer pays on a hosted or embedded checkout with their preferred method: card (Visa/Mastercard/PayPak), Raast, JazzCash, easypaisa, bank transfer — or USDT crypto where supported.
  3. The gateway authorises the transaction and sends a signed webhook to your server.
  4. Funds settle to your business bank account — typically T+1 in Pakistan, real-time for Raast.

How a payout API works in Pakistan

Payouts can be single (refund one customer) or bulk — thousands of transfers in one batch for payroll or weekly gig settlements. Our dedicated payout API guide covers the disbursement side in depth.

  1. Your system submits a payout instruction — recipient account (IBAN, Raast ID or wallet number), amount, and rail.
  2. The provider validates the recipient and routes the transfer: Raast for instant bank credit, IBFT/1LINK for standard interbank, or a wallet push for JazzCash/easypaisa users.
  3. Funds land in the recipient's account — in real time on Raast.
  4. A webhook reports paid / failed / returned so your ledger reconciles automatically.

Pay-in vs payout at a glance

Pay-in APIPayout API
DirectionCustomer → youYou → recipient
Also calledCollection, acquiring, gatewayDisbursement, transfer, mass payout
Main rails (PK)Cards, Raast, JazzCash, easypaisa, bank, USDTRaast, IBFT/1LINK, wallet push
SettlementTo your account (T+1; Raast instant)To recipient (Raast instant)
Typical usersEvery online businessMarketplaces, gig platforms, payroll
ConfirmationSigned webhookSigned webhook

Who needs both: the platform money loop

The businesses growing fastest in Pakistan's digital economy run a complete loop — collect from one side of the market, disburse to the other:

  • Marketplaces: collect from buyers (pay-in), pay sellers their share (payout).
  • Ride-hailing & delivery: collect fares and order payments, disburse driver and rider earnings weekly or instantly.
  • Gig & freelance platforms: collect from clients, pay out to workers.
  • Insurance & lending: collect premiums or repayments, disburse claims and loan amounts.
  • Employers: collect revenue through the gateway, run salary disbursement from the same treasury.

In Pakistan, several providers now position around this full loop — Swich (a Numbers Pvt Ltd brand) markets a payment gateway plus a payouts API for gig-economy disbursements, and Simpaisa offers collection alongside disbursements, per their public materials. When you evaluate any provider for the payout side, apply the same tests as pay-in: rail coverage, webhook quality, reconciliation and SBP-framework compliance.

What to look for when combining pay-in and payout

  • Raast on both sides: instant, low-cost rails for collecting and disbursing — see our Raast guide.
  • One ledger, clean webhooks: both directions should reconcile automatically into your books; signed webhooks with idempotency are non-negotiable.
  • Wallet reach: many Pakistani recipients are wallet-first — payouts to JazzCash/easypaisa matter as much as bank credit.
  • Compliance: providers should operate under the State Bank of Pakistan framework, with KYC on your recipients where required.
  • Transparent pricing per direction: pay-in is priced as MDR (a % per transaction); payouts are usually a flat fee per transfer. Get both in writing.
  • Sandbox for both flows: you should be able to test collection and disbursement end-to-end before going live.

Frequently asked questions

What is the difference between a pay-in API and a payout API?

A pay-in API collects money from your customers into your account (the payment gateway function). A payout API sends money out from your account to recipients like vendors, workers or sellers. They are the two directions of one money flow, and platforms typically need both.

Can one provider handle both pay-in and payouts in Pakistan?

Some Pakistani providers offer both directions, while others specialise in one. It is also common to combine a dedicated gateway for collection with a separate disbursement provider — as long as both reconcile cleanly via webhooks, the split works well.

Does Rapid Gateway offer payouts?

Rapid Gateway focuses on the pay-in side: accepting cards, Raast, JazzCash, easypaisa, bank transfer, QR and USDT (TRC-20) through one integration, with T+1 settlement and published pricing. For outbound disbursements, evaluate a dedicated payout provider using the criteria in this guide — and see our payout API guide for the full checklist.

What is the fastest payout rail in Pakistan?

Raast — the State Bank's instant payment system — settles in real time, 24/7, at minimal cost, making it the fastest way both to receive customer payments and to disburse funds to any Pakistani bank account or Raast ID.

The bottom line

Pay-in and payout are two halves of the same infrastructure: one API collects, the other disburses, and Raast now makes both sides fast and cheap in Pakistan. Get the collection side right first — it funds everything else — then add disbursements when your model needs to pay people at scale.

For the pay-in half, Rapid Gateway unifies every Pakistani payment method with transparent pricing and same-day onboarding — create a free account, or start with the step-by-step guide to accepting online payments.

Ready to start accepting payments?

Set up Rapid Gateway in minutes. No setup fees, no monthly subscriptions.

Create Your Free Account