Iran Payments Guide

Payments in Iran: Market Scale Under Severe International Payment Constraints Iran has a functioning digital-payment economy. Domestic consumers use bank cards, online banking, mobile applications, card-to-card transfers, payment gateways, and locally operated financial infrastructure. World Bank financial-inclusion data indicate that 86% of Iranian adults had an account in 2024, while 76% of women and 81% of men reported making or receiving a digital payment under the World Bank’s broad definition. (Digital Finance) That sounds like a promising foundation for ecommerce. For an international merchant, however, it describes only one side of the transaction. The other side contains the institution that must contract with the merchant, the bank that must receive the funds, the currency in which they settle, the network that must carry the payment, the jurisdiction governing the merchant, the product being supplied, and the sanctions and export-control rules that may prohibit or restrict the activity. Iran’s domestic payment system can be highly functional for domestic participants while remaining largely inaccessible to an ordinary foreign merchant. This creates the central rule for evaluating Iran: Do not begin with consumer demand or payment-method popularity. Begin by establishing whether the merchant, product, customer, provider, bank, currency flow, data model, and settlement route can lawfully and practically participate.

Iran remains subject to multiple overlapping U.S. sanctions authorities, and OFAC maintains a dedicated Iran sanctions program containing regulations, executive orders, licenses, guidance, designations, and frequently updated actions. The EU also maintains several Iran-related sanctions regimes and reimposed nuclear-related restrictive measures in September 2025 through the sanctions “snapback” process. Additional EU designations followed in 2026. (OFAC) The result is not a simple universal statement that every Iran-related transaction is prohibited in every jurisdiction. It is a transaction-specific analysis involving: * The merchant’s jurisdiction * Ownership and control * The product or service * The customer and beneficial owner * End use and end user * Banks and payment providers * Currency * Intermediaries * Export-control classification * Sanctions lists * Available licenses or exemptions * Data and technology transfers * Settlement and repatriation Until those questions are resolved, Iran is not a conventional payment-localization project. Iran payment snapshot Category Iran Region Middle East and Western Asia Population Approximately 92 million in World Bank 2025 data; the IMF currently lists roughly 87.9 million, illustrating meaningful source differences Currency Iranian rial, IRR; toman is commonly used colloquially as a pricing unit 2025 GDP per capita Approximately US$3,924 in current-dollar World Bank data Implied 2025 nominal GDP

Approximately US$361 billion using the World Bank population and per-capita figures Economic rank The brief’s 44th-place estimate requires final verification against a selected nominal-GDP dataset and year Domestic payment maturity High account ownership and extensive domestic electronic-payment use Domestic infrastructure Shetab interbank card infrastructure and Shaparak-regulated retail-payment environment International card access Ordinary Visa, Mastercard, and other international card acceptance cannot be assumed International banking access Severely constrained by sanctions, institutional restrictions, and correspondent-banking risk SWIFT access EU-sanctioned Iranian banks have been disconnected where required by applicable EU regulation Currency complexity Very high due to inflation, multiple exchange-rate contexts, controls, and conversion constraints Local acquiring relevance Essential for domestic card access, but generally unavailable to an ordinary foreign merchant without an approved local structure Settlement complexity Extreme Recurring-payment readiness Possible within domestic systems, but highly provider- and structure-specific Regulatory complexity Extreme and multinational Merchant recommendation Do not analyze commercial opportunity until legal access, payment connectivity, and usable settlement are independently confirmed

The IMF’s Iran page currently projects a 5.4% real GDP contraction and 68.9% average consumer-price inflation for 2026, while listing a population of approximately 87.9 million. These are projections produced amid unusually high economic and geopolitical uncertainty, not stable merchant-planning assumptions. (IMF) The World Bank’s 2025 Data360 profile instead reports a population of about 92 million and GDP per capita of US$3,924. Differences in source dates, methodologies, and demographic estimates mean the population and nominal-GDP rank should be verified consistently before publication. (World Bank Open Data) The Iran market-entry feasibility gates A merchant should not proceed to the next gate unless the previous one has a documented, current, and defensible answer. Gate 1: Is the activity legally permissible? The merchant must determine whether its proposed product, service, technology, support, or transaction is permitted under every applicable sanctions and export-control regime. Relevant jurisdictions can include: * The merchant’s incorporation jurisdiction * Parent-company jurisdictions * Employee locations * The location of servers and cloud infrastructure * The provider’s jurisdiction * The acquiring bank’s jurisdiction * Correspondent-bank jurisdictions * The customer’s location * The location of beneficial owners * The currency-clearing jurisdiction A company outside the United States may still encounter U.S. restrictions because of: * U.S.-origin goods or technology

