Environments

Development environments help separate application testing from live operations.

When integrating with Senmo infrastructure, always use the environment and credentials provisioned for your specific product.

Environment types

Depending on the platform and its deployment configuration, the following environment classifications may be used.

The availability of each environment is product-specific. Not every platform necessarily provides all four.

Production

Production environments are intended for live workloads.

Operations performed in production may affect actual financial records, digital assets, vouchers, or connected external systems.

Before using production:

• Verify your application's authentication and authorization controls.
• Confirm the correct API base URL and credentials.
• Validate request handling and error management.
• Review transaction safety and duplicate-prevention mechanisms.
• Establish monitoring and operational procedures.

Non-production environments

Non-production environments allow developers to validate integrations without intentionally affecting live operations.

Depending on the product, these environments may use simulated data, isolated infrastructure, or connected testing services.

Do not assume that non-production environments reproduce every production behavior.

Environment configuration

Store environment-specific settings separately from application code.

For example:

PLATFORM_ENVIRONMENT=sandbox
PLATFORM_API_BASE_URL=<documented-base-url>
PLATFORM_API_CREDENTIAL=<environment-specific-credential>

These are illustrative application variables, not required Senmo configuration names.

Environment isolation

Never assume that resources or credentials created in one environment are available in another.

Your application should maintain clear separation between:

• API credentials.
• Base URLs.
• Resource identifiers.
• Test data.
• Logs and monitoring.
• Integration configurations.

Moving to production

Before production deployment, verify that the integration uses the correct environment and that all required operational checks have been completed.

Consult the relevant product documentation for actual environment availability, access procedures, and production-readiness requirements.