Online Payment Gateways

An online payment gateway connects a merchant's digital checkout with payment services. SEP describes its gateway as supporting websites, mobile applications, and organizational systems, with acceptance of cards belonging to Shetab, Iran's interbank card network. That documented scope concerns domestic network membership; it does not establish acceptance of foreign-issued cards. s1

SEP distinguishes a direct gateway supplied by a PSP from an offering supplied through a payment facilitator, which obtains payment infrastructure from PSPs. The distinction concerns the service arrangement behind checkout. A facilitator's interface and the underlying payment-service infrastructure should therefore be examined separately. SEP's commercial comparisons of speed and security are provider claims, not independently verified comparisons. s1

[s1]

Integration involves more than placing a payment button on a website. ZarinPal's official sample-code directory identifies payment creation, verification, transaction-status inquiry, and management of verified and unverified transactions as distinct capabilities. It provides examples for PHP, Node.js, Python, and Android, and identifies registration and a merchant identifier as prerequisites. The directory establishes the available integration topics without, by itself, defining every endpoint or response condition. s2

These distinctions are useful editorial safeguards. A customer returning to a shop, a provider recording a payment, and the merchant verifying a transaction are different events to investigate. The existence of separate verification and inquiry functions makes it inappropriate to describe checkout as a single undifferentiated success step. Exact behavior must be checked against the documentation for the particular integration. s2

[s2]

A payment company's API documentation may also describe administrative functions. ZarinPal's API introduction documents an authenticated account interface using OAuth 2.0 and GraphQL. OAuth provides the access-token mechanism described by the documentation; GraphQL lets clients request specified fields through structured queries. The introduction lists functions such as creating support tickets, handling documents and profile details, and creating gateways. s3

This account interface should be read according to its stated purpose. Its authentication model does not establish the protocol used by every payment-acceptance endpoint. Developers and researchers need to distinguish merchant administration, payment initiation, transaction verification, and later reporting instead of assuming that one API introduction covers the entire lifecycle. s3

[s3]

SEP's gateway page describes merchant onboarding through business and identity information, website review, supporting documents, and contracting. It also describes transaction reporting after activation. These are the provider's published conditions and service descriptions; the undated page is not sufficient evidence that every listed requirement applied unchanged at the editorial cutoff. s1

The practical subject is therefore broader than checkout design. A researched gateway profile needs to establish who provides the service, what the integration verifies, how records are accessed, and which onboarding conditions apply to the relevant period. This account leaves current fees, settlement schedules, and comparative reliability unresolved.

[s1]