* U.S. persons * U.S. financial institutions * U.S. dollar clearing * Ownership or control * Secondary-sanctions exposure * Export Administration Regulations * Designated counterparties OFAC describes the Iran sanctions program as the implementation of multiple legal authorities rather than one rule. That makes activity-specific legal analysis essential. (OFAC) Required evidence Obtain written advice covering: * The exact product or service * Customer type * Customer location * End use * End user * Merchant entity * Payment structure * Provider * Banks * Currency * Technology transfer * Support and maintenance * Data processing * Refunds * Contract termination * Applicable licenses or exemptions A provider saying “we can process it” is not a substitute for the merchant’s legal analysis. Gate 2: Are the parties and institutions acceptable? Screen more than the customer’s name. Potentially relevant parties include: * Customer * Customer owners * Customer directors * End users * Recipient * Shipping party * Reseller * Distributor * Marketplace seller * Local agent * Provider * Acquirer * Issuing bank * Settlement bank * Correspondent bank * Foreign-exchange provider * Technology partner OFAC provides sanctions-list services and a searchable sanctions-list tool, while the U.S. International Trade Administration maintains a Consolidated Screening List covering restrictions administered by several U.S. agencies. (OFAC)

Screening must also account for ownership and control. A company that is not named directly may still be treated as restricted under applicable aggregation or ownership rules. Fail conditions Pause the transaction when: * A blocked party is involved * Ownership cannot be established * End use is unclear * The payment route obscures the beneficiary * The proposed intermediary appears intended to circumvent restrictions * Required licenses are absent * The bank or provider refuses the activity * Counsel cannot establish a defensible legal basis Gate 3: Can the product legally be supplied? Digital merchants often underestimate export controls because no physical shipment occurs. Potentially controlled activities can include: * Software downloads * Software-as-a-service access * Encryption * Cybersecurity products * Cloud computing * Hosting * Technical support * Updates and patches * Telecommunications tools * Industrial software * Engineering services * Data analytics * Artificial intelligence * Developer infrastructure * Remote administration * Professional services The U.S. government’s export-control framework covers exports, reexports, and transfers of controlled items and technology, including some intangible deliveries. (Trade.gov) The merchant must classify the product before deciding how to charge for it. Gate 4: Is a permitted provider available? A domestic method can exist without being commercially available to a foreign merchant. The merchant needs written confirmation addressing:

* Contracting entity * Merchant jurisdiction * Merchant category * Product * Customer location * Transaction type * Domestic payment methods * Underlying banks * Settlement account * Settlement currency * Cross-border payout * Refunds * Recurring payments * Data processing * Sanctions responsibilities * Termination rights A provider’s generic “Middle East coverage” or country list is not sufficient. Questions to ask * Which legal entity provides the service? * Is that entity allowed to contract with the merchant? * Which Iranian institutions are involved? * Are any of them designated? * What happens if a bank is newly sanctioned? * Where do funds settle? * Can funds leave Iran? * Can refunds be returned? * Who performs customer and counterparty screening? * Who bears frozen-fund risk? * Can the provider terminate immediately after a sanctions change? * What records will the merchant receive? Gate 5: Can customers access the payment method? Iran has a mature domestic card and account-payment environment, but ordinary international card interoperability is severely limited. Domestic access may include: * Locally issued bank cards * Card-to-card transfers * Domestic payment gateways * Bank-account transfers * Mobile-banking applications * QR or app-based payment * Domestic wallets * Bill-payment infrastructure

The Shetab system connects Iranian banks for domestic card and interbank functionality, while Shaparak operates as a central part of the regulated retail-payment environment. Reliable current primary-source documentation in English is limited, so the precise structure, volume, membership, and capabilities require specialist verification before publication. The key distinction is: A method can be widely used by Iranian residents and still be inaccessible to an international merchant. Gate 6: Can funds settle into an approved, usable account? A completed customer payment has no commercial value if the merchant cannot lawfully receive and use the proceeds. The merchant must trace: Customer → issuing institution → domestic payment network → provider → settlement bank → foreign-exchange conversion → correspondent bank → merchant account At each stage, determine: * Institution identity * Ownership * Sanctions status * Currency * Jurisdiction * Legal basis * Processing time * Conversion method * Documentation * Rejection risk * Freeze risk * Refund route Usable settlement rate Funds received in an approved and accessible merchant account ÷ completed customer-payment value × 100 A transaction paid domestically but trapped in an inaccessible account should not be counted as successful merchant revenue. Gate 7: Can refunds and reversals be operated? Before accepting a payment, the merchant must know whether it can return it. Verify: * Full refund * Partial refund * Multiple partial refunds * Authorization reversal

* Failed refund * Refund after settlement * Refund after provider termination * Refund if the original bank is designated * Refund currency * Customer receipt * Reconciliation A merchant should not accept prepaid consumer funds if it cannot establish a reliable and lawful reimbursement process. Gate 8: Can the data and technology model comply? Payment acceptance may involve: * Customer identity * Payment credentials * Device information * IP address * Transaction history * Location * Sanctions-screening data * Customer-support records * Cloud services * Encryption * Fraud tools The merchant needs current professional advice on Iranian requirements involving: * Personal data * Local hosting * Cybersecurity * data transfers * encryption * telecommunications * government access * retention * customer consent The analysis must also consider the merchant’s home-jurisdiction privacy and export-control obligations. Gate 9: Can the operating model survive a sudden change? Iran-related restrictions can change quickly. The merchant needs procedures for: * New sanctions * Bank designation * Provider exit * Currency interruption * Frozen settlement * Service suspension * Refund backlog * Data access * customer communication * subscription termination * contract wind-down A model that works only while every institution remains unchanged is not operationally ready. Economic scale and what it does—and does not—mean

