PTS Stripe

What is PTS Stripe?

PTS Stripe connects your store to Stripe so you can take card payments, digital wallets such as Apple Pay, Google Pay, Link, PayPal or Amazon Pay, the usual bank methods of each European country, and the voucher methods used in Brazil, Mexico or Portugal. Each one is enabled separately and can be limited to the countries and customer groups you choose.

Besides taking payments inside the checkout, it adds express purchase buttons on the product page, the cart and the payment page, and its own tab on every back office order where you can review the payment and issue refunds without opening the Stripe dashboard.

Main Features

System Requirements

Method 1: Installation from Back Office

Method 2: Installation via FTP

Possible Installation Issues

If you experience override errors when installing or activating the module, do not attempt to resolve it yourself if you lack technical experience. Contact our support team to receive personalized help and resolve the conflict safely.

General

Holds the module's diagnostic options and the behaviour of automatic refunds.

Debug mode

When you enable this option, the module's payment methods are only shown to the IP addresses you list in the "IP" field. That way you can test payments in your own store while the rest of your customers keep buying with the payment methods you already had.

IP

Lists the addresses the module will be visible from while debug mode is active. The button next to the field adds the address you are browsing from at that moment, which is the easiest way not to get it wrong.

Enable debug logs

Stores in the back office logs the detail of every payment: when the payment attempt is created, how express purchase shipping costs are calculated, and which notifications Stripe sends. It is meant for diagnosing a specific incident together with support, not for leaving it on day to day.

Auto-refund on credit slip

When someone creates a credit slip in PrestaShop, the module issues the refund in Stripe for that same amount, without having to repeat the operation by hand on the order tab. It is disabled by default: enable it only if your way of working is to always issue the credit slip first.

Getting your Stripe keys

The module connects to your Stripe account with two keys: a publishable key, which starts with pk_ and is used on the payment page, and a secret key, which starts with sk_ and is used only by your server. Stripe gives you one pair for testing (pk_test_ and sk_test_) and another for real charges (pk_live_ and sk_live_). Usually nothing else is needed: the module creates the webhook itself when it connects, and the status box tells you if it could not.

Stripe

This is where the store connects to your Stripe account. Usually it is enough to paste the two keys of the mode you are going to use: when you save them, the module checks them and tries to create your store's webhook in Stripe, and the status box tells you whether it succeeded. If you do not have them yet, see Getting your Stripe keys.

Sandbox mode (test)

Switches between Stripe's test environment and the real one. With the mode enabled, the module works with your test keys and no charge is real, so you can place complete orders with Stripe's test cards. When you disable it, it starts using the live keys and payments are charged for real.

The fields shown below change depending on the switch: with the mode enabled you are asked for the Public test key, the Secret test key and the Test webhook secret; with the mode disabled, the Public live key, the Secret live key and the Live webhook secret. Each mode keeps its own, so you can have both configured and switch from one to the other without pasting anything again.

Test webhook secret

This is the signature the module uses to verify that a test notification really comes from Stripe and not from a third party. You do not need to type it: it is filled in automatically when the module connects and creates the webhook in Stripe. Paste it by hand only if the automatic connection could not create the webhook.

Live webhook secret

The same for real payments. Since Stripe uses a different webhook for each mode, each one has its own secret, and the module uses the right one depending on whether the notification comes from test or live mode.

Connection status

Below the fields, a box tells you how the selected mode stands: the name of the Stripe account the store is connected to, whether the webhook is registered, or what is wrong if something does not work. The usual errors come with their fix (a key in the wrong field, a key from the other mode, a key Stripe does not accept or a server that cannot reach Stripe); any other one is shown with the message Stripe returns. The Connect with Stripe button, or Check connection again if it has connected before, repeats the check whenever you want.

When it connects, the module registers your store's Webhook URL, the one you see at the bottom of the screen, in your Stripe account with the events it needs. If there was already a webhook for that same address, it updates it and re-enables it if Stripe had disabled it after failed deliveries; if it was one created by hand whose secret the module does not know, it replaces it with a new one. Webhooks belonging to other stores or other applications in your account are left alone.

Payments

This tab decides how payment methods are presented to the customer: all together inside a single form, or each one as an independent option in the payment list. It is an either/or choice, and the form itself changes depending on what you pick.

Enable integrated payment form

Shows every available method inside a single form instead of splitting them into separate options. Stripe then decides which methods to offer, based on the customer's country, the currency and the order amount, so you do not need to enable them one by one.

Integrated form design

Choose how methods are grouped inside the form: Tabs, Accordion (with radio buttons) or Accordion (without radio buttons). With few options tabs read better; with many, the accordion takes up less room.

Integrated form theme

Visual appearance of the form: Stripe, Flat, Night or None. The first three are the styles Stripe ships. With "None" the form gets none of them and is drawn with the browser's minimal appearance, which is the most neutral starting point if your checkout has a very distinctive design. Bear in mind that Stripe draws the form inside an isolated frame: it does not pick up your theme's styles, so "None" does not blend it into your design on its own.

