PrestaShop payments
PrestaShop merchants and technical agencies use Cardflo to connect storefronts with a global acquirer partner network. By installing our official PrestaShop payment module, operators can configure multi-acquirer routing rules, orchestrate cross-border transactions and process alternative methods natively at checkout.
- Category
- Plugins
- Capabilities
- 6
- Available on
- All plans
E-commerce deployments relying on single gateways often experience checkout latency and higher decline rates during international traffic spikes. Technical agencies building PrestaShop environments require granular control over transaction flows, native hook integrations and compatibility with one page checkout architectures to maintain high conversion rates across multiple currencies.
Cardflo provides a comprehensive PrestaShop payment module that orchestrates transactions across an international network of acquirer partners. Merchants can map multi-acquirer routing rules directly within the PrestaShop back office, ensuring that domestic and cross-border volume flows automatically to the most suitable acquiring partner based on bin, currency and value.
Our solution connects PrestaShop merchants to over 50 acquirer partners, deploying automated smart routing to recover declined transactions. This significantly reduces merchant chargeback rates and enhances overall payment processing efficiency.
PrestaShop payments overview
Managing cross-border volume within a self-hosted e-commerce environment demands precise control over the checkout architecture and back office transaction data. The Cardflo PrestaShop payment module installs directly into the framework, enabling technical teams to configure native checkout routing and multi-acquirer logic without modifying core files.
Merchants can build specific rules for card networks, alternative payment methods and 3DS2 exemptions, orchestrating traffic to regulated acquirer partners based on regional performance metrics. This setup is specifically engineered for the PrestaShop hook system and one page checkout flows.
Developers looking to implement similar logic for other frameworks should consult the OpenCart payments documentation or the Shopware payment plugin guide. By centralising acquiring connections into a single PrestaShop installation, finance teams can reconcile multi-currency settlements and manage refunds from one unified dashboard.
How prestaShop payments works
Module deployment process
Technical administrators upload the Cardflo package directly via the standard PrestaShop back office module manager. Once activated, the extension connects to the central orchestration API using secure credentials. Developers map the necessary front-end hooks to ensure the gateway renders correctly within native templates or custom one page checkout environments, preparing the system for live transactions.
Checkout routing configuration
Merchants establish logic within the PrestaShop back office to handle transaction distribution across multiple acquirer partners. Finance teams can dictate volume caps, currency specific pathways and bin routing rules without writing custom PHP code. The integration reads the incoming cart data, assesses the geographical origin and routes the payment attempt to the optimal acquiring destination.
Transaction synchronisation
Following a successful authorisation through the acquirer network, Cardflo transmits an immediate callback to the PrestaShop environment. The order status updates automatically within the database, triggering standard confirmation emails to the customer. Finance personnel can subsequently process partial or full refunds directly from the order page, keeping the PrestaShop ledger and gateway reporting aligned.
Why prestaShop payments matters
Centralised multi acquirer control
Operating a PrestaShop multi acquirer setup typically requires managing several disparate plugins that conflict during checkout. Consolidating these connections into a single orchestration layer eliminates front-end interference. Merchants benefit from unified reconciliation, fewer technical maintenance requirements and consistent payment workflows, all while accessing rates from 0.2% through various acquirer partners.
PrestaShop checkout failover routing
High latency and failed 3DS2 challenges frequently cause drop-offs at the final stage of the buyer journey. Integrating a native PrestaShop checkout routing solution via orchestration ensures that failed attempts cascade automatically to secondary acquirers before the user receives a decline message. This failover logic preserves conversions during network outages.
Regulatory notes for prestaShop payments
Isolating card data from PrestaShop
Managing sensitive card data directly within a self-hosted PrestaShop database imposes severe compliance obligations and extensive auditing requirements on the merchant.
The Cardflo module mitigates this regulatory burden by employing secure iframe elements alongside robust tokenisation protocols, ensuring raw primary account numbers never touch the local e-commerce server infrastructure.
By isolating the initial payment capture phase, e-commerce operators can complete their self-assessment questionnaires with a significantly reduced technical scope.
All sensitive transaction information transmits directly to the central orchestration environment and the respective regulated acquirer partners, keeping the core PrestaShop installation secure and fully compliant.
Strong Customer Authentication and 3DS2
European regulatory frameworks dictate that online e-commerce transactions must undergo stringent authentication procedures to adequately verify the cardholder identity.
The Cardflo integration includes native 3DS2 capabilities, automatically challenging customers through the PrestaShop checkout interface only when explicitly mandated by the issuing bank or specific acquiring scheme rules.
PrestaShop administrators can configure smart exemption logic within the orchestration dashboard to handle low-value purchases or recurring customer orders.
This system transmits targeted exemption flags directly through the acquirer partner network, minimising unnecessary friction for legitimate buyers while securely maintaining compliance with regional liability shift directives.
PrestaShop payments use cases
Back office module commissioning
Technical agencies installing the PrestaShop payment module must align module settings, credentials and environment modes without exposing live card acceptance during commissioning. Cardflo supports installation and sandbox validation, while acquirer partner credentials are configured in the PrestaShop back office before controlled production activation.
One page checkout validation
PrestaShop stores using one page checkout can lose payment state when address, carrier or basket updates refresh checkout hooks. Cardflo validates the module against these events and maintains the payment session, 3DS2 flow and final order confirmation through PrestaShop’s native hook sequence.
PrestaShop subscription box merchants
PrestaShop merchants need authorised, captured, failed and refunded transactions to produce the correct order states before fulfilment begins. Cardflo maps gateway responses and webhooks to the module’s order workflow, helping operations teams prevent premature dispatch, duplicate capture attempts and unmatched refunds.
PrestaShop B2B wholesale merchants
Agencies managing a PrestaShop multistore group may need separate MIDs, currencies and settlement records for each shop while retaining one module deployment. Cardflo applies shop-level routing rules across the acquirer partner network and returns transaction references to the relevant PrestaShop back office context.
PrestaShop payments by the numbers
Merchants moving from legacy modules to those with 3DS2 optimisation and smart routing often observe modest improvements in successful authorisation rates.
Standard industry data suggests that providing local payment methods and a streamlined SCA flow can reduce exit rates at the final payment stage.
Modern API-based integrations typically achieve sub-three-second response times for authorisation requests, depending on the speed of the issuer and acquirer networks.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with PrestaShop payments
- Native PrestaShop hook integration to synchronise order statuses and payment confirmations in the core database.
- Compatibility with popular PrestaShop one page checkout modules to maintain low latency during the payment phase.
- Multi-acquirer routing configuration managed entirely from within the standard PrestaShop back office administration panel.
- Tokenisation support for repeat customers, storing credentials safely through the core gateway framework.
- Granular bin routing logic to direct transactions to acquirer partners with the highest regional approval rates.
- Comprehensive synchronisation of refunds and partial captures triggered directly through the PrestaShop order management interface.
A short scoping call, then a written plan for your MIDs.
Questions about PrestaShop payments
Which PrestaShop hooks does the payment module use during checkout?
The PrestaShop payment module uses native checkout hooks to register available payment methods, render the payment interface and receive order confirmation events. Agencies can verify hook placement in the PrestaShop back office when a theme or one page checkout component changes the standard checkout structure.
Custom modules that override payment hooks may require compatibility testing to ensure the payment option appears once and the completed transaction updates the correct order.
Can administrators map specific currencies to different acquirer partners?
PrestaShop merchants can define granular currency rules directly within the back office configuration interface. When a customer selects a specific currency on the storefront, the routing engine evaluates the cart total and automatically directs the payload to the designated regional acquirer partner.
This configuration bypasses unnecessary foreign exchange conversions and allows the merchant to settle funds locally, mitigating margin erosion on international orders and improving overall authorisation rates for foreign cardholders.
Does the integration support native PrestaShop refund processes?
Financial controllers can initiate both full and partial refunds from within the standard PrestaShop order management view. When a user changes the order status to trigger a refund, the module transmits the corresponding API request to the central orchestration layer.
Cardflo communicates with the relevant acquirer partner to reverse the transaction, and the success response automatically updates the order history, ensuring that the e-commerce database remains perfectly synchronised with the payment gateway ledger.
How are PrestaShop routing rules configured for different storefront orders?
Routing criteria are configured through the Cardflo orchestration layer rather than hard-coded into individual PrestaShop templates. Rules can evaluate supported transaction data such as currency, order value, market or payment method, then direct eligible orders through the appropriate acquirer partner connection.
Technical teams should test each rule against PrestaShop test orders and confirm that the resulting transaction reference, payment status and order record remain aligned.
Related guides.
See how Cardflo compares.
From the blog
A merchant acquirer is a licensed bank that holds your account, takes liability for transactions, and settles funds. The payment processor is the technology layer routing data between the checkout, card networks, and issuing banks. Every card payment requires both components to manage technical encryption and financial liability. They are often separate entities with distinct fee structures.
Read articleA merchant acquirer is a financial institution that processes card transactions and verifies funds. The payment gateway acts as the technological bridge, encrypting sensitive data between the website and the acquirer. Merchants need both components to ensure that electronic payments are accepted, authorised, and settled. Together, they create a seamless and secure payment experience for customers.
Read articleA merchant account is a specialised business account used to accept electronic payments like Apple Pay and Google Pay. It acts as a bridge between the business and the customer bank. Funds are held here for verification and compliance before being transferred to a main bank account. This process ensures that all transactions are secure and reduces the risk of fraud for the merchant and the customer.
Read articleReady to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.