Add online payments to your platform
Do you run a platform that serves merchants? Connect your platform to SwiftPayIQ once, and your merchants accept payments from inside your own system, without building a payment system from scratch.
Each merchant stays independent, with their own account, documents and funds. We handle the technical integration layer.
What is the Partner Program?
If your platform serves a number of merchants, whether it is an online marketplace, a delivery app, an ERP or point-of-sale system, a booking platform or a SaaS product, each of those merchants needs a way to accept online payments.
Today, each of them has to find a provider on their own, sign up on their own and connect their system on their own. Most of them won't.
The Partner Program makes this part of your platform: you connect your platform to SwiftPayIQ through one technical integration, then bring your merchants in through that integration. Each merchant gives their own consent, their application is reviewed, and once they are approved your platform can create invoices and payment links and track the status of every transaction on their behalf.
One integration that serves all your merchants, instead of a separate integration for each one.
Who is this program for?
Online marketplaces
A platform that brings together a number of sellers. Each seller sells under their own name and receives their own funds directly.
Delivery and booking apps
Restaurants, clinics, hotels, training centers: each business in your app becomes an independent merchant.
ERP and point-of-sale systems
Accounting or sales management software that serves many companies and wants to add online payments to its product.
Software companies
You build solutions for your clients and want online payments to be part of what you deliver.
SaaS products
A subscription product that serves business owners, where you want payment to stay inside the user experience.
If you are a single merchant who wants to accept payments, our page for merchants is the right place.
How the money moves
This is the most important point in the program, so we state it clearly before any technical detail.
Each merchant receives their own funds.
Transaction amounts go from the licensed payment gateways directly to the merchant's own account. They don't pass through your platform, and they don't pass through SwiftPayIQ.
SwiftPayIQ is a technical intermediary platform that connects merchants to licensed payment gateways. It does not hold anyone's funds or route them between parties. Likewise, the partner does not receive funds on behalf of their merchants or distribute funds to them.
Why is this in your interest?
- You don't carry responsibility for your merchants' funds. Each merchant is responsible for their own sales and for any dispute about them.
- Your merchants' transactions are not concentrated in a single entity, so your accounting and administrative burden doesn't swell.
- Merchants see their funds reach them in their own name, so they trust your platform more, not less.
As for your own commission on your platform's services, you collect it from your merchants in the way you choose within your platform, outside the payment flow. Your Dashboard shows your referred merchants' transactions, so you can calculate it accurately.
What a partner can and cannot do
The partner can
- Start registering a new merchant and prepare their details
- Create payment links and invoices in a referred merchant's name
- Read the status of a referred merchant's transactions
- Track the status of each merchant's application and see what is missing
- See all their referred merchants in one place
The partner cannot
- Sign in as a merchant or act on their behalf beyond the permissions granted
- View a merchant's personal documents
- View payment gateway credentials
- Hold, move or otherwise touch any merchant's funds
- Change a merchant's payout method or destination
The merchant grants every permission themselves and can disconnect at any time from their account settings. When they disconnect, your platform's key for that merchant stops working immediately, while their account, funds and own keys stay as they are.
The merchant journey, step by step
- 01
Your platform starts the connection
Your platform calls the connection API, and a page we host opens for the merchant.
- 02
The merchant confirms their identity
They confirm their phone number with a code sent to them, and agree themselves to the terms and to connecting their account to your platform.
- 03
Documents
They upload their ID documents and a business document. You can also prepare their details and upload their documents for them.
- 04The gateway decides
Review
The application is reviewed by the verification team of the gateway you chose, who decide whether the account is opened. We do not set a timeline for the review, and approval is not guaranteed.
- 05
Going live
Once approved, your platform can create invoices and payment links and track transaction status, and the merchant receives their funds in their own account.
Frequently asked questions
Can I collect my merchants' funds in my own account and then distribute them?
Do you support automatic payment splitting between the merchant and my platform?
Does each merchant need their own account?
How many merchants can I connect?
Do I need any extra steps, such as setting up a new company?
What documents does each merchant need?
How long does the review of a merchant's application take?
Which cards are supported?
What happens if a merchant leaves my platform?
Can I see my merchants' sales?
Is there a setup or integration fee?
Is the program available now?
Talk to us before you build
We set up your return URL, issue your partner key and review your integration plan with you. A short conversation now saves long ones later.
Technical details for developers
Run payments for merchants who are not yours
You have merchants. We connect your merchants to a licensed payment gateway in Iraq. This is how a merchant on your platform becomes one who can take card payments through us — without either of us asking them to copy a secret between two websites.
There are two kinds of key
Almost every integration problem we see comes from using one where the other belongs. They are not interchangeable and they are not the same length of trust.
spp_live_…Your partner key. One per platform.
- Identifies you, never a merchant
- Starts onboarding and swaps codes
- Cannot take a payment or read one
- Lives on your server, always
spi_live_…A merchant key. One per merchant you connect.
- Acts as that one merchant, and only them
- Creates payment links, invoices, reads payments
- Handed to you once and never shown again
- Dies the moment the merchant disconnects you
A merchant key is returned exactly once. We keep only a hash, so we cannot show it to you again — persist it before you respond to the request. Lose it and the merchant has to authorise you from the beginning.
The merchant never touches a secret
We do not ask a merchant to copy a key and paste it into your site. They would not know what it was, they would paste it in the wrong box, and a secret that travels through a clipboard and a support chat is a secret nobody controls any more.
Connecting your first merchant
Send the merchant to a page we host
Call this with your partner key. You get back a single-use URL — open it for the merchant in a new tab. Every screen that touches a password or a verification code stays on our domain, so their credentials never pass through your servers.
POST /api/v1/partner/onboarding-sessions
Authorization: Bearer spp_live_…
Content-Type: application/json
{ "phone": "+9647701234567" }The page reads the merchant's own records each time rather than storing a step number, so somebody who stops halfway through uploading documents and comes back next week lands on exactly the screen they left.
They come back to you carrying a code
We return the merchant to the address registered for your account with ?code= on the end. The code grants nothing on its own. It is worth something only in combination with your partner key, which is why it is safe for it to travel through a browser redirect.
Your server swaps the code for the merchant's key
POST /api/v1/partner/connections/exchange
Authorization: Bearer spp_live_…
{ "code": "…" }You receive that merchant's own spi_live_… key. From here you act as them: create payment links, issue invoices, read their payments.
Sometimes no code comes back
A merchant who already trades with SwiftPayIQ is not handed to a platform on the strength of one button press. When they connect a business they already had, we record their consent and then wait for one of our admins to approve it.
Their consent is real and dated. What is missing is our decision — so they return to you with no code, and there is nothing for you to exchange yet.
Collecting them afterwards
Once an admin approves, the merchant is waiting for you to pick up. Ask for what is ready when you are able to exchange straight away — each entry carries a fresh code that lives five minutes.
GET /api/v1/partner/connections/pending
Authorization: Bearer spp_live_…
[
{
"businessId": "…",
"businessName": "Al Amal Store",
"code": "…",
"scopes": ["payment_links:write", "invoices:write", "payments:read"],
"expiresAt": "2026-09-04T20:31:00.000Z"
}
]An entry disappears once you hold a key for that merchant, so a run that fails halfway is safe to repeat — you are simply offered the ones you did not finish. An empty array means nothing is waiting.
What the refusals mean
| Error | What happened |
|---|---|
| partner.no_redirect_uri | No return address is registered for your account, so a finished journey would have nowhere to go. Ask our team to set it before you start. |
| partner.connection_code_invalid | Unknown, expired, already used, or issued for a different partner. One message covers all four on purpose — telling you which codes exist would tell an attacker the same. |
| partner.link_already_pending_review | This merchant's request is already on our desk. Nothing to retry; wait for the decision and collect them from the pending list. |
| partner.business_already_linked | The business belongs to a live connection already — yours or another platform's. A business has one partner at a time. |
Two limits worth knowing
The exchange endpoint accepts 30 requests a minute, which is far more than you need — you call it once per merchant, not once per payment. And a code is single use: if your server sends the same one twice at the same moment, exactly one wins and the other is refused.
A merchant can disconnect you at any time from their own settings. The key we issued you for that business stops working immediately; keys they created themselves are untouched.
SwiftPayIQ is a technical intermediary platform that connects merchants to licensed payment gateways, which process and settle the payments.