Restrict by countries

Limits which delivery countries the method is offered in. If you leave it empty, it is shown in all of them. This is how you offer each market what is actually used there, instead of showing everyone a long list of local methods from other countries.

Restrict by customer groups

Limits which customer groups the method is offered to. If you leave it empty, it is shown to all of them. It is useful, for example, to reserve deferred payment for wholesale customers, or to keep a method for a single group while you test it.

Payment methods

With the integrated form disabled, each method is enabled separately and appears as its own option in the checkout payment list. All of them accept the same delivery country and customer group restrictions explained above.

Credit/Debit Card

Takes payment with the usual credit and debit cards inside the checkout itself, without the customer leaving your store. When the bank requires strong authentication, the 3D Secure screen appears on its own and the customer returns to the same place afterwards.

Show postal code in card form

Adds the postal code field to the card form. In some countries the bank uses it as an extra check on the cardholder, so it can reduce declines; in others it is just one more field to fill in. It only appears when card is enabled.

iDEAL

The most used method in the Netherlands. On confirming, the customer goes to their bank's page, authorises the transfer and returns to the store with the order already placed.

Bancontact

The Belgian equivalent: the customer authorises the payment at their bank or with their app and returns to the store.

Klarna

Lets the customer pay later or in instalments, depending on what Klarna offers them in their country. The customer completes the process on Klarna and you get the full amount all the same.

EPS

The usual online bank transfer in Austria. The customer picks their bank and confirms the payment there.

Przelewy24 (P24)

A Polish gateway that brings together most banks in the country. The customer chooses theirs and authorises the transfer.

BLIK

Polish as well, but without leaving the store: the customer opens their banking app, generates a six-digit code and types it into the checkout.

TWINT

The most widespread mobile payment app in Switzerland. The customer confirms the purchase from their phone.

Afterpay / Clearpay

Deferred payment in several instalments, interest-free for the customer. It is called Clearpay in the United Kingdom and Afterpay in the other markets where it operates.

PayPal

Takes PayPal payments through your own Stripe account, without installing the separate PayPal module. The customer authorises the payment on PayPal and returns to the store.

SEPA Direct Debit

The customer types their IBAN and authorises the charge on their account. Bear in mind that a direct debit takes days to confirm: the order is not paid at that moment, but when Stripe reports that the bank has accepted the charge.

Pix

Brazilian instant payment. The customer gets a code, pays it from their banking app and the order is confirmed as soon as Stripe receives the money.

OXXO

The customer gets a voucher with a number and pays in cash at any OXXO shop in Mexico. The order stays on hold until Stripe confirms the deposit.

Boleto

The usual payment document in Brazil: the customer downloads a PDF and pays it at their bank or through the app. The order is confirmed when the deposit arrives.

Multibanco

In Portugal, the customer gets an entity and a reference to pay with from their bank or at an ATM. The order stays on hold until the payment is received.

Affirm

Instalment payment in the United States and Canada. The customer takes out the financing with Affirm and you get the full amount.

Where the buttons appear

On the cart, the payment page and the side cart, the position is fixed. On the product page you can choose it, because that is where themes vary the most.

Product Page — Button Position

Choose at which point of the product page the buttons are drawn:

• Additional product information (displayProductAdditionalInfo): below the product details. This is the factory value and the one most themes support.
• After Add to Cart button (displayAfterProductAddCartBtn): right under the purchase button.
• Product actions area (displayProductActions): inside the actions block, next to the add to cart button.
• Custom CSS selector (advanced): anywhere on the page, with you pointing at the reference element.

CSS selector

Points at the element the buttons will be placed next to, for example the add to cart button. It only appears when you have chosen the "Custom CSS selector" position.

Position relative to the element

Decides where the buttons are placed with respect to the element matching the selector: Before the element (beforebegin), Inside, at the start (afterbegin), Inside, at the end (beforeend) or After the element (afterend, default). It also only appears in CSS selector mode.

How the buttons look

These options apply to every express purchase button at once, on all the pages where they appear.

Button Height (px)

Height shared by every button. Stripe accepts values between 40 and 55 pixels; the factory value is 48. It is worth bringing it close to the height of your theme's purchase button so they do not clash.

Max Columns

Maximum number of buttons per row. With Unlimited (default) Stripe distributes them according to the available width, which is usually the most sensible choice if you have several wallets enabled.

Max Rows

Maximum number of button rows. Those that do not fit go into the overflow menu, so a customer with many wallets available does not end up with half a screen of buttons.

Overflow Menu

Decides what happens to the buttons that do not fit in the grid. With Auto (default) Stripe sorts it out; with Never none of them are grouped.

Hide carriers

The carriers you tick here are not offered inside the wallet window. This is the option that solves pickup points: they require the customer to choose a physical location on a map, and that screen does not exist in Apple Pay or Google Pay, so an order with such a carrier would end up without a delivery point. If you leave it empty, all of them are offered.

Where the wallet's shipping costs come from

