Downloads

Downloads

To download support materials, please select your product from the list below. You will automatically be shown all downloads for that product, including extensions, brochures, sales presenters and technotes.

  • 1. Select your section, category and chosen product.
  • 2. Click on the Manual, brochure, sales presenter or technote of your choice.
  • 3. Take careful note of any applicable instructions, especially for extensions.
  • 4. Download the file to your hard drive.
Knowledge Base

Knowledge Base

Stripe Payment Extension

Categories: Magento 2
Date Created: 15 Jul 2018
Last Updated: 8 Oct 2019
  1. Enable the module by running the following commands:
    php bin/magento setup:upgrade
    php bin/magento cache:flush
  2. If you are running Magento in production mode, you will also need to deploy the module's static files using the following command:
    php bin/magento setup:static-content:deploy
  3. If you are upgrading from a previous version, you will also need to run:
    php bin/magento module:enable Magespacex_StripePayments

CONFIGURATION

Navigate to Stores > Configuration > Sales > Payment Methods. There you will find a configuration section for the Stripe module:

  1. Enabled - Change to “Yes” to enable the module
  2. Title - Change this to whatever you would like to display to the customer at the checkout page.
  3. Mode - If you would like to test a payment, leave the mode to “Test”. When you are ready to accept live transactions, you can change this to “Live”. Testing cards are provided in the next section.
  4. Keys - You will also need to fill in your test and live keys that Stripe has provided to you when you created your account. You can get these by logging into Stripe, navigating to your account settings and clicking on “API Keys”
  5. Security Method: This configuration option sets the method by which card details are transmitted from the customer's browser to the payment network. There are 3 possible options here:
    • None: The card details are sent directly to your website, where the Stripe API is used to tokenize them and charge the customer. Although the card details are not saved on your website, this is considered an insecure method of handling cardholder details. The reason this is supported is because it is the most compatible method with heavily customized checkout pages. If you decide to use this method in production, we recommend that you select a hosting provider that is also PCI compliant (i.e. that had a vulnerability scan by an «Approved Scanning Vendor»). Otherwise, you can use this method during development until your website is stable and you are ready to switch to the javascript-based Stripe.js or Stripe Elements methods.
    • Stripe.js v2: The card details are sent from the customer's browser directly to Stripe's secure servers where they are tokenized for security. Using this method will both provide increased security and also enable you to use Apple Pay and Stripe Radar. If you use this method, PCI guidelines require that you validate your PCI compliance annually using SAQ A-EP, instead of the simpler SAQ A.
    • Stripe.js v3 + Stripe Elements: This is a new security method from Stripe which is different in that the form fields of the card details are hosted directly on Stripe's servers using an embedded iframe on your website. Merchants that use this method are eligible for the simplest PCI validation method: Self-Assessment Questionnaire A (SAQ A). Using this method will both provide increased security and also enable you to use Apple Pay, Stripe Radar and 3D Secure. For CSS styling of Stripe Elements, please refer to the section How to style the payment form.
  6. 3D Secure: Please see here for details on how to correctly enable 3D Secure.
  7. Apple/Android Pay: Enabling this feature will display an Apple Pay or Android Pay button at the checkout. See this section for details on additional steps necessary to enable this feature.
  8. Payment Action - Select “Authorize and Capture” if you would like the customer cards to be charged immediately after a purchase. This is the default option and it does not require you to do anything else after the customer has placed the order. If you prefer to finalize the payment later, you can choose “Authorize Only” which will lock/authorize the order amount on the customer’s card so that you can capture the amount later by issuing an invoice. You can find out more on how to capture these payments by clicking here.
  9. Expired Authorizations: If you decide to «Authorize Only» your customer's transactions, have in mind that Stripe will expire authorizations after 7 days. Under «Expired Authorizations», you can decide what to do in the admin area after authorizations have expired. Capturing the amount will work fine within 7 days but Stripe will give you an error after that. With the Stripe Payments module, you can configure it to try and re-create the original payment using one of your customer's saved cards. If you enable this feature, make sure to also enable the saved cards feature.
  10. Automatic Invoicing: If you have "Payment Action" configured to be "Authorize Only", then an invoice is not normally created because a charge is not created at the checkout. However, if you need to force generate an invoice at the checkout, either because you need to email it to the customer before the charge is created, or because you need the order status to be Processing instead of Pending, then you can enable this option. Once enabled, an invoice will be created in "Pending" status instead of the normal "Paid" status. Then, after you capture the payment, the invoice will switch to "Paid" status and the order status will change to "Complete".
  11. Stripe Radar: Enabling Stripe Radar will place orders under manual review if they are marked as Elevated risk by Stripe. Please see the section Enabling fraud prevention features (Stripe Radar) for additional details.
  12. Save Customer Cards: Enable if you want Amazon-style saved cards on your website, so that customers do not enter their details more than once. This feature does not store cards or card tokens on your server and is fully PCI compliant. For more details, please see the «Saved Cards» section in this document.
  13. Pay in store currency - If you are running a multi-currency / multi-language website, then you can charge your customers either in the configured base currency or in the foreign currency that they see in the checkout. This is enabled by default, but if you have reason to prefer the base currency (i.e. some Canadian Stripe accounts have currency restrictions) then you can disable this.
  14. New Order Status - This is the order status that will automatically be assigned to each new order.
  15. Enable Stripe email receipts: This setting will force the module to always send the customer email to Stripe, even for guest customers, which is a requirement if you have Stripe Email Receipts enabled in your Stripe account. Enabling email receipts will allow you to send customized payment emails to your customers through Stripe. Deliverability of these emails is higher than many Magento setups, and can be used without setting up a mailing system on your Magento server.
  16. Payment Applicable From - If you only want to provide this payment option to certain countries, you can optionally change the “Payment Applicable From” to “Specific Countries”
  17. Payment From Specific Countries Select the countries for which this payment method should appear at the checkout.
  18. Sort Order - If you have multiple payment methods enabled, this setting will determine the order of the Stripe payment method at the checkout page. For example, if you also have PayPal enabled and would like Stripe to appear after PayPal, then set this number to something larger than what is configured in the PayPal configuration section.
Support Enquiry

Support Enquiry

If you have a question or require technical support for a Magespacex hosting or extensions you have purchased, please fill out the form below and a member of our support team will contact you shortly.

  • * Required Fields

Warranty