Iran is a large population market with substantial domestic production, energy resources, industry, services, and consumer demand. Yet nominal-dollar GDP can be difficult to interpret because of: * Exchange-rate differences * Inflation * Currency controls * Official and market-rate divergence * Statistical revisions * Sanctions-related trade distortion * Economic volatility The World Bank’s 2025 population and GDP-per-capita figures imply nominal GDP of roughly US$361 billion, but this should not be presented as a precise final estimate without confirming the underlying series. (World Bank Open Data) The IMF projects severe contraction and inflation in 2026, while the World Bank describes the outlook as subject to substantial downside risk from conflict, sanctions, social disruption, oil-market exposure, and import constraints. (IMF) For merchants, economic size does not answer: * Whether the activity is legal * Whether customers can pay the merchant * Whether the merchant can settle * Whether pricing can remain stable * Whether refunds can be made * Whether the provider will continue service * Whether revenue can be repatriated Iran’s economic rank should therefore appear as context, not as a recommendation to enter. Domestic digital maturity Iran’s domestic digital-finance profile is stronger than its international payment accessibility. World Bank 2024 data show: * Account ownership of approximately 86% for both women and men * Digital-payment use of approximately 76% among women

* Digital-payment use of approximately 81% among men The World Bank definition includes adults who used mobile money, a card, a phone, or the internet to make or receive specified payments during the prior year. It is not an ecommerce-market-share measure. (Digital Finance) These figures support three conclusions: 1. Domestic electronic-payment behavior is widespread. 2. Bank and account infrastructure reaches much of the adult population. 3. International merchant access cannot be inferred from domestic adoption. No single reliable digital-economy percentage A current, internationally comparable official measure of Iran’s digital economy as a share of GDP was not established from the sources reviewed. The guide should therefore use a maturity profile based on: * Account ownership * Digital-payment use * Internet access * Mobile connectivity * Domestic ecommerce * Online banking * Domestic card infrastructure * Technology and platform use Any percentage attributed to the “digital economy” should state: * The producing institution * Definition * Year * Included sectors * Whether it is an estimate * Whether sanctions-constrained or informal activity is captured The domestic payment system Shetab Shetab is Iran’s domestic interbank card and electronic-banking network. From the consumer’s perspective, it supports interoperability among participating domestic banks for functions such as: * Card payments * ATM access * Interbank activity * Domestic transfers

From the merchant’s perspective, the important questions are: * Can the merchant legally obtain domestic acceptance? * Which acquirer or PSP supplies it? * Which bank settles it? * Is a local entity required? * Can the merchant category be onboarded? * Are online recurring payments supported? * How are refunds handled? * Can proceeds be transferred abroad? Domestic ubiquity does not answer any of those questions for a foreign merchant. Shaparak Shaparak is associated with the supervision and routing of Iran’s domestic electronic retail-payment environment. A merchant considering local connectivity would need verified current information on: * Licensed PSPs * Payment facilitators * Gateway rules * Merchant onboarding * technical standards * transaction limits * authentication * settlement * refunds * disputes * reporting * data storage Current official English-language documentation should be obtained directly through qualified local legal and payment specialists rather than inferred from secondary summaries. Domestic bank cards Locally issued cards can be widely usable inside Iran while being unusable on ordinary international card networks. The merchant should distinguish: * Domestic debit or account-linked card * International-network card * Domestic acceptance * Cross-border acceptance * Card-not-present capability * Recurring capability * Tokenization * Refund support A consumer’s domestic card ownership does not mean the card can be charged by a foreign PSP. International card networks

Visa and Mastercard acceptance should not be presented as part of a normal Iran launch stack. Sanctions, network policy, bank access, and domestic isolation make ordinary international-card acceptance highly constrained. Specific exceptions, niche travel arrangements, or third-country structures should not be generalized into merchant availability. Any provider claiming international card access in Iran should be subjected to enhanced due diligence: * Legal basis * Acquirer * Issuer route * settlement bank * currency * customer eligibility * merchant eligibility * sanctions analysis * refund process * contractual protection SWIFT and correspondent banking SWIFT states that it disconnected Iranian financial institutions subject to EU sanctions when legally required and that it must comply with applicable EU restrictions because it is incorporated under Belgian law. (Swift) SWIFT access itself is not the same as permission to transact. A bank can also refuse Iran-related activity because of: * Sanctions exposure * Risk appetite * Correspondent-bank requirements * Anti-money-laundering controls * Documentation * Currency-clearing restrictions * Reputational risk The merchant must verify the entire bank chain, not merely whether a BIC exists. Payment-method accessibility matrix The matrix below describes the distinction between domestic relevance and likely international-merchant feasibility. It is not a recommendation to use any method. Method Domestic relevance Ordinary foreign-merchant accessibility