The wallet window, whichever wallet it is, shows your carriers with their rates, worked out from the address it returns. If that address carries the province, it is used, and that holds for any country: the module recognises it by its ISO code or by its name, however it comes written. When it arrives without a province and your country splits its rates across several zones, the module works it out from the postcode in Spain, Portugal, France, Finland, the United States, Canada, Australia and Mexico. That way both the territories with their own rate (the Balearic Islands, the Canary Islands, Ceuta and Melilla, the Azores, Madeira, Corsica, the French overseas departments and Åland) and the states and provinces of the four non-European countries are charged with the zone you have configured for them, and not with the country one.

Which wallets are offered

Each wallet is enabled separately and carries the same sub-options: which pages it appears on and, where the wallet allows it, the text and colour of its button.

Apple Pay

Shows the Apple Pay button. It only appears on Apple devices with Safari, which is where the customer keeps their saved cards.

Google Pay

Shows the Google Pay button. It only appears on Chrome and compatible browsers.

Link by Stripe

Shows the Link button, Stripe's own wallet: customers who have already saved their details on any store using Stripe pay without typing them again.

PayPal

Shows the PayPal button for customers who have their account linked in the browser.

Amazon Pay

Shows the Amazon Pay button, with which the customer pays using the address and method saved in their Amazon account.

Klarna

Shows the Klarna button to buy now and pay later, without going through the whole checkout.

Show as a payment option

Available on Apple Pay and Google Pay. On top of the express purchase button, it offers the wallet as one more option inside the checkout payment list: since the customer has already identified themselves and chosen their address, a single tap is enough to finish. It is the only flow of these wallets where the customer's address and group are known, and that is why it is the only one that accepts Restrict by countries and Restrict by customer groups.

Show on Product Page

Draws that wallet's button on the product page, in the position you chose above. The customer buys that product directly, without going through the cart.

Show on Cart Page

Draws that wallet's button on the cart page, next to the button that leads to the checkout.

Show on Checkout

Draws that wallet's button on the payment page, as a shortcut for anyone who would rather finish with their wallet than fill in the form.

Show in side cart (One Page Checkout PS)

Draws the button inside the One Page Checkout PS sliding cart panel, so the customer can pay from any page of the store without opening the checkout.

Button Text

The text shown on that wallet's button. Each one accepts its own: Apple Pay and PayPal offer the longest list, Google Pay a handful, and Klarna only "Pay" or "Continue". It is worth choosing it based on where the button is: on a product page "Buy" fits better, and on the cart, "Pay".

Button Theme

The colour of that wallet's button. Apple Pay accepts black, white and white with outline; Google Pay, black and white; PayPal, gold, blue, silver, white and black; and Klarna, dark, light and outlined. Choose the one that contrasts with your theme's background, especially if it is a light one.

Stripe tab on the order

On orders paid with this module (Orders → Orders → the order you want) there is a tab called "Stripe" with everything known about the payment. On an order paid by other means the tab is not shown:

• Charge identifier, with a direct link to that operation in your Stripe dashboard.
• Payment method the customer paid with, showing the wallet name when they paid with one.
• Amount charged, amount already refunded and amount still refundable.
• Mode: whether the payment was made in test or for real.

While there is a refundable amount left, a form appears below to return the amount you enter. Type the amount, confirm, and the refund is issued in Stripe: if you return only part of it, the order moves to the partial refund status and still accepts further refunds until the total is used up.

Order statuses

On installation, the module creates three statuses of its own in PrestaShop so you can tell these situations apart at a glance:

Edit Translations

The module includes a translations editor that allows you to customize all texts in any language installed in your store.

1. Access the "Translations" section in the module configuration
2. Select the language you want to edit
3. Modify text strings as needed
4. Click "Save" to apply changes

Available Actions

The translations editor includes several actions to manage your translations:

Generate backup

To create a new backup, click the "Generate new backup" button. The system will create a backup of the module's current configuration: the Stripe keys, the enabled methods with their country and group restrictions, and the express purchase button settings.

Upload backup

If you have a previously downloaded backup, you can upload it by clicking the "Upload backup" button. A dialog will open where you can select the backup ZIP file.

Available backups

The list shows all created backups. You can filter by date using the date selector and refresh the list with the "Refresh list" button.

List actions

Each backup in the list has the following available actions:

To restore, click the "Restore backup" button of the backup you want to recover and confirm the action in the dialog.

PrestaShop and PHP

Devices and wallets

Digital wallets are not decided by the module: they appear if the customer can use them at that moment, and if not, the option is simply not shown.

Other modules

These are the checkouts we test every version against. With another module replacing the purchase process, payment methods should appear as long as it uses PrestaShop's standard integration points, but we cannot claim it as tested: the express purchase buttons and the wallets inside the payment list depend on how that checkout is built. If you use one that is not listed here, test it before opening it to your customers and write to us with the module and its version if something does not fit.

Common Issues

Frequently Asked Questions

Licenses and Purchase

Installation and Compatibility

Using the module

Updates

Technical Support

Refunds and Warranty

Customization