Curated market guide
Iraq PSP routes to verify first
Which PSPs, acquirers, gateways, and local payment routes should a merchant ask first for Iraq?
central bank listed electronic payment provider
Prioritize this when you need wallet, mobile payment, issuer, processor, collector, or gateway capabilities from a provider listed by the Central Bank of Iraq.
Treat Iraq as a high-verification market. Ask every provider whether an Iraqi company, local bank account, tax registration, local representative, local signatory, or bank sponsor is mandatory, and confirm sanctions, AML, restricted-category, and data requirements with counsel before contracting.
- Which Central Bank of Iraq listed role applies to your merchant product: issuer, processor, collector, mobile payment, QR collection, gateway, or another role?
- Can my current merchant entity onboard, or do you require an Iraqi company, Iraqi bank account, local tax profile, or local representative?
- Which checkout flows, refunds, disputes, reconciliation files, and customer support routes are available for my category?
bank or qr collection route
Prioritize this when the use case depends on QR-code collection, bank account settlement, government or bill collection, or a bank-led acquiring relationship.
Treat Iraq as a high-verification market. Ask every provider whether an Iraqi company, local bank account, tax registration, local representative, local signatory, or bank sponsor is mandatory, and confirm sanctions, AML, restricted-category, and data requirements with counsel before contracting.
- Are you licensed or approved for QR-code collection, electronic collection, or payment facilitation for merchants?
- Which bank account, settlement, compliance, and local documentation requirements apply?
- Does the route support ecommerce, in-person QR, app payments, invoices, or only selected bill-collection flows?
regional or cross border psp
Prioritize this only for preliminary screening if the merchant lacks an Iraqi entity and needs to understand whether Iraq can be served through a partner route.
Treat Iraq as a high-verification market. Ask every provider whether an Iraqi company, local bank account, tax registration, local representative, local signatory, or bank sponsor is mandatory, and confirm sanctions, AML, restricted-category, and data requirements with counsel before contracting.
- Is Iraq supported for merchant collection, payout, card acceptance, wallet acceptance, or only informational routing?
- Which local provider or bank is the contracting, acquiring, processing, or settlement partner?
- Which sanctions, AML, prohibited-category, local licensing, and documentation checks apply before any commercial discussion?
CBI-listed electronic payment provider
The Central Bank of Iraq publishes electronic payment provider lists with roles such as mobile payment, issuer, processor, and collector.
Treat Iraq as a high-verification market. Ask every provider whether an Iraqi company, local bank account, tax registration, local representative, local signatory, or bank sponsor is mandatory, and confirm sanctions, AML, restricted-category, and data requirements with counsel before contracting.
- Verify the provider against the CBI page first, then ask for merchant onboarding and compliance requirements for the exact role.
- Which Central Bank of Iraq listed role applies to your merchant product: issuer, processor, collector, mobile payment, QR collection, gateway, or another role?
- Can my current merchant entity onboard, or do you require an Iraqi company, Iraqi bank account, local tax profile, or local representative?
QR-code collection or electronic collection institution
CBI publishes a dedicated page for institutions approved to provide electronic financial collection and QR-code collection services.
Treat Iraq as a high-verification market. Ask every provider whether an Iraqi company, local bank account, tax registration, local representative, local signatory, or bank sponsor is mandatory, and confirm sanctions, AML, restricted-category, and data requirements with counsel before contracting.
- Ask whether the provider can onboard your merchant category for QR or collection, and do not treat a listed contact as proof of ecommerce capability.
- Which Central Bank of Iraq listed role applies to your merchant product: issuer, processor, collector, mobile payment, QR collection, gateway, or another role?
- Can my current merchant entity onboard, or do you require an Iraqi company, Iraqi bank account, local tax profile, or local representative?
Documents to prepare
- Company registration certificate and operating entity details.
- Beneficial-owner, director, and signatory identity documents.
- Business website/app URLs, product description, refund policy, terms of service, and restricted-category explanation where relevant.
- Bank account, settlement currency, tax/VAT/GST information, and expected processing volume.
Questions to ask
- Can my current merchant entity onboard, or is a local company or bank account required?
- Which local payment methods are live for my business category and customer flow?
- What documents are required for KYB, technical review, and production approval?
- How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
- Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
If the official contact route is unclear
Use the Central Bank of Iraq provider list, approved collection page, official provider website, bank relationship route, or public merchant form first. If no safe merchant route is visible, ask LocalPayMap for routing research rather than contacting unrelated consumer support.
- Which local payment methods are live for my business category and customer flow?
- What documents are required for KYB, technical review, and production approval?
- How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
- Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
Route comparisons
CBI-Listed Electronic Payment Provider vs Bank or QR Collection Route in Iraq
How local customers usually pay
Iraq is a high-friction market for cross-border payment acceptance. Cards, bank transfers, mobile wallets and cash-on-delivery may all appear, but merchant onboarding, banking relationships, sanctions screening, product category review and settlement rules need unusually careful checking. A small merchant should avoid announcing local payment methods before a provider confirms that the merchant entity, customer geography, goods and currencies are acceptable. Treat any provider claim as preliminary until compliance approval is written. For many overseas merchants, a regional PSP may still require enhanced due diligence or may decline certain industries. Keep the first conversation focused on eligibility and risk.
- Cards or hosted checkout only after enhanced compliance review. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Wallet or bank-transfer options where a licensed local or regional provider confirms support. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Cash-on-delivery or offline collection only with legal, tax and fulfilment review. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
Payment methods to check first
For Iraq, begin with the methods that match real customer behavior, then map each one to a provider that can actually onboard your merchant. Current public records point to Card acquiring, General commerce, Digital wallet, Instant payment and Bank transfer, but availability can vary by PSP, entity type and industry.
- Start with the payment method customers already recognize, not the provider with the longest logo wall.
- Check whether the method supports online checkout, payment links, QR, app redirects, refunds and clear transaction references.
- Keep one fallback method for buyers who cannot or will not use cards.
- Document which method is mandatory for launch and which can wait for phase two.
What to do if you do not have a local company
Iraq needs conservative eligibility review before any commercial commitment. A foreign merchant should ask risk and compliance questions first, then payment-method questions only after the provider confirms that the company location, owners, customers, product category and settlement route can be supported.
- Ask whether foreign entities are accepted directly or only through a local subsidiary, distributor or merchant-of-record arrangement.
- Confirm local company, tax ID, local bank account, local director, licence and proof-of-address requirements.
- Ask which settlement currencies and payout countries are supported for your entity.
- Get the onboarding answer in writing before promising a local method to customers.
PSP and four-party provider screening
Use provider discovery to separate customer-facing payment brands from the companies that can legally process and settle funds. Public PSP/contact leads for Iraq currently include local PSPs, banks, gateways and aggregators. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.
- Ask regional PSPs and local banks which Iraq methods are live for your merchant category.
- Request links to official onboarding, developer documentation, support and pricing pages.
- Do not rely on marketplace claims unless the provider confirms your entity and industry in writing.
Settlement, currency, refunds and disputes
Treat all pricing and settlement information for Iraq as preliminary until confirmed by the official provider or contract. Fees, payout timing, rolling reserves, FX, chargeback costs and refund rules can change by industry, volume, risk review, settlement currency and integration route.
- Ask for transaction fee, fixed fee, refund fee, chargeback fee, payout fee, FX spread, reserve policy and minimum monthly or setup charges.
- Confirm payout timing, settlement currency, settlement account country, failed-payout handling and reconciliation file fields.
- Check whether refunds must return through the original method and whether partial refunds are supported.
- For cards, confirm dispute workflow, evidence deadlines, chargeback fees and fraud-monitoring rules.
Compliance and operating checks
Before launch in Iraq, prepare KYB and risk material as if the provider will ask for it. Most delays for new merchants come from unclear ownership, unsupported industries, missing licences, incomplete websites, weak refund policies or settlement accounts that do not match the merchant record.
- Prepare company registration, ownership, director ID, website/app URL, product description, terms, privacy policy and refund policy.
- Disclose regulated products, digital content, subscriptions, marketplace activity, high-risk categories and cross-border fulfilment.
- Ask how the provider screens sanctions, fraud, AML risk, chargebacks and customer complaints.
- Keep sensitive or restricted markets at compliance-review level; do not use unofficial workarounds.
Questions to ask service providers
Send a concise written checklist to every Iraq PSP or aggregator so responses can be compared side by side. The goal is to expose hidden entity, settlement, support and technical gaps before engineering work begins.
- Which payment methods are live today for my exact merchant entity, industry and customer geography?
- Do you support hosted checkout, API, plugin, payment links, webhooks, sandbox, refunds and reconciliation exports?
- Who is the merchant of record, who handles chargebacks and who owns customer support for failed payments?
- What documents are requested, how is approval reviewed, and what would cause rejection?
- Can you provide official links for pricing, settlement terms, developer docs and support escalation?
Common beginner mistakes
The most common mistake in Iraq is treating payment acceptance as a logo checklist. Local conversion depends on customer habit, provider eligibility, settlement flow, refund support and operational reliability. A cheaper-looking route can become expensive if it cannot settle where you need, cannot refund cleanly or cannot support the methods buyers expect.
- Choosing cards only when wallets, mobile money, bank transfer, QR or cash-style routes are normal for local buyers.
- Building against an API before KYB, entity and settlement eligibility are confirmed.
- Ignoring refund and dispute flows until the first customer complaint arrives.
- Comparing providers without asking the same written questions of each one.
Questions merchants ask
Which payment methods should a new merchant check first in Iraq?
Start with Card acquiring, General commerce, Digital wallet, Instant payment and Bank transfer. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.
Can a foreign merchant accept local payments in Iraq without a local company?
Sometimes, but it must be verified provider by provider. Ask whether a local entity, local bank account, tax ID, licence, local director or merchant-of-record route is required.
Which PSPs or aggregators are worth screening for Iraq?
Public leads include local PSPs, banks, gateways and aggregators. Treat them as a shortlist for outreach, not as confirmed eligibility or complete market coverage.
Can I use public fee pages as a final quote?
No. Public fees are screening context only. Final pricing can vary by country, industry, volume, risk review, settlement currency, FX, reserves and contract terms.
What operational questions should I ask before integration?
Ask about onboarding documents, restricted industries, live payment methods, checkout flow, webhooks, sandbox, refunds, disputes, chargebacks, reconciliation files, settlement timing and support escalation.
What should I do if the provider has no public sales email?
Use the official contact form, support page or developer contact route, and send a short brief with your entity country, product, volume, currencies and required payment methods.