SourCherry Help Centre
HomePaymentsGetting Started w/ Payments

How to Manage Stripe Payment Methods inside SourCherry

Now you can manage your Stripe payment methods entirely within SourCherry, no need to switch back and forth between dashboards! Simplify your payment setup across invoices, funnels, stores, and more while ensuring greater control and flexibility for your business.


TABLE OF CONTENTS


What is Stripe Payment Method Management?


Stripe Payment Method Management allows you to configure which payment options (like credit cards, wallets, bank debits) are available across various SourCherry product areas, directly inside your SourCherry account. This eliminates the need to manage payment methods separately on Stripe’s dashboard, streamlining operations and improving payment setup control.


Key Benefits of Stripe Payment Method Management


Understanding how managing Stripe payment methods directly in SourCherry benefits your business helps you make the most out of this feature.



How To Manage Stripe Payment Methods


Effectively setting up your Stripe payment options ensures smooth transactions across all your product areas. Follow these easy steps to start managing them directly within SourCherry:


Step 1: Navigate to Payments Settings


  1. Click on the Payments tab from your sub-account.



  2. Click on Integrations.



  3. Click the Manage button next to your connected Stripe account.



Step 2: Enable/Disable Payment Methods


  1. Click on the Manage Payment Methods option.



  2. You’ll see a list of payment methods available for different product areas.

  3. Toggle on or off based on which payment methods you want available for a particular product area.



  4. If you’re offering subscription products, you’ll see a special drop-down called Subscriptions. Configure payment methods specifically for subscription checkouts here.


Advanced Payment Method Setup & Troubleshooting

Some payment methods require additional configuration before they become available at checkout. Availability depends on factors such as account verification status, country support, payment method eligibility, and whether you are using Test or Live Mode.

Enabling Digital Wallets

Digital wallet payment methods can provide a faster checkout experience for customers using supported devices and browsers.

Apple Pay

Before Apple Pay can appear during checkout:

To enable Apple Pay:


Google Pay

Google Pay availability depends on supported devices, browsers, and payment account eligibility.

To enable Google Pay:



Activating Bank-Based Payment Methods

Bank payment methods may require additional account verification before becoming available.

ACH Payments

ACH payments may only be available in supported regions and for eligible payment accounts.

To enable ACH:


iDEAL and SEPA

Regional payment methods such as iDEAL and SEPA may only appear when supported by your payment account and customer location.

To enable these methods:



Buy Now, Pay Later Payment Methods

Supported financing and installment payment options may require approval from the payment provider before activation.

Examples may include:

To enable available installment options:


Switching Between Test Mode and Live Mode


Payment methods can be configured independently for Test and Live environments.

When troubleshooting payment visibility:


Stripe Payment Method Settings for Different Product Areas


Managing Stripe payment methods across product areas ensures that your customer-facing interfaces only show relevant payment options. Here’s where your configurations apply:

SaaS Configurator-generated checkout links for SaaS subscriptions support card payments only.
  
Other payment methods may be available in Stripe or other SourCherry product areas, but they are excluded for SaaS subscription onboarding.


Each checkout will respect the settings you’ve configured — no more surprises for your customers at checkout!


Frequently Asked Questions


Q: What are the transaction fees for Stripe?

Stripe transaction fees vary depending on your country and the type of payment method used. Generally, Stripe charges a percentage of each transaction plus a fixed fee. Because pricing differs by region, you should always refer to Stripe’s official pricing page for the most accurate and up-to-date details.


Q: Why don’t I see the Subscriptions list in SourCherry?

The Subscriptions list only becomes available after you’ve added at least one subscription product in Live Mode within the respective sub-account. This requirement comes directly from Stripe.


Q: What happens if I already have payment methods configured in Stripe?

Your existing settings are preserved. Default payment methods for product areas or checkouts will match your original Stripe setup unless you update them inside SourCherry.


Q: Will Live and Test modes have separate settings?

Yes! You can configure payment methods independently for Live and Test environments, allowing full flexibility during development and production.


Q: Why don’t I see the Subscriptions dropdown?

The Subscriptions settings become available only after adding at least one subscription product in Live Mode in that sub-account, according to Stripe’s rules.


Q: Are these changes applied to all sub-accounts?

Each sub-account connected to Stripe needs to configure its payment methods individually under its Payments settings.


Q: The Checkout and PMC pages do not show BLIK, even though it is active in Stripe. How can I enable it?

BLIK will not appear in our current integration. Stripe determines which payment methods are shown at runtime based on the connected account’s Payment Method Configuration and the checkout context. BLIK is not supported in this flow because it requires immediate PaymentIntent confirmation at checkout, which is not compatible with our deferred payment flow. We do not have plans to change this setup right now, but we regularly review payment method coverage with Stripe to support current use cases.

Q: Why is a payment method enabled but not appearing at checkout?

Payment methods may be hidden due to account restrictions, unsupported checkout types, regional limitations, missing verification requirements, or because they are enabled only in Test Mode instead of Live Mode.