PrestaShop Payment Gateway Integration Setup

PrestaShop Payment Gateway Integration Setup

We integrate payment gateways into PrestaShop stores, connecting Stripe, PayPal, LiqPay, Fondy, CloudPayments, and other providers through the PrestaShop 8.x Payment API. Our team builds the full payment module: initialization controller, webhook callback processing, order status management, and admin configuration interface. Delivery takes two to four working days. We have built PrestaShop payment modules for 15+ e-commerce stores. Our modules comply with provider API requirements and pass security review on first submission.

A payment gateway integration done right handles edge cases that manual testing rarely catches: concurrent order validations, webhook signature verification, idempotent retries, and correct status transitions on successful payment, failure, and refund. Our modules are built for production from day one, not assembled from tutorial code.

What's Included in Our PrestaShop Payment Integration

We deliver the complete payment gateway integration turnkey. The scope covers:

• Custom payment module with all required PrestaShop hooks registered
• Payment initialization controller with cart validation and redirect to provider
• Webhook callback controller with HMAC signature verification
• Order status mapping: Pending, Paid, Failed, Refunded
• Refund processing via actionOrderStatusUpdate hook
• Admin configuration page with API key fields, test mode toggle, and order status selection
• Error handling and logging for debugging production issues
• End-to-end testing covering successful payment, failed payment, and manual refund flows

PrestaShop 8.x Payment Module Structure

modules/mypay/
├── controllers/front/
│   ├── payment.php     # Payment initialization
│   └── callback.php    # Webhook from provider
├── views/templates/front/
│   └── payment_infos.tpl
├── mypay.php           # Main module class
└── logo.png

Main Module Class

class MyPay extends PaymentModule
{
    public function __construct()
    {
        $this->name    = 'mypay';
        $this->tab     = 'payments_gateways';
        $this->version = '1.0.0';
        $this->ps_versions_compliancy = ['min' => '8.0.0', 'max' => _PS_VERSION_];
        parent::__construct();
    }

    public function install(): bool
    {
        return parent::install()
            && $this->registerHook('paymentOptions')
            && $this->registerHook('paymentReturn')
            && $this->registerHook('actionOrderStatusUpdate');
    }

    public function hookPaymentOptions(array $params): array
    {
        $option = new \PrestaShop\PrestaShop\Core\Payment\PaymentOption();
        $option->setCallToActionText($this->trans('Card Payment', [], 'Modules.Mypay.Shop'))
               ->setAction($this->context->link->getModuleLink('mypay', 'payment', [], true));
        return [$option];
    }
}

Payment Initialization and Callback

// Payment controller: validate order, create payment session, redirect
public function postProcess(): void
{
    $cart     = $this->context->cart;
    $total    = (int) round($cart->getOrderTotal(true) * 100);
    $currency = new Currency($cart->id_currency);

    $this->module->validateOrder(
        $cart->id,
        Configuration::get('MYPAY_OS_PENDING'),
        $cart->getOrderTotal(true),
        $this->module->displayName,
        null, [], (int) $currency->id, false,
        (new Customer($cart->id_customer))->secure_key
    );

    $payment = (new MyPayApiClient(
        Configuration::get('MYPAY_API_KEY'),
        Configuration::get('MYPAY_SECRET_KEY')
    ))->createPayment([
        'amount'       => $total,
        'currency'     => $currency->iso_code,
        'order_id'     => Order::getIdByCartId($cart->id),
        'callback_url' => $this->context->link->getModuleLink('mypay', 'callback', [], true),
    ]);

    Tools::redirect($payment['payment_url']);
}

