For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Log in to the PayOS Dashboard
GuidesAPI ReferenceHelp Center
GuidesAPI ReferenceHelp Center
  • Getting Started
    • Introduction to PayOS
    • Account Setup
    • Authentication
  • Core Concepts
    • Webhooks
    • Merchant Location
      • Environment Rules
      • Exception Rules
  • Integration Guides
    • Hosted Checkout
    • Secure Fields (BETA)
    • Direct API Integration
  • Advanced Features
    • Recurring Payments (BETA)
    • Fraud Prevention (BETA)
    • Mobile Number Verification
  • Best Practices
    • Security Best Practices
    • Error Handling
    • Rate Limiting
Log in to the PayOS Dashboard
LogoLogo
On this page
  • Overview
  • Importance of Environment Rules
  • How to Configure Environment Rules
Core ConceptsPayment Rules

Environment Rules

Configuring Environment-Specific Payment Rules

Was this page helpful?
Edit this page
Previous

Exception Rules

Handling Exceptions in Payment Processing
Next
Built with

Overview

Environment rules in PayOS are integral to the foundational setup of a merchant’s account. They are part of the overall configuration process and determine your environment’s default routing behavior.

These settings encompass things like the specific processors which are enabled and configured with working credentials, which payment methods are allowed, and which processors should be the default for specific payment methods in a given market or geographical location.

Importance of Environment Rules

  1. Default Processor Configuration: During the onboarding process, merchants are required to define a default processor for each payment method enabled in a specific region. This ensures that transactions are processed efficiently and according to the merchant’s preferences.

  2. Fallback Processor Options: Merchants can also configure optional fallback processors. These processors will be used if the default processor is unavailable or fails to process a transaction. This flexibility helps maintain a seamless payment experience for users.

  3. Processor and Payment Method Management: These configurations specify which processors are active and which payment methods are available, allowing merchants to tailor their offerings to meet market demands and regulatory requirements.

  4. Transaction Routing: In the absence of exception rules, these configurations guide the routing of transactions, determining the available options for users and ensuring the desired payment processing paths are followed.

How to Configure Environment Rules

Environment rules are configured on your merchant dashboard, providing a user-friendly interface to manage these essential settings. Merchants are supported through our white-glove solutions engineering approach, ensuring that the setup process is smooth and tailored to their specific needs.

  1. Define Default and Fallback Processors: As a merchant configures their payment methods within a location, they should configure at least a default payment processor and can also configure secondary (fallback) processors. This is effectively a rule that ensures a primary processor is always available for each payment method.

  2. Set Default Processors: Assign default processors for specific payment methods based on market or geographical location, ensuring that transactions are processed efficiently.

  3. Testing and Validation: Regularly test and validate the environment settings to ensure they align with business objectives and regulatory standards.