Connect Payment Processor to Paywall
Learn how to connect payment processors to your paywalls to enable transaction processing and handle payments effectively.
Prerequisites: You must have at least one payment processor created before connecting it to a paywall.
Overview
Connecting payment processors to paywalls allows you to:
- Process transactions through multiple payment providers
- Distribute risk across different payment systems
Step 1: Access Payment Processor Manager
Navigate to your paywall settings and locate the “Payment Processor Manager” button. This is where you can manage which payment processors are connected to your specific paywall.
Step 2: Understanding Test vs Live Mode
The system automatically shows payment processors based on your paywall’s current mode:
| Paywall Mode | Available Processors | Usage |
|---|---|---|
| Test Mode | Only test payment processors | Development and testing |
| Live Mode | Only live payment processors | Production environment |
Important: Test payment processors connected will only be available when the paywall is in test mode. When you switch paywall to live mode, only live connected payment processors will be available for clients.
Step 3: Select Payment Processors
Choose which payment processors you want to connect to your paywall:
- Open the Payment Processor Manager modal
- Review available processors - You’ll see a list of all payment processors created in the current mode
- Select processors - Use checkboxes to select which ones to connect
- Review processor information:
- Name - Custom name you assigned
- Mode - Test or Live indicator
- Provider - Stripe, Paddle, etc.
Risk Distribution: You can select multiple payment processors. Transactions will be divided equally between the selected acquiring services to minimize risks.
Step 4: Save Configuration
After selecting your payment processors:
- Click “Save” to apply the configuration
- Wait for confirmation - The system will update the connections
Payment Processing Logic
When multiple payment processors are connected:
Load Distribution: Transactions are automatically distributed equally between all connected payment processors. This helps balance load and reduce dependency on a single provider.
Transaction Flow
- Customer initiates payment
- System selects processor - Automatically chooses from connected processors
- Payment processing - Transaction is handled by selected processor
- Confirmation - Payment success/failure is reported back
Removing Processors
To remove payment processors:
- Uncheck the processors you want to disconnect
- Save the configuration
- Removed processors will no longer process new transactions
Active Transactions: Removing a payment processor doesn’t affect ongoing transactions or existing subscriptions. Only new transactions will use the updated processor list.
Troubleshooting
No payment processors available
Possible causes:
- No payment processors created in the current mode
- All processors are in different mode (test vs live)
- Processors are not properly configured
Solution:
- Create payment processors in the correct mode
- Verify processor configuration
- Check processor status in the main dashboard
Cannot select a processor
Possible causes:
- Processor is marked as unavailable
- Shared processor with restricted access
- Processor configuration issues
Solution:
- Contact support for shared processors
- Verify processor configuration
- Check processor credentials and webhook setup
Payments not processing
Possible causes:
- No processors connected to paywall
- Configuration errors in payment processors
Solution:
- Ensure at least one processor is connected
- Verify processor status and credentials
- Review processor logs for errors
Best Practices
Redundancy and Reliability
- Multiple Processors - Connect at least 2 payment processors for redundancy
- Different Providers - Use different payment systems (e.g., Stripe + Paddle)
- Monitor Performance - Track success rates for each processor
Next Steps
After connecting payment processors to your paywall:
API Reference
For programmatic management of payment processor connections, see: