Redirect payment
(Card payment online)
When making a payment, the customer is transferred to the bank's or payment provider's secure payment page, where they enter their card details, and then return to the web store after payment.
Who is it recommended for?
- For startups, small and medium-sized enterprises (SMEs): If a company does not have a dedicated development team or a huge budget to build an online payment system, redirect payment is the best choice. For most ready-made webshop engines (e.g. Shoprenter, UNAS, WooCommerce, Shopify), there are pre-made, “plug-and-play” modules that can be deployed in a few clicks.
- For those who want to minimize security risks (and paperwork) Since the customer does not enter their card details on the webshop interface, but on the bank or payment service provider’s website, the card details never touch the merchant’s own server. The huge advantage of this is that the merchant does not have to comply with extremely strict and expensive international data security standards (PCI-DSS compliance), as the service provider takes on this responsibility entirely.
- For new or even less well-known webshops (Trust building): If a customer visits a smaller webshop for the first time, they are understandably cautious about entering their bank card details. However, if they are transferred to a well-known and trusted interface (for example, the website of a large domestic bank or a well-known international brand) during payment, this drastically increases their sense of security and reduces the number of cart abandonments before payment.
- For cost-sensitive projects: The development and ongoing security maintenance of unique (embedded in the page, so-called in-context or API-based) payment solutions costs significant amounts. Implementing and maintaining the redirect version is a penny in comparison.