// Callback controller: verify signature, update order status
public function postProcess(): void
{
    $raw  = file_get_contents('php://input');
    $data = json_decode($raw, true);

    if (!hash_equals(
        hash_hmac('sha256', $raw, Configuration::get('MYPAY_SECRET_KEY')),
        $_SERVER['HTTP_X_SIGNATURE'] ?? ''
    )) {
        http_response_code(403); exit;
    }

    $statusMap = [
        'succeeded' => Configuration::get('MYPAY_OS_PAID'),
        'failed'    => Configuration::get('PS_OS_ERROR'),
        'cancelled' => Configuration::get('PS_OS_CANCELED'),
    ];

    $order = Order::getByReference($data['payment_id'])->getFirst();
    if ($order && isset($statusMap[$data['status']])) {
        $history = new OrderHistory();
        $history->id_order = $order->id;
        $history->changeIdOrderState((int) $statusMap[$data['status']], $order);
        $history->addWithemail(true);
    }

    http_response_code(200); echo 'OK'; exit;
}

Why HMAC Signature Verification Matters

Webhook endpoints without signature verification accept requests from anyone, not just the payment provider. An attacker who knows your callback URL could send a fake succeeded status and mark an unpaid order as paid. All major payment providers support HMAC or RSA signature verification, and we implement it in every integration.

PrestaShop 8.x does not provide automatic HMAC validation. We implement it explicitly in the callback controller using hash_equals to prevent timing attacks.

Refund Processing

PrestaShop does not automatically notify the payment module when an admin issues a refund from the order management panel. We subscribe to the actionOrderStatusUpdate hook and trigger a refund API call when the order transitions to the refund status:

public function hookActionOrderStatusUpdate(array $params): void
{
    if ($params['newOrderStatus']->id !== (int) Configuration::get('PS_OS_REFUND')) {
        return;
    }
    (new MyPayApiClient(
        Configuration::get('MYPAY_API_KEY'),
        Configuration::get('MYPAY_SECRET_KEY')
    ))->refund($params['order']->reference, (int) round($params['order']->total_paid * 100));
}

Contact us to discuss your payment integration requirements. We will review your PrestaShop version, gateway choice, and order flow, then provide a fixed-price quote.

Pre-Launch Testing Checklist

Before going live, every payment integration we build passes a structured test protocol in the sandbox environment.

We test successful payment and verify the order reaches Paid status. We test failed payment and verify the order stays in Pending or moves to Failed. We test a cancelled payment from the provider's page and verify the order does not change incorrectly. We simulate a webhook retry and verify the order does not get double-updated. We test the refund flow from the PrestaShop admin and verify the refund API call fires correctly.

Only after all scenarios pass in sandbox mode do we switch to live credentials and run a real test transaction before handover.

How We Deliver

We review your PrestaShop version and gateway API docs. We set up the module scaffold. We build the payment controller. We build the callback controller with signature verification. We add the admin configuration page. We test in sandbox mode. We deploy to production. We run a live test transaction. We hand over the module with documentation.

Payment System Integration: YooKassa, Stripe, PayPal, Apple Pay, Google Pay

Conversion dropped by 12% immediately after the redesign. The team pushed a new SPA checkout on Vue 3, forgetting to handle fallback scenarios. Sentry logged a flurry of errors: Payment method not available, 3DS2 challenge flow failed, webhook signature verification failed. Users abandoned carts at the payment method selection stage. Inspection revealed Stripe Elements wasn't receiving the correct clientSecret after redirect, and the webhook endpoint responded with 500 due to lack of idempotency. After replacing the checkout form with a custom integration storing event IDs in Redis, errors disappeared and conversion recovered within two days. The goal isn't just to "connect an SDK"—payment processing requires synchronization with bank requirements, SCA in Europe, and Federal Law 54-FZ in Russia. Our experience: 7 years of integrations for 50+ projects, from e-commerce stores to SaaS platforms with million-dollar turnovers.

What's Included in Turnkey Work

• Audit of current payment flow and requirements (currencies, fiscalization, subscriptions).
• Provider selection based on geography and business model.
• Backend integration (Laravel/Node.js/Go) with webhook handling, idempotency, and retries.
• Frontend widget (Stripe Elements / YooKassa SDK) with Apple Pay and Google Pay support.
• Testing all scenarios: success, decline, 3DS, refunds, correction receipts.
• Monitoring of first transactions and documentation.

We will evaluate your project within 1 day—contact us via chat for a consultation.

Provider Comparison: Which to Choose

