Direct API payment integration
(Card payment online)
The webshop collects card details on its own payment form and sends them directly to the payment provider through a technical API connection; this requires more development work and greater security responsibility.
Who is it recommended for?
- For high-traffic, premium web stores (Where conversion is king) When a web store is already processing thousands or tens of thousands of transactions per month, every thousandth of an improvement in the cart abandonment rate means serious millions.
- For subscription and SaaS businesses: If the business provides a monthly fee service (e.g. software, streaming, membership systems, regular product box delivery), API integration is practically unavoidable.
- For companies with their own mobile application (In-App payment): If a company develops its own iOS or Android application (e.g. food delivery app, taxi/car sharing, ticket sales), redirect payment would provide a terrible user experience by opening an external mobile browser.
- For Marketplaces and Complex Platforms: If you run a site where multiple sellers offer their products (like Emag or Etsy), the API integration allows for intelligent splitting of funds (Split Payment). The buyer pays once, but the API transfers part of the money to the main site for commission, and the rest directly to the seller.