Required conclusion Iranian domestic bank cards High Generally inaccessible through ordinary international PSP arrangements Requires lawful local provider, acquiring, entity, bank, and settlement structure Domestic online bank gateway High Restricted and provider-specific Requires local onboarding and legal approval Card-to-card transfer Common domestic behavior Poor fit for ordinary scalable international ecommerce High reconciliation, identity, compliance, and refund risk Domestic bank transfer Material Bank-, party-, currency-, and sanctions-sensitive Specialist legal and treasury review required Local wallets or payment applications Potentially relevant Operator- and provider-specific Review ownership, bank, licensing, settlement, sanctions, and refunds Visa or Mastercard Not a normal domestic route for international merchants Highly constrained Do not treat as a launch assumption Foreign wallet funded by international card Generally limited Highly constrained Requires network and provider verification Cash Domestic use possible Does not solve international settlement Usually unsuitable for international digital commerce Cryptocurrency Technically possible in some contexts Legally and sanctions-sensitive Never treat as a sanctions workaround Third-country intermediary Possible in informal structures High circumvention and enforcement risk Do not proceed without explicit legal approval Cryptocurrency is not a compliance shortcut

A merchant should not use cryptocurrency, stablecoins, informal transfer systems, or third-country entities to conceal an Iran-related transaction or evade financial restrictions. Digital assets may introduce additional issues involving: * Sanctions * Wallet screening * Exchange screening * beneficial ownership * source of funds * destination * money laundering * transaction monitoring * export controls * prohibited counterparties * settlement * accounting * volatility A transaction does not become lawful because it avoids a bank. The legal question remains: * Who is sending value? * Who receives it? * What is being supplied? * Which jurisdictions apply? * Is the route intended to circumvent a restriction? Currency and pricing Iran’s official currency is the Iranian rial, code IRR. In everyday commerce, prices may be described in tomans, where one toman is commonly understood as ten rials. Merchants must not assume that customers, providers, invoices, accounting systems, and APIs use the same unit. This creates a serious implementation risk. Required currency controls Every transaction record should identify: * Display unit * Currency code * Numeric amount * Decimal policy * Conversion source * Conversion timestamp * Settlement unit * Accounting unit A merchant must prevent a tenfold amount error caused by confusing rial and toman. Exchange-rate complexity The merchant may encounter: * Official rates * administered rates * preferential rates * provider rates * market rates * restricted conversion

* changing settlement rates Do not publish a single “Iranian exchange rate” without stating: * Source * Date * Market * Purpose * Availability to the merchant Inflation and price validity The IMF’s current 2026 projection of 68.9% average consumer-price inflation illustrates how quickly fixed local-currency pricing can become commercially obsolete. (IMF) Merchants would need controls for: * Frequent repricing * Quote expiration * Subscription repricing * Customer notification * Refund amount * accounting * tax * FX loss * prepaid balances Settlement currency A merchant may theoretically accept a rial-denominated domestic payment but be unable to convert or remit the proceeds. Distinguish: * Customer presentment currency * Domestic processing currency * Provider settlement currency * Conversion currency * Cross-border payout currency * Merchant reporting currency The ability to price in IRR is not evidence of international payout. Local acquiring and cross-border processing Domestic acquiring is effectively necessary for ordinary Iranian domestic-card acceptance. Yet “local acquiring” is not one capability. It can involve: * Local legal entity * Local merchant account * Domestic bank account * Licensed domestic PSP * Local gateway * Merchant-category approval * Tax registration * Local settlement * Data obligations * Domestic customer support For an international merchant, each element raises separate sanctions, contractual, regulatory, tax, and governance questions. Cross-border processing

Conventional cross-border card processing cannot be assumed to reach Iranian domestic cards. Potential alternatives described by providers should be tested for: * Lawfulness * Transparency * named institutions * actual settlement route * customer protection * refundability * documentation * ongoing availability Avoid arrangements where: * The true customer location is misrepresented * The merchant descriptor is misleading * A reseller disguises the original transaction * A third party receives funds without legitimate commercial purpose * The route depends on false invoicing * Payment purpose is obscured Authentication and customer verification Domestic Iranian customers may authenticate through: * Card credentials * One-time passwords * Banking applications * Device confirmation * Local identity information * Merchant or provider account credentials The merchant must establish: * Who collects the data * Where it is stored * Whether export controls apply to the technology * Whether personal-data rules apply * Whether the provider supplies a reliable result * How failed authentication is handled * Whether customer support can assist lawfully International 3-D Secure assumptions should not be mapped automatically onto domestic Iranian card flows. Recurring payments and subscriptions A domestic payment method that supports a one-time purchase may not support an unattended recurring transaction. Subscription merchants need written confirmation of: * Initial customer authorization * Stored credential * mandate * token

