APIs · head to head
i2c vs Percy

i2c
APIs
Configurable card issuing and banking processing platform for banks and programme managers
- From
- On request
- Free plan
- No

Percy
Testing
Visual regression testing owned by BrowserStack, with a permanent free tier for low screenshot volume
- From
- Free
- Free plan
- Yes
The short version
- Percy is free; i2c prices on request.
- Only i2c lists configurable product engine; only Percy lists screenshot diffing.
- Where Percy falls short: paid tier pricing above the free tier is not transparently published as a fixed number, requiring a quote to know actual cost at scale.
- Prices and features on this page were last checked on 20 November 2026.
How do i2c and Percy differ?
i2c and Percy differ on starting price (On request against Free), pricing model and free tier (No against Yes). Only the attributes on which i2c and Percy actually diverge.
Which features does each one have?
They share no listed features; 6 appear only for i2c and 6 only for Percy. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in i2c
- Configurable product engine
- Credit and instalments
- Multi-currency
- Fraud and risk tooling
- Digital banking front ends
- Global scheme connectivity
Only in Percy
- Screenshot diffing
- Framework integrations
- Responsive and cross-browser snapshots
- Review workflow
- Build history
- BrowserStack platform integration
What is each one used for?
The jobs each tool is most often brought in to do.
i2c
- A bank wanting credit, debit and prepaid portfolios on one processor rather than threenot Percy
- An issuer in a market where local scheme and currency support rules out US-centric processorsnot Percy
- A programme manager launching instalment products without building a lending corenot Percy
- A credit union replacing an ageing processor without writing custom code for product rulesnot Percy
Percy
- A team already on BrowserStack for device testing that wants to add visual regression without a separate vendor relationshipnot i2c
- A low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anythingnot i2c
- A team wanting a lower cost per screenshot than Applitools and willing to tolerate more manual false-positive triagenot i2c
- A Cypress or Playwright test suite adding visual checks without changing its existing test runnernot i2c
Where do i2c and Percy fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
i2c
- Developer experience lags API-native competitors, and teams expecting Stripe-grade documentation and sandboxes find an enterprise integration project instead
- Implementations lean on i2c or partner professional services, so timelines and costs are set by a services queue rather than by your own engineering speed
- Pricing is per active card and per transaction with monthly minimums, none of it published, so comparing bids requires modelling your own portfolio carefully
- Configuration flexibility means product behaviour lives in platform settings rather than in your repository, which complicates version control, testing and audit trails
- As a private company with a broad global footprint, regional support depth is uneven, and a programme in a smaller market may get thinner service than a flagship account
Percy
- Pixel-based diffing generates more false positives from font rendering and anti-aliasing noise than Applitools' AI-based comparison, which trains some teams to start ignoring diff alerts over time
- It is billed separately from core BrowserStack device testing, and stacking Percy with other BrowserStack modules such as Accessibility Testing materially increases total contract value beyond the headline device testing price
- Paid tier pricing above the free tier is not transparently published as a fixed number, requiring a quote to know actual cost at scale
- The free tier's 5,000-screenshot cap is easy to exceed for any team running visual tests across multiple browsers and viewports on every commit, pushing many active projects into a paid tier faster than the free number suggests
- As part of a larger acquired portfolio, Percy's roadmap priority within BrowserStack's broader product strategy is less certain than it would be as a standalone company's sole focus
How much do i2c and Percy cost?
i2c is priced on request; Percy is free to use. Plan by plan below, from each vendor's own pricing page.
i2c
On request- i2c processing platformOn request
- Per-active-card and per-transaction processing fees
- Minimum monthly commitments by programme
- Implementation and configuration professional services
Percy
Free- FreeFree
- 5,000 screenshots a month
- Unlimited users and projects
- 30-day build history
- PercyOn request
- Priced by screenshot volume above the free tier
- Sold separately from core BrowserStack device testing plans
- Get a current quote before assuming bundled pricing with other BrowserStack products
Which should you pick?
Choose i2c if
- You need configurable product engine.
- You work on Web, API.
- You also want credit and instalments.
Choose Percy if
- You need screenshot diffing.
- You want to start without paying.
- You also want framework integrations.
Questions people ask
- Is i2c or Percy better?
- Neither clearly leads. i2c starts at On request and Percy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, i2c or Percy?
- Percy has a free tier; the other does not. Paid plans start at On request for i2c and Free for Percy.
- Does i2c or Percy run on more platforms?
- i2c runs on Web, API. Percy runs on Web.
- Can I use Percy for free?
- Yes. Percy has a free tier, so you can try it without paying. i2c starts at On request.
- What is i2c best used for?
- i2c is most often used for a bank wanting credit, debit and prepaid portfolios on one processor rather than three, an issuer in a market where local scheme and currency support rules out us-centric processors, a programme manager launching instalment products without building a lending core, a credit union replacing an ageing processor without writing custom code for product rules. Of those, a bank wanting credit, debit and prepaid portfolios on one processor rather than three and an issuer in a market where local scheme and currency support rules out us-centric processors are not what Percy is typically brought in for.
- What can i2c do that Percy cannot?
- i2c covers Configurable product engine, Credit and instalments, Multi-currency, Fraud and risk tooling. Percy covers Screenshot diffing, Framework integrations, Responsive and cross-browser snapshots, Review workflow.
Answered from the vendors’ own pages
i2c: Does i2c issue the cards itself?
No. It processes; issuance sits with a bank or licensed issuer, and in most markets you need that relationship separately.
Percy: Is Percy free?
Yes for up to 5,000 screenshots a month with unlimited users and projects; beyond that it is a paid, quote-priced module.
i2c: Can it handle revolving credit?
Yes. Credit, instalments and buy-now-pay-later sit on the same platform as debit and prepaid, which is unusual among modern processors.
Percy: Is Percy included if I already pay for BrowserStack device testing?
No, it is billed separately by screenshot volume, not bundled into core device testing plans.
i2c: Is it self-serve?
No. Expect a configuration-led implementation with professional services rather than signing up and calling an API.
Percy: How does it compare to Applitools?
Percy uses pixel-based diffing, which is generally cheaper per screenshot but produces more false positives than Applitools' AI-based perceptual comparison.
Related pages
Other head to heads
- i2c vs Marqeta
- i2c vs Paymentology
- i2c vs Enfuce
- i2c vs Episode Six
- i2c vs Tribe Payments
- i2c vs Thredd
- i2c vs Mambu
- i2c vs Highnote
- i2c vs Lithic
- i2c vs Skaleet
- i2c vs 10x Banking
- i2c vs Temenos Transact
- i2c vs Moov
- i2c vs Portkey
- i2c vs Q2 Digital Banking
- i2c vs Svix
- i2c vs Swagger/OpenAPI
- i2c vs Synctera
- i2c vs Applitools
- i2c vs Sauce Labs
- i2c vs BrowserStack
- i2c vs Playwright
- i2c vs Cypress
- i2c vs TestRail
- i2c vs Katalon
- i2c vs PractiTest
- i2c vs Jest
- i2c vs Xray Test Management
- i2c vs JUnit
- i2c vs Puppeteer
- i2c vs Kameleoon
- i2c vs Qase
- i2c vs Robot Framework
- i2c vs Zephyr Scale
- i2c vs Ranorex
- i2c vs Appium
- Percy vs Marqeta
- Percy vs Paymentology
- Percy vs Enfuce
- Percy vs Episode Six
- Percy vs Tribe Payments
- Percy vs Thredd
- Percy vs Mambu
- Percy vs Highnote
- Percy vs Lithic
- Percy vs Skaleet
- Percy vs 10x Banking
- Percy vs Temenos Transact
- Percy vs Moov
- Percy vs Portkey
- Percy vs Q2 Digital Banking
- Percy vs Svix
- Percy vs Swagger/OpenAPI
- Percy vs Synctera
- Percy vs Applitools
- Percy vs Sauce Labs
- Percy vs BrowserStack
- Percy vs Playwright
- Percy vs Cypress
- Percy vs TestRail
- Percy vs Katalon
- Percy vs PractiTest
- Percy vs Jest
- Percy vs Xray Test Management
- Percy vs JUnit
- Percy vs Puppeteer
- Percy vs Kameleoon
- Percy vs Qase
- Percy vs Robot Framework
- Percy vs Zephyr Scale
- Percy vs Ranorex
- Percy vs Appium
