Download websites that use Iamport

About Iamport

The product name and the company name do not match here, and the gap is the first useful thing in the record. We detect the integration as Iamport while the vendor behind it is recorded as Portone. When a payments company rebrands, the script embedded in a live checkout does not rebrand with it, because touching a working payment path is a project nobody schedules without a reason.

So what this page counts is the merchants still shipping the original integration. A payment fingerprint is a strong commercial signal in any case. A domain carrying one takes money, that money moves through a named processor or aggregator, and somebody made an integration decision a developer had to implement. Iamport dates to 2014 and is distributed as JavaScript under a Proprietary licence, so the surface we key on is client side code loaded into a checkout flow.

Version detail sharpens the picture. We record 5 distinct version strings for the product, and 1.1.8 recurs across the sites we see. Checkout code tends to be pinned and then left alone, so the spread of versions works as a rough proxy for when each merchant last touched their payment layer. Merchants on old pinned builds are the ones exposed when an endpoint is deprecated, and they are also the ones a competing provider can approach with a migration argument rather than a price argument.

The audiences follow from that. Competing gateways and aggregators want merchants whose integration is old enough to be worth replacing. Acquirers and banks want to see which processors sit in front of which merchant populations. Fraud and compliance researchers want the same map for a different reason, since the checkout stack a merchant runs shapes what its transaction traffic looks like.

On geography we can say less than we would like. The vendor publishes from a Korean country domain, which supports a regional reading of the product, but our record carries no country or domain suffix breakdown for the merchant sites themselves, so nothing in the file tells you where those businesses are registered or who their shoppers are. Anyone who needs that has to join our list against their own data.

Payment scripts also load at checkout rather than on a home page, and a merchant can sit behind a wrapper that hides the underlying processor entirely, so the count is a floor and not a census. As of October 2026 we detect Iamport on 143 sites. Confirming one merchant is a lookup anyone can run. Assembling the population of merchants on an aging payment integration, which is what a competing provider, a risk team or a market analyst actually needs, requires the whole list.