Who This Is For / When to Use
This article is for Kyrios account owners who:
Have connected more than one payment gateway
Need to control which gateway processes new payments
Want to ensure existing subscriptions continue without interruption
What a Default Payment Gateway Is
A default payment gateway is the primary gateway Kyrios uses to process new payments when multiple gateways are connected.
Only one default gateway can be set at a time
The default applies to new transactions only
Existing subscriptions continue using their original gateway
A default gateway is required to prevent ambiguity when processing payments.
Where the Default Gateway Is Used
The default gateway determines which gateway processes payments for:
Order forms
Invoices
Other areas may continue using a specific gateway depending on feature limitations.
Supported Default Gateway Options
Only the following gateways can be set as the default:
Stripe
Authorize.net
NMI
PayPal cannot be selected as a default gateway.
How to Set a Default Payment Gateway
Step-by-Step
Go to Payments → Integrations in your Kyrios account
Add or connect a supported payment gateway
When prompted, choose whether to make it the default
Select Confirm to set it as the default gateway
Prompt Behavior
Confirm → Gateway is connected and set as default
Cancel → Gateway is connected but not set as default
Important: One default gateway must be selected when multiple gateways are connected.
Using Multiple Payment Gateways Together
Kyrios allows multiple gateways to be connected at the same time.
You do not need to disconnect an existing gateway
Defining a default affects new transactions only
Existing subscriptions remain unchanged
This ensures continuity for active customers while routing new payments correctly.
PayPal Behavior with Default Gateways
PayPal works alongside credit card gateways but has specific limitations.
PayPal cannot be set as the default gateway
The default must be Stripe, Authorize.net, or NMI
PayPal can still appear as a payment option on order forms
Existing PayPal subscriptions continue to run normally.
Stripe as a Default Gateway
When Stripe is set as the default gateway:
New order form and invoice payments use Stripe
Existing Stripe and PayPal subscriptions remain active
Stripe supports memberships, calendars, SaaS, and subscriptions
Stripe is currently required for Apple Pay and Google Pay.
Authorize.net as a Default Gateway
When Authorize.net is set as the default gateway:
New order form and invoice payments use Authorize.net
Membership payment links process through Authorize.net
Existing Stripe or PayPal subscriptions continue unchanged
Do not disconnect Stripe or PayPal if active subscriptions exist.
NMI as a Default Gateway
When NMI is set as the default gateway:
NMI processes payments for:
Invoices
Text2Pay links
Order forms
Other areas (calendars, SaaS, memberships) continue using Stripe
NMI does not replace Stripe for all payment features.
Google Pay and Apple Pay Limitations
Apple Pay and Google Pay have strict requirements.
Only Stripe supports Apple Pay and Google Pay
You cannot:
Use Stripe for Apple/Google Pay
AND use NMI or Authorize.net for credit cards at the same time
One default gateway must handle order form payments
Mixed gateway usage for these wallets is not supported.
Adyen Integration Overview
What Adyen Is
Adyen is an enterprise-grade payment provider commonly used in:
Europe
North America
It is ideal for international and high-risk transactions.
Key Capabilities
Credit and debit card payments
3DS card support for compliance
Strong coverage for enterprise clients
Changing gateways impacts new transactions only.
Important Notes About Subscriptions
Existing subscriptions always continue on their original gateway
Changing the default does not migrate subscriptions
Disconnecting a gateway with active subscriptions will cause:
Failed transactions
Subscriptions marked as unpaid
Retries based on retry logic
Do not disconnect gateways with active subscriptions.
Workflow Automation with Multiple Gateways
Kyrios supports automation logic for payment routing.
Custom Values and If/Else filters are available
Supported when using the Order Submitted workflow trigger
Enables gateway-based branching logic
This allows advanced payment automation without manual intervention.
FAQ
What is a default payment gateway?
A default payment gateway is the primary gateway Kyrios uses to process new payments when multiple gateways are connected.
How do I set a default payment gateway?
Go to Payments → Integrations, add or connect a gateway, and select Confirm when prompted to make it the default.
Can I connect multiple payment gateways at the same time?
Yes. You can connect Stripe, Authorize.net, NMI, and PayPal simultaneously, but one default gateway must be selected.
What happens if I don’t choose a default gateway?
Kyrios requires one default gateway when multiple gateways are connected. Without it, new payments cannot be routed correctly.
Can PayPal be my default gateway?
No. PayPal cannot be set as the default. The default must be Stripe, Authorize.net, or NMI.
Do I need to disconnect Stripe to use NMI or Authorize.net?
No. Gateways can coexist. Defining a default only affects new transactions.
What happens to existing subscriptions if I change the default gateway?
Existing subscriptions continue unchanged on their original gateway. Only new transactions use the new default.
What payments does NMI process when set as default?
NMI processes payments for invoices, Text2Pay links, and order forms only.
Can I use Apple Pay or Google Pay with NMI or Authorize.net?
No. Apple Pay and Google Pay are supported only through Stripe.
What happens if I disconnect a gateway with active subscriptions?
Payments will fail, subscriptions will move to unpaid, and retry attempts will continue based on retry logic.
How do workflows handle multiple payment gateways?
You can use Custom Values and If/Else filters in workflows with the Order Submitted trigger to route logic by gateway.