* recurring indicator * payment schedule * cancellation * price changes * failed-payment recovery * refunds * customer notice * provider continuity Sanctions-change risk A subscription relationship may become impossible after: * New designation * Provider withdrawal * Bank restriction * Currency interruption * Product-control change * Customer-status change The merchant needs: * Immediate suspension logic * Service termination rules * Customer communication * Refund assessment * Data retention * account closure * legal escalation Recurring revenue should not be accepted if the merchant cannot operate an orderly wind-down. Refunds, reversals, and disputes Method popularity is irrelevant if the merchant cannot return funds. For each proposed method, confirm: * Native refund support * Partial refunds * Refund deadline * Customer action * Bank details needed * Refund currency * Exchange-rate treatment * Failed-refund procedure * Provider termination procedure * Sanctions-change procedure * Reporting and reconciliation Refund completion rate Refunds successfully received through an approved route ÷ valid refund requests submitted × 100 Do not count: * Refund request created * Provider ticket opened * Internal approval granted * Outbound instruction submitted until customer receipt is established. Disputes Domestic dispute processes may differ significantly from international card chargebacks. The merchant should determine: * Which institution receives the complaint * Whether funds can be reversed * Evidence requirements

* response deadlines * consumer rights * merchant liability * account-freeze risk * reconciliation Settlement and treasury Settlement is likely to determine feasibility more than checkout design. Trace the flow of funds The merchant should document: 1. Customer account 2. Issuing institution 3. Domestic payment system 4. PSP or gateway 5. Acquirer 6. Settlement bank 7. Currency conversion 8. Cross-border bank 9. Merchant bank 10. Final usable funds For each link record: * Legal name * Ownership * Jurisdiction * Sanctions status * Currency * Role * Contract * Account * timing * failure procedure Treasury metrics Usable settlement rate Approved funds reaching a usable merchant account ÷ completed customer-payment value × 100 Settlement delay Elapsed time from confirmed customer payment to merchant access to usable funds Conversion loss Difference between the approved reference value and usable payout value ÷ approved reference value × 100 Frozen-fund exposure Funds unavailable because of compliance, designation, reserve, provider, or banking restrictions Concentration exposure Track the percentage of funds dependent on: * One bank * One provider * One currency route * One intermediary * One legal structure Regulation, tax, invoicing, and data Iran’s domestic legal requirements must be reviewed alongside the merchant’s home-jurisdiction obligations. Potential subjects include: * Payment licensing * Local entity * ecommerce authorization * merchant registration * consumer protection * electronic contracts * tax * invoicing * withholding

* data protection * cybersecurity * content restrictions * foreign ownership * currency controls * reporting * refunds * marketplace duties A domestic license does not override foreign sanctions or export controls. A foreign sanctions license does not eliminate Iranian local-law obligations. This article provides general information and does not constitute legal, sanctions, export-control, regulatory, tax, banking, privacy, or accounting advice. Merchants should obtain written advice from qualified specialists in every relevant jurisdiction. Fraud, financial crime, and sanctions risk Fraud and sanctions compliance must remain separate controls. A transaction can be: * Low fraud risk but legally prohibited * High fraud risk but not sanctions-related * Sanctions-cleared but operationally suspicious * Technically valid but linked to an unacceptable intermediary Relevant behavioral risks can include: * Account takeover * Identity fraud * stolen domestic cards * fake payment confirmation * refund abuse * marketplace seller fraud * disguised beneficiaries * false invoicing * transaction splitting * third-country rerouting * end-use misrepresentation * sanctions evasion * money laundering Required controls Depending on the legally approved model: * Customer due diligence * beneficial-owner screening * institution screening * transaction monitoring * device analysis * source-of-funds review * end-use certification * manual escalation * record retention * repeated screening * sanctions-change monitoring

Never rely on a screenshot, customer email, or intermediary statement as final proof of payment or compliance. Provider and operating-model considerations Possible models may include: * Domestic Iranian PSP * Local gateway * Local acquirer * Local distributor * Payment facilitator * Merchant of Record * Third-country reseller * Direct bank transfer * Licensed humanitarian or exempt channel None should be treated as permissible by default. Global PSP Most ordinary international PSP relationships may not support Iran-related payments. Verify: * Explicit Iran policy * Merchant jurisdiction * Product * customer type * bank exposure * currency * refund * termination Local PSP A local provider may offer domestic access but create unresolved issues involving: * Contract enforceability * Sanctions * bank ownership * settlement * data * foreign exchange * support * beneficial ownership * merchant eligibility Merchant of Record A Merchant of Record does not neutralize sanctions or export controls. The merchant must understand: * Who sells to the customer * Who owns the customer relationship * Who is screened * Which product is supplied * Who receives funds * Who bears refund liability * Which banks are involved * Whether the model is genuine or a circumvention arrangement Third-country reseller A legitimate reseller may have a substantive commercial role. A shell structure created primarily to disguise the destination, customer, product, or payment route can create severe legal exposure.

