Skip to content

armgit / spree

Public Imported from GitHub
0

Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.

[Skip CI] updated Payments docs

Damian Legawiec06e195c1dc26
diff --git a/docs/developer/core-concepts/payments.mdx b/docs/developer/core-concepts/payments.mdx
index c3f238aaff..c86f0bc61b 100644
--- a/docs/developer/core-concepts/payments.mdx
+++ b/docs/developer/core-concepts/payments.mdx
@@ -55,9 +55,7 @@ Here's the list of attributes for the `Spree::Payment` model:
## Payment Methods
-Payment methods represent the different options a customer has for making a payment. Most sites will accept credit card payments through a payment gateway, but there are other options. Spree also comes with built-in support for a Check payment, which can be used to represent any offline payment.
-
-There are also third-party extensions that provide support for some other interesting options such as [Spree Braintree Vzero](https://github.com/spree-contrib/spree_braintree_vzero) for Braintree & PayPal payment methods.
+Payment methods represent the different options a customer has for making a payment. Most sites will accept credit card payments through a payment gateway, but there are other options. Spree also comes with built-in support for a Check payment, which can be used to represent any offline payment. Gateway providers such as Stripe, Braintree, and PayPal provide a wide range of payment methods, including credit cards, bank transfers, buy-now-pay-later, and digital wallets (Apple Pay, Google Pay, etc.).
A `PaymentMethod` can have the following attributes:
@@ -71,7 +69,7 @@ A `PaymentMethod` can have the following attributes:
| `position` | The position of the payment method in lists. Lower numbers appear first. | `1` |
<Info>
-You can decide which Payment Method will appear on which Store. This allows you to create different experiences for your customers in different countries.
+Each payment method is associated to a Store, so you can decide which Payment Method will appear on which Store. This allows you to create different experiences for your customers in different countries.
</Info>
## Payment Processing
@@ -167,10 +165,18 @@ payment.log_entries.first.details
## Supported Gateways
-Access to a number of payment gateways is handled with the usage of the [Spree Gateway](https://github.com/spree/spree_gateway) extension. This extension currently supports the following gateways:
+Spree team maintains several payment gateways integrations, including:
+
+* [Spree Stripe](https://github.com/spree/spree_stripe) - Stripe integration, supports all Stripe payment methods, including credit cards, bank transfers, Apple Pay, Google Pay, Klarna, Afterpay, and more. Also supports quick checkout.
+* [Spree PayPal](https://github.com/spree/spree_paypal) - native PayPal integration, supports PayPal, PayPal Credit, and PayPal Pay Later.
+
+<Info>
+ Spree Stripe and Spree PayPal are fully PCI compliant, meaning no sensitive data is stored or processed through Spree.
+</Info>
+
+There are also community-maintained extensions for other payment gateways, such as [Spree Gateway](https://github.com/spree/spree_gateway) extension. This extension currently supports the following gateways:
* Authorize.net
-* Apple Pay via Stripe
* BanWire
* Bambora previously Beanstream
* Braintree
@@ -188,7 +194,6 @@ Access to a number of payment gateways is handled with the usage of the [Spree G
* sage Pay
* SecurePay
* Spreedly
-* Stripe with Stripe Elements
* USAePay
* Worldpay previously Cardsave
@@ -217,10 +222,6 @@ Rails.application.config.after_initialize do
end
```
-<Info>
-[Spree Braintree Vzero](https://github.com/spree-contrib/spree_braintree_vzero) is a good example of a standalone custom gateway.
-</Info>
-
## Payment Method visibility
We've mentioned before that a `PaymentMethod` can have a `display_on` attribute. This attribute can have the following values: `front`, `back`, or `both`. For more granular control which Payment Methods should be available in which Store, you can override the `available_for_store?` method in your `PaymentMethod` subclass.