Defining a default gateway becomes essential when you integrate multiple payment gateways through our platform. The default gateway acts as the primary choice for processing payments across various areas of your business, ensuring a streamlined transaction flow. Setting the default gateway simplifies the payment process, avoiding ambiguity and ensuring your transactions are processed seamlessly. This article delves into the world of default gateways, clarifying their role in payment integrations and highlighting crucial updates to empower your transactions.
Specify the default gateway for order forms and invoices in case multiple payment gateways are connected
Access Integrations: Navigate to the Payments > Integrations section within your account settings.
Select Your Preferred Gateway: Choose your desired payment gateway (Stripe, Authorize.net, or NMI) based on your business needs.
Confirm Default Status: When adding a new gateway, you'll be prompted to set it as your Default Payment Gateway.
Clicking 'Cancel' integrates the gateway without making it the default.
Clicking 'Confirm' integrates the gateway and designates it as the Default Payment Gateway.
Please Note: One default choice must be made.
When saving a new gateway it will show you a quick prompt asking whether you want to make the gateway your Default Payment Gateway.
Clicking on Cancel will still integrate the gateway but will not make it the Default Gateway.
Clicking on Confirm will integrate the gateway and make it the Default Payment Gateway.
Our recent enhancements bring two more membership-focused gateways into play:
Stripe: Your trusted payment partner, ensuring secure transactions and streamlined payment processing.
NMI: Empowering diversity in payment options, seamlessly integrating with invoices, text2pay links, and order form payments.
Authorize.net: A robust gateway choice for memberships, providing reliability and efficiency in transaction processing.
You are not required to disconnect Stripe to connect to other integrations. You can connect to multiple gateways on the integrations page. However, since you have connected to different gateways for processing payments, you will need to define a default gateway for processing payments. PayPal will continue to function alongside Stripe/Authorize.net/NMI in order forms, whichever is set as the default
You can connect both PayPal and Stripe simultaneously, utilizing them independently or together.
Define the default choice
Existing subscriptions running through Stripe or PayPal will continue as usual until changes are made.
You can connect to Paypal and use it as a payment method alongside a credit card payment method using Stripe/Authorize.net/NMI. This means that the default must be chosen among Stripe/Authorize.net/NMI when connected. PayPal can be used independently and alongside credit card payment methods on order forms.
If there are recurring subscriptions/pending transactions with Stripe, they will continue to run as is until the Stripe connection is in place. We encourage you not to disconnect any gateway. Defining the default gateway will run new transactions through the desired choice and keep the existing subscriptions running through Stripe and PayPal integrations in place.
Ensure existing subscriptions through Stripe and PayPal remain functional. New transactions will align with the default gateway choice.
If Authorize.net is your default gateway, areas like memberships and SAAS payment links will use it for processing payments.
No, You are not required to disconnect Stripe to connect to NMI. You can connect multiple gateways on the integrations page. However, since you have connected multiple gateways for processing payments, you must define a default gateway for processing order form payments.
Connect NMI without disconnecting Stripe. Both can coexist for diverse payment options.
NMI integrates seamlessly with invoices, text2pay links, and order form payments.
Ongoing subscriptions with Stripe, PayPal, or Authorize.net will persist. Defining a default gateway affects new transactions, preserving existing subscriptions.
The NMI integration is available only for invoices, text2pay links, and order form payments. This means that if NMI is connected and is set as the default gateway, only these payments will be processed through NMI. Other payment areas like calendars, SaaS, or memberships will continue to process payments using Stripe.
Please Note: If there are any recurring subscriptions/pending transactions with Stripe, they will continue to run as is till the time the Stripe connection is in place. We encourage you to keep the connections in place and not disconnect any gateway, defining the default gateway will run new transactions through the desired choice and will keep in place the existing subscriptions running through Stripe, PayPal, and Authorize.net.
Unfortunately, this cannot be the case. Google Pay and Apple Pay can be provided using Stripe only for now, and only one gateway has to have defaulted for order form payments among Stripe, Authorize.net, or NMI. So using both simultaneously is not possible.
Currently, only Stripe supports Google Pay and Apple Pay functionalities.
Choose a single default gateway among Stripe, Authorize.net, or NMI for order form payments, ensuring a smooth customer experience.
For ongoing subscriptions, maintaining existing connections is crucial. Changing gateways impacts new transactions, not existing subscriptions.
Custom values and If/Else filters in workflows offer flexibility when working with different payment gateways, enhancing your automation capabilities.
Please Note: If the business disconnected the gateway account and there is an ongoing subscription, the transaction cannot be processed, and hence the subscription will move to unpaid. The retry attempts will continue according to the retry logic.
Note: Custom Values and If/Else filters exist for payment gateway within workflows when using the Order Submitted trigger