No vertical should be recommended without specialist review The brief correctly requires that the guide avoid recommending market entry or priority verticals before legal and provider feasibility is established. Potential domestic demand may exist in areas such as: * Software * Digital media * Gaming * Education * Consumer ecommerce * Professional services * Travel * B2B platforms But each can face distinct restrictions. SaaS and software Review: * Export classification * Encryption * cloud access * software updates * technical support * customer identity * enterprise end use * government affiliation * hosting * subscription collection Gaming and digital media Review: * Content * platform restrictions * software controls * virtual goods * age requirements * domestic method access * recurring payment * refunds * account location * app-store availability Education Certain educational, communications, or humanitarian activities may receive different treatment under some sanctions regimes, but scope, conditions, technology, payments, institutions, and licensing must be reviewed precisely. Do not infer that an educational purpose makes every transaction permissible. Travel Travel-related activity may involve: * Airlines * hotels * agencies * transport companies * designated entities * foreign cards * domestic cards * refund requirements * insurance * currency exchange Each counterparty requires screening. Marketplaces Marketplaces multiply exposure because the operator must assess: * Seller * buyer * product * bank * payout

* beneficial owner * prohibited goods * restricted services * refunds * transaction monitoring Merchant-stage recommendations Merchant considering demand Do not begin by building a localized checkout or collecting unnecessary customer data. First: * Obtain sanctions and export-control advice. * Classify the product. * Identify applicable jurisdictions. * Consult the merchant’s bank. * Consult the merchant’s PSP. * Establish explicit no-go criteria. * Determine whether customer research itself creates legal or data issues. Merchant evaluating a proposed provider Require: * Provider legal identity * License * ownership * banks * payment methods * settlement path * currency route * sanctions policy * merchant eligibility * refund process * termination process * written legal basis Independently verify the answer. Merchant with a legally approved use case Run a controlled end-to-end validation covering: * Customer screening * payment initiation * authentication * confirmation * settlement * conversion * payout * refund * reconciliation * sanctions rescreening * provider failure * bank designation * wind-down Merchant already operating Maintain continuous review of: * OFAC actions * EU measures * UK and other applicable sanctions * export controls * bank designations * provider policy * currency availability * product scope * customer ownership * refunds * data * tax * contracts A previously approved flow may cease to be permissible or operational. Iran feasibility scorecard Gate Required proof Failure condition Legal permission

Written multi-jurisdiction sanctions analysis Activity prohibited or unresolved Export controls Product and technology classification License required but unavailable Counterparty screening Customer, owner, bank, provider, and intermediary screening Blocked, controlled, or opaque party Provider access Written production approval for exact merchant and use case Generic coverage only Domestic payment access Confirmed method, acquirer, and merchant eligibility Method exists but merchant cannot access it Settlement Tested flow into approved, usable account Funds trapped, frozen, or nonconvertible Refunds End-to-end customer reimbursement test Refund cannot be reliably delivered Currency Documented amount, unit, rate, and conversion process Rial/toman ambiguity or unusable FX route Data and technology Approved hosting, transfer, and security model Compliance or export-control gap Tax and invoicing Specialist-reviewed requirements Unresolved registration or reporting Operations Named compliance, treasury, payments, and support owners No durable operating capacity Change management Immediate suspension and wind-down process Merchant cannot react to new restrictions A failure at one mandatory gate should stop the project regardless of estimated demand. Iran-specific checklist * Identify every jurisdiction connected to the proposed transaction. * Obtain current Iran-specific sanctions advice. * Classify the product, software, technology, and support services.

* Determine whether a license, exemption, or authorization is required. * Screen the customer, owners, end users, banks, providers, and intermediaries. * Confirm end use and ultimate beneficiary. * Reject structures designed to obscure Iran-related activity. * Obtain the merchant bank’s written position. * Obtain the PSP’s written position. * Identify every domestic and cross-border institution in the flow. * Confirm whether the merchant can legally access domestic cards or gateways. * Do not assume Visa, Mastercard, or ordinary international-wallet acceptance. * Define whether amounts are expressed in rial or toman. * Document the exchange-rate source and purpose. * Confirm domestic settlement. * Confirm lawful currency conversion. * Confirm cross-border payout into an approved account. * Calculate usable settlement rather than domestic payment completion alone. * Test a full refund to the original customer. * Test failed-payment and failed-refund handling. * Review domestic tax, invoice, ecommerce, and consumer rules. * Review data, hosting, encryption, and transfer obligations. * Build transaction and counterparty rescreening. * Establish immediate suspension criteria. * Build customer communication and wind-down procedures. * Assign legal, sanctions, export-control, payments, treasury, finance, data, security, and support owners. * Reverify all assumptions immediately before launch and continuously afterward. Payment-performance measurement

Performance measurement is relevant only after the flow has passed every feasibility gate. Legally eligible transaction rate Transactions passing all required legal and counterparty checks ÷ transactions submitted for eligibility review × 100 This is not a commercial approval metric. It measures the share legally eligible to proceed. Payment completion rate Completed domestic payments ÷ valid eligible payment attempts initiated × 100 Usable settlement rate Funds reaching an approved, usable merchant account ÷ completed domestic payment value × 100 Refund completion rate Refunds received by customers through an approved route ÷ valid refund requests initiated × 100 Compliance-exception rate Transactions requiring manual legal or compliance review ÷ transactions screened × 100 Settlement delay Time from completed domestic payment to merchant access to usable funds Frozen-fund rate Funds inaccessible because of compliance, banking, provider, reserve, or designation issues ÷ completed payment value × 100 Cost per usable completed order All payment, compliance, screening, provider, FX, settlement, refund, and operating costs ÷ orders whose proceeds reached an approved, usable merchant account A low domestic processing fee has little value if the settlement route fails. Final merchant recommendation Iran should not be prioritized through an ordinary market-sizing or payment-method-selection process.

The country has a large population, substantial domestic account ownership, widespread digital-payment behavior, and established internal card and banking infrastructure. Those facts describe real domestic commerce. They do not establish that an international merchant can lawfully supply the product, access the payment system, receive the funds, convert the currency, refund the customer, or continue operating after a regulatory change. No merchant vertical should receive a general entry recommendation from this guide. A merchant should proceed only when it has independently established that: 1. The product, service, software, support, and technology transfer are permitted. 2. The customer, owner, end user, provider, bank, and intermediary are acceptable. 3. A provider has approved the exact merchant, product, entity, and transaction. 4. Domestic customers can use the proposed method. 5. Funds can settle into an approved and usable merchant account. 6. Currency conversion and payout are lawful and operational. 7. Refunds can be delivered reliably. 8. Data, tax, invoicing, and consumer obligations can be met. 9. The merchant can suspend or unwind the operation immediately if conditions change. Until those conditions are documented, Iran is not a checkout-localization opportunity. It is a legal, institutional, and financial-access problem whose payment feasibility remains unproven.

The uploaded brief positions Iran as a legal-and-infrastructure feasibility question before it becomes a commercial payment market. Domestic consumers may use cards, transfers, mobile banking, and online commerce extensively, but those capabilities operate within a financial system that is substantially isolated from ordinary international card networks, banking relationships, PSP coverage, and cross-border settlement. Editorial interpretation Country-specific anchor: Strong domestic digital-payment activity does not establish accessibility for an international merchant. Editorial position: Legal permission, export-control classification, counterparty screening, provider approval, payment access, currency conversion, and usable settlement must be established before demand or checkout optimization is analyzed. Assumption being challenged: A large population with established ecommerce and electronic banking can be addressed through the same international PSP and card infrastructure used in neighboring markets. Merchant decision supported: Determine whether a proposed Iran-related activity and payment flow is lawful, contractually available, technically possible, financially usable, and operationally sustainable. Selected format: A feasibility-gate structure beginning with legal access.

Critical publication note: Iran-related sanctions, export controls, designations, licenses, and financial restrictions change frequently. Every legal, banking, provider, network, currency, and settlement statement in this guide requires review immediately before publication and before any merchant action.

Editorial recommendations package SEO title options 1. Payments in Iran: Access, Sanctions, and Feasibility 2. Iran Payment Methods and Merchant Restrictions 3. Accepting Payments in Iran: A Feasibility Guide 4. Iran Payments: Domestic Systems and International Limits 5. Payment Processing in Iran: What Merchants Must Verify Recommended SEO title Payments in Iran: Access, Sanctions, and Constraints Recommended H1 Payments in Iran: Market Scale Under Severe International Payment Constraints Meta description Understand Iran’s domestic payment systems, international network restrictions, sanctions, currency, settlement, refunds, provider access, and merchant feasibility. URL slug /payments-in-iran/ Primary keyword payments in Iran Secondary keywords * Iran payment methods * payment processing Iran * accept payments in Iran * Iranian card payments * Shetab payment system * Shaparak payment network * Iran payment sanctions * Iran ecommerce payments * Iranian rial payments * cross-border payments Iran * Iran merchant payment access * Iran payment gateway Related entities Iran, Iranian rial, toman, Central Bank of Iran, Shetab, Shaparak, OFAC, EU sanctions, SWIFT, correspondent banking, domestic cards, foreign exchange, export controls, ecommerce and digital payments. Search intent High-risk legal, financial, technical, and operational feasibility research for merchants assessing whether an Iran-related payment flow is permissible and accessible. Article excerpt

Iran has widespread domestic digital-payment use, but its payment infrastructure is substantially isolated from ordinary international networks. Merchants must establish legal permission, provider access, currency conversion, usable settlement, and refund feasibility before evaluating commercial demand. Social description Iran’s domestic payment system is digitally mature—but that does not make it accessible to international merchants. Legal access, provider approval and usable settlement come first. Internal-link recommendations * What to evaluate before entering a new market * How to select a PSP for international expansion * International payment expansion checklist * Payment infrastructure for global expansion * Global payment gateway versus local PSP * Merchant of Record versus PSP * Settlement and reconciliation for international payments * How payment data quality affects operations * Cross-border payment compliance * Payment-provider due diligence Authoritative external-source recommendations Use and refresh immediately before publication: * OFAC Iran sanctions program, regulations, licenses, FAQs, and recent actions * U.S. Bureau of Industry and Security export-control regulations and guidance * U.S. Consolidated Screening List * Council of the European Union Iran sanctions pages and regulations * UK and other relevant national sanctions authorities * United Nations sanctions materials where applicable * IMF for current macroeconomic projections

