diff --git a/_data/sidebars/pbc_all_sidebar.yml b/_data/sidebars/pbc_all_sidebar.yml index c26fdb3e50b..542f51e2fdd 100644 --- a/_data/sidebars/pbc_all_sidebar.yml +++ b/_data/sidebars/pbc_all_sidebar.yml @@ -2183,6 +2183,8 @@ entries: url: /docs/pbc/all/payment-service-provider/base-shop/hydrate-payment-methods-for-an-order.html - title: Interact with third party payment providers using Glue API url: /docs/pbc/all/payment-service-provider/base-shop/interact-with-third-party-payment-providers-using-glue-api.html + - title: Retrieve and use payment details from third-party PSPs + url: /docs/pbc/all/payment-service-provider/base-shop/retrieve-and-use-payment-details-from-third-party-psps.html - title: "Payments feature: Domain model and relationships" url: /docs/pbc/all/payment-service-provider/base-shop/payments-feature-domain-model-and-relationships.html - title: Domain model and relationships @@ -2415,15 +2417,19 @@ entries: url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/ratepay/integrate-payment-methods-for-ratepay/integrate-the-installment-payment-method-for-ratepay.html - title: Invoice url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/ratepay/integrate-payment-methods-for-ratepay/integrate-the-invoice-payment-method-for-ratepay.html + - title: Stripe url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/stripe/stripe.html nested: - - title: SCCOS prerequisites for Stripe - url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/stripe/sccos-prerequisites-for-the-stripe-app.html - - title: Manage Stripe configurations in the ACP catalog - url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/stripe/manage-stripe-configurations-in-the-acp-catalog.html - - title: Project guidelines for Stripe + - title: Install the prerequisites + url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/stripe/install-and-configure-stripe-prerequisites.html + - title: Connect and configure + url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/stripe/connect-and-configure-stripe.html + - title: Project guidelines url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/stripe/project-guidelines-for-stripe.html + - title: Disconnect + url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/stripe/disconnect-stripe.html + - title: Unzer url: /docs/pbc/all/payment-service-provider/base-shop/third-party-integrations/unzer/unzer.html nested: diff --git a/docs/about/all/about-the-docs/docs-updates.md b/docs/about/all/about-the-docs/docs-updates.md index 9a37619f082..dc843b6599e 100644 --- a/docs/about/all/about-the-docs/docs-updates.md +++ b/docs/about/all/about-the-docs/docs-updates.md @@ -37,7 +37,7 @@ In February 2024, we have added and updated the following pages: - [Secure coding practices for external packages](/docs/dg/dev/guidelines/coding-guidelines/secure-coding-practices-for-external-packages.html). - [Merchant Portal Agent Assist feature overview](/docs/pbc/all/user-management/202404.0/marketplace/merchant-portal-agent-assist-feature-overview.html). - [Finilizing upgrades](/docs/ca/devscu/finilizing-upgrades.html): Learn how you can make sure everything works correctly after upgrading a module. -- [Manage Stripe configurations in the ACP catalog](/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/manage-stripe-configurations-in-the-acp-catalog.html). +- [Manage Stripe configurations in the ACP catalog](/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/connect-and-configure-stripe.html). - [Project guidelines for the Stripe app](/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/project-guidelines-for-stripe.html). ### Updated pages diff --git a/docs/pbc/all/payment-service-provider/202311.0/base-shop/retrieve-and-use-payment-details-from-third-party-psps.md b/docs/pbc/all/payment-service-provider/202311.0/base-shop/retrieve-and-use-payment-details-from-third-party-psps.md new file mode 100644 index 00000000000..56fb2adac6f --- /dev/null +++ b/docs/pbc/all/payment-service-provider/202311.0/base-shop/retrieve-and-use-payment-details-from-third-party-psps.md @@ -0,0 +1,94 @@ +--- +title: Retrieve and use payment details from third-party PSPs +description: Learn how to retrieve and use payment details from a third-party payment service providers +last_updated: Mar 20, 2024 +template: howto-guide-template +--- + +This document describes how to retrieve and use payment details from third-party payment service providers (PSPs). + +## Configure payment details to be retrieved + +1. Install the required modules using Composer: + +```bash +composer require spryker/sales-payment-detail +``` + +2. In `config/Shared/config_default.php`, add or update the shared configs: + +```php +//... + +use Generated\Shared\Transfer\PaymentCreatedTransfer; + +$config[MessageBrokerConstants::MESSAGE_TO_CHANNEL_MAP] = [ + //... + PaymentCreatedTransfer::class => 'payment-events', +]; + +$config[MessageBrokerConstants::CHANNEL_TO_RECEIVER_TRANSPORT_MAP] = [ + //... + 'payment-events' => MessageBrokerAwsConfig::HTTP_CHANNEL_TRANSPORT, +]; + +``` + +3. In `src/Pyz/Zed/MessageBroker/MessageBrokerDependencyProvider.php`, add or update the config of the message broker dependency provider: + +```php + +namespace Pyz\Zed\MessageBroker; + +use Spryker\Zed\MessageBroker\MessageBrokerDependencyProvider as SprykerMessageBrokerDependencyProvider; +use Spryker\Zed\SalesPaymentDetail\Communication\Plugin\MessageBroker\PaymentCreatedMessageHandlerPlugin; + +class MessageBrokerDependencyProvider extends SprykerMessageBrokerDependencyProvider +{ + /** + * @return array<\Spryker\Zed\MessageBrokerExtension\Dependency\Plugin\MessageHandlerPluginInterface> + */ + public function getMessageHandlerPlugins(): array + { + return [ + //... + + # This plugin is handling the `PaymentCreated` messages sent from any Payment App that supports this feature. + new PaymentCreatedMessageHandlerPlugin(), + ]; + } +} + +``` + +4. In `src/Pyz/Zed/MessageBroker/MessageBrokerConfig.php`, add or update the config of the message broker channels: + +```php +namespace Pyz\Zed\MessageBroker; + +use Spryker\Zed\MessageBroker\MessageBrokerConfig as SprykerMessageBrokerConfig; + +class MessageBrokerConfig extends SprykerMessageBrokerConfig +{ + /** + * @return array + */ + public function getDefaultWorkerChannels(): array + { + return [ + //... + 'payment-events', + ]; + } + + //... +} +``` + +## Using payment details from third-party PSPs + +When a third-party PSP supports this feature, your shop receives asynchronous messages about each payment when it's created. + +To use the data of the `spy_sales_payment_detail` table, you need to combine the data from the table with the entity you are fetching from the database to which this payment detail is related. + +When the payment is used in the normal order process, the payment detail can be combined by using `spy_sales_order.order_reference` and `spy_sales_payment_detail.entity_reference`. diff --git a/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/manage-stripe-configurations-in-the-acp-catalog.md b/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/connect-and-configure-stripe.md similarity index 53% rename from docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/manage-stripe-configurations-in-the-acp-catalog.md rename to docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/connect-and-configure-stripe.md index 3566deff2ec..455eddffb8a 100644 --- a/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/manage-stripe-configurations-in-the-acp-catalog.md +++ b/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/connect-and-configure-stripe.md @@ -1,26 +1,20 @@ --- -title: Manage Stripe configurations in the ACP catalog +title: Connect and configure Stripe description: Find out how you can configure the Stripe app in your Spryker shop -draft: true last_updated: Jan 31, 2024 template: howto-guide-template -related: - - title: Stripe - link: docs/pbc/all/payment-service-provider/page.version/base-shop/third-party-integrations/stripe/stripe.html redirect_from: - /docs/pbc/all/payment-service-provider/202311.0/third-party-integrations/stripe/install-stripe.html - /docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/configure-stripe.html - /docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/disconnect-stripe.html +- /docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/manage-stripe-configurations-in-the-acp-catalog.html --- -This document describes how to connect configure the Stripe app in the ACP catalog of your Back Office. -Once you have , you can configure it. +This document describes how to connect and configure the Stripe app in the Back Office. ## Prerequisites -Before configuring Stripe in the ACP catalog, make sure you have met these prerequisites: -- [Prerequisites for using the Stripe app](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/third-party-integrations/stripe/stripe.html#prerequisites-for-using-the-stripe-app) -- [SCCOS prerequisites for Stripe](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/third-party-integrations/stripe/install-stripe.html) +[Install and configure Stripe prerequisites](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/third-party-integrations/stripe/install-and-configure-stripe-prerequisites.html) ## Connect and configure the Stripe app @@ -37,29 +31,5 @@ Before configuring Stripe in the ACP catalog, make sure you have met these prere 9. Optionally: In *Payment page title*, enter your shop name. This name will be displayed on the *Payment* page as a merchant label for the payee. ![stripe-configuration](https://spryker.s3.eu-central-1.amazonaws.com/docs/pbc/all/payment-service-providers/stripe/configure-stripe/stripe-configuration.png) 10. Click **Save**. -If the app was connected successfully, a corresponding message appears, and the app status changes to **Connected**. +If the app was connected successfully, a corresponding message appears, and the app status changes to **Connected**. 11. Activate Stripe in your store's Back office, in **Administration** -> **Payment methods**. For details, see [Edit payment methods](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/manage-in-the-back-office/edit-payment-methods.html). - -## Disconnect the Stripe App - -Disconnecting the Stripe app from your store makes it unavailable to your customers as a payment option. - -{% info_block infoBox "Info" %} - -You should only disconnect if there are no open orders that still use the Stripe payment method. - -{% endinfo_block %} - -To disconnect the Stripe app from your store, do the following: -1. In your store's Back Office, go to **Apps**. -2. Click **Stripe**. -3. On the Stripe app details page, next to the **Configure** button, hold the pointer over ![disconnect-button](https://spryker.s3.eu-central-1.amazonaws.com/docs/aop/user/apps/bazzarvoice/disconnect-button.png) and click **Disconnect**. -4. In the message that appears, click **Disconnect**. This removes the Stripe configurations from the Back Office and from the Storefront. - -{% info_block infoBox "Info" %} - -If you want to use the Stripe app after the disconnection, you will need to reconnect the App. - -{% endinfo_block %} - - diff --git a/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/disconnect-stripe.md b/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/disconnect-stripe.md new file mode 100644 index 00000000000..b3e3cbbe86b --- /dev/null +++ b/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/disconnect-stripe.md @@ -0,0 +1,21 @@ +--- +title: Disconnect Stripe +description: Learn how to disconnect Stripe in the Back Office +last_updated: Mar 24, 2024 +template: howto-guide-template +--- + +This document describes how to disconnect Stripe from your store. + + +## Prerequisites + +Complete all the orders that were placed with Stripe used as a payment method. + +## Disconnect Stripe from Spryker + +1. In the Back Office, go to **Apps**. +2. Click **Stripe**. +3. On the Stripe app details page, next to the **Configure** button, hold the pointer over ![disconnect-button](https://spryker.s3.eu-central-1.amazonaws.com/docs/aop/user/apps/bazzarvoice/disconnect-button.png) and click **Disconnect**. +4. In the message that appears, click **Disconnect**. + This removes the Stripe configurations from the Back Office and from the Storefront. diff --git a/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/sccos-prerequisites-for-the-stripe-app.md b/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/install-and-configure-stripe-prerequisites.md similarity index 69% rename from docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/sccos-prerequisites-for-the-stripe-app.md rename to docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/install-and-configure-stripe-prerequisites.md index fe90e352321..add039ca460 100644 --- a/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/sccos-prerequisites-for-the-stripe-app.md +++ b/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/install-and-configure-stripe-prerequisites.md @@ -1,34 +1,38 @@ --- -title: SCCOS prerequisites for the Stripe app -description: Find out about the SCCOS modules needed for the Stripe App to function and their configuration -draft: true -last_updated: Jan 31, 2024 +title: Install and configure Stripe prerequisites +description: Learn how to prepare your project for Stripe +last_updated: Mar 20, 2024 template: howto-guide-template -related: - - title: Stripe - link: docs/pbc/all/payment-service-provider/page.version/base-shop/third-party-integrations/stripe/stripe.html redirect_from: - /docs/pbc/all/payment-service-provider/202311.0/third-party-integrations/stripe/install-stripe.html - /docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/install-stripe.html - /docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/integrate-stripe.html - +- /docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/sccos-prerequisites-for-the-stripe-app.html --- -This document gives an overview of the SCCOS prerequisites required for the [Stripe App](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/third-party-integrations/stripe/stripe.html) to function in your Spryker Shop. -{% info_block infoBox "Info" %} +To install and configure the prerequisites for the [Stripe App](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/third-party-integrations/stripe/stripe.html), take the following steps. + + +## Fulfill Stripe's prerequisites -The steps listed is this document are only necessary if your Spryker shop doesn't contain the packages (or their versions are outdated) and configurations below. +* Create a Stripe account. +* Make sure [your countries are supported by Stripe](https://stripe.com/global). +* Make sure [your business is not restricted by Stripe](https://stripe.com/legal/restricted-businesses). -{% endinfo_block %} +## Fulfill ACP prerequisites +* Connect your Stripe account to the Spryker Platform account. Request this link by [creating a support case](https://support.spryker.com/s/). +* Enable ACP in your project. For instructions, see [App Composition Platform installation](/docs/acp/user/app-composition-platform-installation.html). Make sure you are using the latest version of the Message Bus. We'll verify this during onboarding, and a migration may be necessary to enable the Stripe app. -## 1. Required packages +## Install packages and add configuration -The Stripe app catalog page lists specific packages that must be installed or upgraded before you can use the Stripe app. To check the list of the necessary packages, in the Back Office, go to **Apps**-> **Stripe**. Ensure that your installation meets these requirements. +1. Install the required packages. + To check the list of required packages, in the Back Office, go to **Apps**>**Stripe**. -## 2. Configure shared configs +2. Add or update the shared configs: -Your project probably already contains the following code in `config/Shared/config_default.php` already. If not, add it: +
+ config/Shared/config_default.php ```php //... @@ -80,6 +84,9 @@ $config[MessageBrokerConstants::MESSAGE_TO_CHANNEL_MAP] = [ PaymentRefundFailedTransfer::class => 'payment-events', PaymentCanceledTransfer::class => 'payment-events', PaymentCancellationFailedTransfer::class => 'payment-events', + + # [Optional] This message can be received from your project when you want to use details of the Stripe App used payment. + PaymentCreatedTransfer::class => 'payment-events', ]; $config[MessageBrokerConstants::CHANNEL_TO_RECEIVER_TRANSPORT_MAP] = [ @@ -95,9 +102,9 @@ $config[MessageBrokerConstants::CHANNEL_TO_SENDER_TRANSPORT_MAP] = [ ``` -## 3. Configure the Message Broker dependency provider +
-Your project probably already contains the following code in `src/Pyz/Zed/MessageBroker/MessageBrokerDependencyProvider.php` already. If not, add it: +3. In `src/Pyz/Zed/MessageBroker/MessageBrokerDependencyProvider.php`, add or update the config of the Message Broker dependency provider: ```php @@ -106,6 +113,7 @@ namespace Pyz\Zed\MessageBroker; use Spryker\Zed\MessageBroker\MessageBrokerDependencyProvider as SprykerMessageBrokerDependencyProvider; use Spryker\Zed\Payment\Communication\Plugin\MessageBroker\PaymentOperationsMessageHandlerPlugin; use Spryker\Zed\Payment\Communication\Plugin\MessageBroker\PaymentMethodMessageHandlerPlugin; +use Spryker\Zed\SalesPaymentDetail\Communication\Plugin\MessageBroker\PaymentCreatedMessageHandlerPlugin; class MessageBrokerDependencyProvider extends SprykerMessageBrokerDependencyProvider { @@ -119,15 +127,16 @@ class MessageBrokerDependencyProvider extends SprykerMessageBrokerDependencyProv # These plugins are handling messages sent from Stripe app to your project. new PaymentOperationsMessageHandlerPlugin(), new PaymentMethodMessageHandlerPlugin(), + + # [Optional] This plugin is handling the `PaymentCreated` messages sent from Stripe App. + new PaymentCreatedMessageHandlerPlugin(), ]; } } ``` -## 4. Configure channels in Message Broker configuration - -Add the following code to `src/Pyz/Zed/MessageBroker/MessageBrokerConfig.php`: +4. In `src/Pyz/Zed/MessageBroker/MessageBrokerConfig.php`, add or updated the channels config in the message broker config: ```php namespace Pyz\Zed\MessageBroker; @@ -152,8 +161,8 @@ class MessageBrokerConfig extends SprykerMessageBrokerConfig } ``` -## 5. Configure the Order State Machine (OMS) -Your project is likely to have the following in `src/Pyz/Zed/Oms/OmsDependencyProvider.php` already. If not, add it: +5. In in `src/Pyz/Zed/Oms/OmsDependencyProvider.php`, add or updated the OMS config: + ```php use Spryker\Zed\SalesPayment\Communication\Plugin\Oms\SendCapturePaymentMessageCommandPlugin; @@ -175,7 +184,7 @@ use Spryker\Zed\SalesPayment\Communication\Plugin\Oms\SendCancelPaymentMessageCo // These two commands will be also supported soon by ACP Stripe app. $commandCollection->add(new SendRefundPaymentMessageCommandPlugin(), 'Payment/Refund'); $commandCollection->add(new SendCancelPaymentMessageCommandPlugin(), 'Payment/Cancel'); - + return $commandCollection; }); @@ -185,4 +194,5 @@ use Spryker\Zed\SalesPayment\Communication\Plugin\Oms\SendCancelPaymentMessageCo ``` ## Next step -[Configure Stripe in the Back Office](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/third-party-integrations/stripe/configure-stripe.html) \ No newline at end of file + +[Connect and configure Stripe](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/third-party-integrations/stripe/connect-and-configure-stripe.html) diff --git a/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/stripe.md b/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/stripe.md index f975d45a8c1..3568fcc377d 100644 --- a/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/stripe.md +++ b/docs/pbc/all/payment-service-provider/202311.0/base-shop/third-party-integrations/stripe/stripe.md @@ -1,45 +1,35 @@ --- title: Stripe description: Stripe technology partner -last_updated: Jan 31, 2024 +last_updated: Mar 24, 2024 template: concept-topic-template -related: - - title: Install Stripe - link: docs/pbc/all/payment-service-provider/page.version/base-shop/third-party-integrations/stripe/install-stripe.html --- [Stripe](https://stripe.com/en-de) is a financial infrastructure platform that enables businesses to accept payments, grow their revenue, and accelerate new business opportunities. -The Stripe integration in Spryker is a part of the App Composition Platform and supports both the default Storefront Yves and Spryker GLUE APIs. +The Stripe integration in Spryker is part of the App Composition Platform and supports both the default Storefront Yves and Spryker GLUE APIs. ## Supported business models -The Stripe App supports the business-to-business (B2B) and business-to-consumer (B2C) models. -## Features -The Stripe app has the following features: +The Stripe App supports B2B and B2C models. + +## Stripe features + - Interface within the Spryker ACP catalog to connect with Stripe: You can connect to Stripe from the App Composition Platform. -- Easy switch between Test and Live mode: You can test payments in either mode. -- Responsive Redirect Payment Page: Once a connection is set up between Spryker & Stripe, upon checkout, end users are redirected to a Spryker-hosted payment page where they can view activated payment methods. This works both on the web and mobile. +- Easy switch between Test and Live modes: You can test payments in either mode. +- Responsive Redirect Payment Page: Once a connection is set up between Spryker and Stripe, upon checkout, end users are redirected to a Spryker-hosted payment page where they can view activated payment methods. This works both on the web and mobile. - Viewing the activated payment methods in the Stripe dashboard. - GLUE API support: Support for customers using Spryker headless. - Authorize payments and capture later: The default OMS configuration lets you authorize cards and capture the order amount either after shipping or based on the established business logic. - Default OMS Configuration: We provide a default OMS configuration that you can use as an example or modify to align with your business logic. -## Prerequisites for using the Stripe app +## Stripe payment methods -1. You have a Stripe Account. -2. Your Stripe Account is connected to the Spryker Platform account. Request this link by [creating a case](https://support.spryker.com/s/). -3. Your Spryker project is ACP-enabled. For more information on the ACP enablement process, see [App Composition Platform installation](/docs/acp/user/app-composition-platform-installation.html). If your project is ACP-enabled, make sure that your project setup with ACP uses the latest version of our Message Bus. We'll verify this during onboarding, and migration may be necessary to enable the use of the Stripe App. -4. You have the required [SCCOS prerequisites](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/third-party-integrations/stripe/install-stripe.html). -5. Your country is included in the [list of countries supported by Stripe](https://stripe.com/global). -6. Your business isn't listed among the [prohibited and restricted businesses](https://stripe.com/legal/restricted-businesses). - -## Payment methods -The Stripe app supports all payments enabled by Stripe in your region. For more information, see [Payment methods in Stripe](https://stripe.com/docs/payments/payment-methods/overview). +The Stripe app supports all payments enabled by Stripe in your region. For more information, see [Payment methods in Stripe](https://stripe.com/docs/payments/payment-methods/overview). However, our team only tested the following payment methods: - Cards: including Visa and Mastercard - Debit card -- Bank transfer +- Bank transfer: supported in some regions, see [Bank transfer payments](https://stripe.com/docs/payments/bank-transfers) - Klarna - Apple Pay - Google Pay @@ -49,17 +39,15 @@ However, our team only tested the following payment methods: - Przelewy24 - Giropay -{% info_block infoBox "Bank transfers" %} - -Stripe supports bank transfers in specific regions. For details on this payment method, see the Stripe documentation on [Bank transfer payments](https://stripe.com/docs/payments/bank-transfers) here. - -{% endinfo_block %} - ## Current limitations The Stripe App has limited or no support for the following features: -- Refunds & Payment Cancellation: Handling refunds & payment cancellation via the Spryker OMS. -- Payment Authorization & Capture: The current logic works with separate authorization & capture. Hence, all payment methods go through this transition. -- Payment Authorization Timeout: There is currently a one-day timeout for authorizing payments. This means that payment methods such as bank transfers, which are not authorized within this timeframe, will experience a timeout. We recommend extending the timeout from one day to seven days. -- Multi-Capture: Partial capture of payment for order items. +- Refunds and payment cancellation: Handling refunds and payment cancellation via the Spryker OMS. +- Payment authorization and capture: The current logic works with separate authorization and capture. Hence, all payment methods go through this transition. +- Payment authorization timeout: There is currently a one day timeout for authorizing payments. Payment methods, like bank transfers, which are not authorized within this timeframe, will experience a timeout. We recommend extending the timeout from one day to seven days. +- Multi-capture: Partial capture of payment for order items. + +## Next step + +[Install and configure the Stripe App prerequisites](/docs/pbc/all/payment-service-provider/{{page.version}}/base-shop/third-party-integrations/stripe/install-and-configure-stripe-prerequisites.html)