Stripe wins on flexibility: 135+ currencies vs. YooKassa's single currency. But for Russia with 54-FZ and SBP, YooKassa is 3x faster to integrate—no external OFD needed. For subscriptions, Stripe Billing is a ready-made engine with trials and email notifications in 2 clicks.

How to Choose the Right Provider?

Three key points. Where do your clients live? Only Russia → YooKassa; globally → Stripe. Do you need 54-FZ fiscalization? Yes → YooKassa; otherwise Stripe + cloud OFD. Do you plan subscriptions? Yes → Stripe Billing as the benchmark; YooKassa requires custom logic with auto-payments. Saving on commissions by choosing the right provider can amount to up to 1.5% of turnover. For a project with 2 million RUB per month, that's 360,000 RUB per year.

Where the Real Difficulties Lie

Setting up a test mode takes an hour. Properly handling all scenarios takes weeks.

Webhook reliability. A webhook may not arrive—server unavailable, timeout, network issues. The provider retries with exponential backoff (Stripe up to 3 days). The handler must be idempotent: if payment.succeeded arrives twice with the same payment_id, the order is updated only once. This is implemented by storing event IDs in Redis with a TTL.

3DS2 and redirect flow. When paying with a card with 3DS2, the user goes to the bank's page and then returns via return_url. During this time, the session may expire or the cart may be cleared. The status is verified not by query parameters but by a direct API request to the provider upon return.

Partial refunds and receipts. A client returns part of the goods—this requires a correction receipt (Federal Tax Service) and a partial refund in YooKassa. Stripe natively supports partial_refund. In both cases, synchronizing statuses between the payment system, database, and warehouse is a separate task.

Currency limitations. YooKassa only handles rubles. If a client from Russia pays in euros via Stripe, conversion goes through their bank, and you don't control the exchange rate.

Why Do Webhooks Require Idempotency?

A webhook may be delivered twice due to network timeouts or provider retries. Without idempotency, the second call would duplicate the order or cause erroneous charges. The solution is to store a unique event ID (e.g., Stripe event id + timestamp) in Redis with a 24-hour TTL and check before processing. If the ID already exists, return 200 without executing business logic. Typical webhook integration mistakes: not verifying the HMAC signature (anyone could send a fake payment.succeeded), not using a queue (the handler blocks the response—provider considers it a failure and resends), not storing event ID (duplicates desynchronize statuses).

How We Build the Integration

Architecture. We never store card data—only tokens from the provider. Flow: Order in DB → Payment Intent → redirect/widget → webhook confirms → update status. The source of truth is the status in the payment system.

For Laravel we use stripe/stripe-php or yookassa-sdk. Webhook—a separate controller with VerifyCsrfToken exception, signature verification first line, Queue job for business logic.

For Next.js/React—@stripe/stripe-js + @stripe/react-stripe-js. PaymentElement includes Apple/Google Pay automatically. Example:

const stripe = await stripePromise;
const { error } = await stripe.confirmPayment({
  elements,
  confirmParams: { return_url: 'https://example.com/order/thank-you' },
});

Testing. Stripe CLI: stripe listen --forward-to localhost:8000/webhook. Test cards for all scenarios (3DS, decline, insufficient funds). Cypress checkout flow test in CI—mandatory stability guarantee.

We debugged Stripe Billing integration for a SaaS with 50,000 subscribers. The issue was handling invoice.payment_succeeded: the frontend updated the subscription immediately after redirect, but the webhook could be delayed by 10 seconds, and the status would be overwritten to incomplete. Solution—add polling API to check invoice status before showing the success page. This reduced erroneous cancellations by 18%.

Process and Timeline

Audit → provider selection → backend → frontend → tests → deploy → monitoring.

Pricing is custom. Order integration and your checkout won't crash on the next update.

Links:

• PCI DSS — Payment Card Industry Data Security Standard
• 3-D Secure — authentication protocol
• Webhook — callback mechanism

We guarantee: 7 years of experience, 50+ successful integrations. Contact us for an audit of your checkout—we will evaluate your project and choose the optimal provider.