* World Bank for population, GDP, account ownership, and digital-payment indicators * SWIFT for sanctions-related network statements * Central Bank of Iran and Shaparak materials where reliable current official access is available * Qualified Iranian payment, banking, tax, and data counsel * Verified provider and bank documentation Structured-data recommendation Use: * Article * BreadcrumbList * FAQPage only if a visible FAQ is later added

Original asset recommendations 1. Iran Market-Entry Feasibility Gates Purpose: Prevent teams from beginning integration or demand analysis before legal and settlement feasibility is established. Intended reader: Executive, legal, compliance, payments, treasury, and expansion teams. Flow: Legal permission → export control → counterparty → provider → domestic method → settlement → currency → refund → data → operations Data required: Current counsel opinions, sanctions status, provider confirmations, bank route, settlement tests, and refund tests. Recommended format: Sequential gated diagram with stop conditions. Placement: Immediately after the introduction. 2. Domestic Payment Use Versus International Merchant Access Purpose: Explain why domestic adoption does not imply foreign accessibility. Left side: * Domestic cards * Shetab * Local gateways * Bank apps * Transfers * Domestic ecommerce Right side: * Sanctions * PSP restrictions * correspondent banking * international-network isolation * FX controls * settlement * refund risk Intended reader: Strategy and product teams. Recommended format: Two-system comparison. Placement: After the country snapshot. 3. Iran Customer Payment to Usable Merchant Funds Purpose: Identify every point at which a completed domestic payment can become legally or financially unusable. Flow: Customer → domestic bank/card → local network → PSP → settlement bank → FX → correspondent bank → merchant account Intended reader: Treasury, finance, compliance, and payment operations.

Data required: Actual institutions, ownership, jurisdictions, currencies, legal basis, and settlement timing. Recommended format: Flow-of-funds diagram with red stop gates. Placement: Settlement section. Visual recommendations Hero image: “A Functioning Domestic System Behind an International Access Wall” Show a highly active domestic payment environment containing: * Cards * Mobile banking * Transfers * Ecommerce * Domestic payment infrastructure Separate it from the international merchant by a series of transparent gates: * Legal permission * Sanctions screening * Provider access * Currency * Settlement * Refunds Central message: Domestic payment maturity does not guarantee international merchant access. Alt text: “Iranian domestic cards, bank apps and ecommerce separated from an international merchant by sanctions, provider, currency, settlement and refund feasibility gates.” Diagram: “Payment Success Is Not Usable Settlement” Flow: Customer paid → domestic provider confirmed → local funds settled → currency conversion attempted → cross-border bank reviewed → merchant received usable funds Mark each stage as: * Unverified * Permitted * Blocked * Completed Caption: “A domestic payment should not count as merchant revenue until funds reach an approved and usable account.” Alt text: “Flow showing the difference between an Iranian customer payment, domestic settlement, currency conversion, cross-border banking and usable merchant funds.” Chart concept

Avoid presenting a standard payment-method market-share chart unless current, verifiable primary data are available. A safer chart would compare World Bank 2024 financial-inclusion indicators: * Account ownership: 86% for women and men * Digital-payment use: 76% for women * Digital-payment use: 81% for men Label the World Bank definition and state that these indicators do not measure international merchant accessibility or ecommerce market share. (Digital Finance) Human review and contribution recommendations Required before publication * Iran sanctions counsel * Export-control counsel * EU sanctions reviewer where relevant * Iranian banking and payments specialist * Treasury and correspondent-banking specialist * Iranian tax and commercial-law reviewer * Data and cybersecurity counsel

Strongly recommended * Financial-crime and sanctions-screening specialist * Foreign-exchange specialist * Settlement and reconciliation specialist * Digital-services export-control specialist * Provider due-diligence reviewer * Crisis and wind-down operations reviewer Optional enhancement Add an approved firsthand observation describing a case where: * Domestic payment capability existed but foreign settlement failed * A provider declined the merchant despite technical capability * A bank designation interrupted an otherwise functioning route * Refunds became impossible after a provider or bank change * Rial/toman ambiguity caused an integration or accounting risk * A software or service classification changed the legal analysis Do not identify a merchant, provider, bank, or transaction without approval. Final fact-check list Verify immediately before publication: * Iran’s latest population * Nominal GDP and global rank * GDP-per-capita methodology * Inflation and growth forecasts * Current U.S. sanctions authorities * Current OFAC general licenses and exemptions * Current EU sanctions and snapback measures * UK and other applicable sanctions * Export-control treatment by product * Current designated Iranian banks * Current SWIFT availability by institution * Shetab structure and membership * Shaparak structure, PSP rules, and transaction statistics * Domestic card and online-payment adoption * International-card availability * Wallet availability * Domestic gateway eligibility

* Iranian entity and bank-account requirements * Rial and toman implementation * Current currency controls and exchange-rate regimes * FX conversion availability * Repatriation * Cross-border payout * Refund support * Recurring-payment support * Domestic ecommerce and data rules * Tax, invoicing, and reporting

* Whether publication requires additional legal, compliance, security, or reputational approval