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
- 10
- Available on
- All plans
Cardflo provides robust payment processing for PrestaShop merchants. Integrate directly with our platform to manage transactions, optimise payment flows, and reduce declines.
Our solution supports various payment methods and offers advanced fraud prevention tools tailored for PrestaShop environments.
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
PrestaShop merchants manage transaction processing through dedicated payment modules that connect the e-commerce store to an external gateway or acquirer. These integrations handle the critical handshake between the shopping cart and the payment processor, ensuring that customer card data or alternative payment method instructions are securely transmitted for authorisation.
A typical integration facilitates real-time communication between the PrestaShop environment and the payments stack, allowing for the execution of SCA-compliant authentications via 3DS2. By implementing a robust plugin, merchants can manage complex tasks such as partial refunds, transaction captures, and multi-currency settlement directly from the back-office console.
The architecture often includes tokenisation to support recurring billing and merchant-initiated transactions, while also managing the technical requirements of different Merchant Category Codes. High-volume businesses often utilise these integrations to consolidate their payment data and improve reconciliation processes across diverse geographic regions.
How prestaShop payments works
Module configuration and installation
The merchant installs the payment module within the PrestaShop administration panel, entering API credentials provided by the PSP. This link establishes a secure channel for data transmission, ensuring that the checkout page can communicate with the gateway to request authorisations and receive status updates regarding payment success or failure.
Authorisation and SCA triggering
When a customer initiates a purchase, the module prepares an authorisation request. If the transaction falls under PSD2 mandates, the system triggers the 3D Secure protocol. The issuer examines the merchant's risk profile and the customer's credentials before granting an authorisation code or issuing a soft decline.
Transaction capture and settlement
After successful authorisation, the merchant can configure the module to capture funds immediately or at a later stage, such as upon shipping. The acquirer processes the capture request, and the funds move into the settlement cycle, eventually deposited into the merchant account after deducting interchange and scheme fees.
Post-purchase management
The integration remains active for the entire transaction lifecycle. Within the PrestaShop order management interface, the merchant can trigger full or partial refunds and retrieval responses. Performance data is synchronised, allowing the store owner to monitor decline reasons and dispute statuses without leaving their primary e-commerce dashboard.
Why prestaShop payments matters
Conversion and Decline Optimisation
Transaction failures often occur due to rigid authentication rules or misaligned MCC configurations. A sophisticated PrestaShop integration allows for the use of smart routing and network tokens, which may help mitigate hard declines and increase the probability of successful authorisations. By managing 3DS2 exemptions and utilising account updaters, merchants can potentially reduce checkout friction while maintaining compliance with regional security mandates.
PrestaShop checkout failover routing
Managing separate consoles for payments and order fulfilment creates administrative overhead and data silos. Integrating the payments stack directly into PrestaShop allows for manual and automated synchronisation of transaction IDs, ARN numbers, and settlement statuses. This visibility is essential for precise KYB and AML reporting, as well as for managing rolling reserves and monitoring the impact of interchange-plus pricing on profit margins.
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 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 support for PrestaShop versions 1.7 through the latest stable releases.
- Integrated 3DS2 framework to manage SCA compliance and liability shift.
- Support for multi-currency processing and local settlement to reduce FX spreads.
- PCI DSS compliant tokenisation for secure storage of customer payment credentials.
- Management of full and partial refunds directly from the PrestaShop order dashboard.
- Configurable capture delays to align with inventory management and shipping workflows.
- Detailed decline reason code visibility for better analysis of transaction failures.
- Automated dunning and account updater support for recurring billing scenarios.
- Capability to route transactions across different MIDs based on risk or region.
- Support for major card schemes alongside regional alternative payment methods.
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 I use multiple acquirers with a single PrestaShop payment module?
While standard modules often link to one provider, advanced payment orchestration integrations allow for smart routing across several acquirers.
This helps manage risk by distributing volume and provides a fallback mechanism if one acquirer declines a transaction due to their internal risk parameters or MCC restrictions. This setup requires the gateway to support multi-MID configurations, which are then governed by the module's logic.
What is the difference between immediate capture and authorised-only transactions?
An immediate capture clears the transaction as soon as the authorisation is granted, initiating the settlement process. An 'authorised-only' transaction places a hold on the customer's funds for a specific period without transferring them.
This is useful for merchants who need to verify stock before finalizing a sale. The PrestaShop module allows merchants to manually trigger the capture after the initial authorisation has been confirmed.
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.
Is it possible to manage chargebacks and disputes within the PrestaShop admin?
Many professional-grade modules provide a data sync that displays retrieval requests and chargeback notifications within the order detail view.
While the actual representment process might still require documentation to be uploaded via the gateway portal, having the status reflected in PrestaShop helps merchants stop fulfilment on disputed orders and adjust their reserve calculations accordingly in real time.
Will this integration store sensitive cardholder data on my PrestaShop server?
No, a secure integration utilises either hosted fields or a redirect to the gateway's environment. This ensures that sensitive Primary Account Numbers (PANs) never touch the merchant's server, which significantly simplifies PCI DSS compliance requirements.
Instead, the server only handles secure tokens and transaction references, reducing the merchant's risk surface while still allowing for a customised checkout experience.
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.