Electronic Payments

An electronic payment can involve several systems, and their names do not describe interchangeable services. The World Bank’s March 2016 account of Iran’s financial infrastructure identified Shaparak with electronic card payments and settlement, PAYA with automated clearing for smaller transfers, and SATNA with real-time gross settlement for larger transfers. Real-time gross settlement means settling transfers individually rather than only calculating a net position across a batch. The report also described Shetab as an interbank information-transfer network. These descriptions provide historical orientation, rather than evidence of present transaction limits or operating schedules. s1

This distinction matters when reading about payment technology. A merchant checkout, a bank-transfer instruction, and an interbank settlement function can all be electronic while performing different jobs. Current service conditions require newer operational documentation than this historical overview. s1

[s1]

The pages in this section approach payments from different directions. Payment service providers concern the organizations delivering payment services; payment facilitators concern intermediaries serving merchants. Online gateways concern the checkout interface and integration. Point-of-sale manufacturers concern physical acceptance equipment. Payment-switch infrastructure concerns the systems connecting participants, while transaction-management systems concern the records and operational handling surrounding payments.

For the facilitator branch, TechRasa Insight describes Iranian payment facilitators as intermediaries between merchants and payment service providers. Its report is industry research with disclosed participation and sponsorship, rather than the regulator’s definitive register or rulebook. s2

[s2]

ZarinPal’s gateway introduction describes a web-service integration for purchases using cards belonging to the Shetab network. It distinguishes the merchant selling the product or service from the cardholding buyer and identifies separate references used for payment requests and completed purchases. This is documentation of one provider’s interface, not a universal specification for every Iranian gateway. s3

The same provider’s verification documentation explains that a payment must receive confirmation from the payment service provider. Depending on configuration, verification can be automatic or initiated by the merchant. A browser’s return to a shop therefore should not be read as a complete account of the payment’s processing state. The documentation also describes reversal when required verification is not completed within the permitted interval. s4

[s3] [s4]

A useful account of this sector needs both technical descriptions and comparable statistics. This draft does not report national transaction totals, provider rankings, or growth rates because the underlying official annual tables were not inspected. Monthly observations and provider publicity would not, by themselves, establish a consistent annual series.

Currency labels also require care. ZarinPal documents separate API values for rial and toman amounts. That example illustrates why an amount without its denomination is incomplete information; this page makes no currency conversion. s5

The practical reading sequence is to identify the payment function, establish which participant supplies it, and then examine the evidence for verification and settlement. This keeps the visible checkout experience connected to the underlying operational questions without assuming that one provider’s interface describes the whole market.

[s5]