When you connect to more than one gateway on the Integrations page, you will be required to define a default gateway for processing payments. This is necessary since more than one gateway is eligible to process payments and would require a default choice. In this article we will overview default gateways and payment integrations.
Specify the default gateway for order forms and invoices in case multiple payment gateways are connected
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.
Paypal and Stripe
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
Why don't I see Paypal among the default gateway options?
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.
Authorize.Net
If Authorize.net is connected and set as the default gateway, other product areas like memberships and SAAS payment links will continue to process payments using Stripe.
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.
NMI
Do I need to disconnect Stripe to connect to NMI?
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.
I have connected to NMI and have selected it as the default gateway. Will transactions across the application be processed through NMI now?
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.
Google Pay and Apple Pay
Can I use Stripe to offer Google Pay and Apple Pay and process credit card payments using NMI/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.
Notes:
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