Start with your company and customers, not a comparison table of headline rates. A provider must accept your business, support the countries and currencies you need, and fit the way your shop handles orders and refunds.
Compare the complete offer
Ask for written pricing for setup, monthly service, fixed and percentage transaction fees, refunds, chargebacks, international cards, currency conversion, payouts and any minimum turnover. Check when funds settle, how disputes are handled and what documents the provider needs before activation. For Cyprus, verify which entity and settlement account are supported; do not assume country coverage from a logo on a website.
Then test the checkout on a phone. A hosted payment page can reduce how much card data touches your own site, while an embedded flow may feel more integrated. Either way, explain accepted methods, currency, shipping, returns and the next step before the customer pays.
Keep card data out of your own systems
The PCI Security Standards Council explains that PCI DSS applies to entities that store, process or transmit card data, including merchants and service providers. Its small merchant guide shows common payment flows and why a third-party payment page does not automatically make every merchant eligible for the same assessment. Confirm the exact requirements with your acquirer or qualified assessor; never store card numbers in order notes or email.
JupiWeb’s published e-shop scope starts at €890 and can include card, IRIS and cash-on-delivery options, but provider charges are separate. Estimate how a fee changes contribution per sale with the break-even ROAS calculator, then use actual provider terms in the calculation.