Production readiness depends on a correct and consistent environment configuration, ensuring that all interactions with SIBS Payment Gateway (SPG) execute against the intended infrastructure, with valid credentials and predictable behavior.

Misconfiguration at this level is a primary source of integration failures, often resulting in rejected transactions, inconsistent processing, or incorrect system behavior.

Environment Separation

SPG integrations operate across distinct environments (e.g., Sandbox and Production), each with its own configuration, credentials, and operational characteristics.

A production-ready system must enforce strict separation between environments by:

• Ensuring that production deployments use only production endpoints and credentials
• Preventing any reuse of Sandbox configuration in production
• Isolating environment-specific variables at configuration and deployment levels

Environment separation must be explicit and verifiable, eliminating any ambiguity about where transactions are being executed.

Endpoint and Connectivity Validation

All API interactions must be configured with the correct production endpoints.

This includes:

• Base API URLs for all SPG operations
• Webhook endpoints exposed by the merchant system
• Redirect URLs where applicable

Before go-live, it must be validated that:

• All endpoints point to production infrastructure
• Webhook endpoints are reachable from SPG
• Network communication is stable, secured over HTTPS, and capable of handling production latency and timeout conditions.

Incorrect endpoint configuration may result in:

• Failed or unreachable API calls
• Webhook delivery failures
• Incomplete transaction flows

See E.1 Webhooks (Notifications) for webhook delivery behavior and processing requirements.

Credential and Access Configuration

Production integrations require valid, environment-specific credentials, including:

• <AuthToken>
• X-IBM-Client-Id
• terminalId

These must be:

• Correctly provisioned for production use
• Securely stored and managed
• Never reused across environments

Any inconsistency or misuse of credentials will lead to request rejection at API level or authorization failures.

Configuration Consistency Across Components

All components participating in the integration must operate under a consistent configuration.

This includes:

• Backend services interacting with SPG APIs
• Webhook processing endpoints
• Any frontend or redirect-based components

Consistency must be ensured for:

• Transaction identifiers (e.g., merchantTransactionId)
• Currency and amount handling
• Timestamp generation (ISO 8601 UTC)

Misalignment between components may result in:

• Invalid or rejected requests
• Inconsistent transaction state handling
• Reconciliation discrepancies

See C.2 Field Semantics and Validation Rules for field-level constraints and validation requirements.

Environment-Specific Behavior Awareness

Sandbox and Production environments do not behave identically.

Sandbox environments:

• Simulate transaction processing
• May not fully reflect real-world timing or external dependencies

Production environments:

• Involve real payment processing
• Depend on user interaction and external systems
• Exhibit variable timing and asynchronous behavior

A production-ready integration must account for these differences and avoid assumptions based solely on Sandbox behavior.

The impact of asynchronous and delayed outcomes is further detailed in F.3 Success and Error Scenarios and illustrated in F.1 End-to-End Integration Examples.

Pre-Go-Live Validation

Before promoting the integration to production, the following must be verified:

• All endpoints are correctly configured for production
• Credentials are valid and operational
• Webhook endpoints are reachable and responsive
• Network connectivity is stable
• Configuration is consistent across all components

Validation must confirm that the system can execute and sustain the full transaction lifecycle under production conditions.

Final Consideration

Environment and configuration readiness is a prerequisite for all other production guarantees.

Even a correctly implemented integration will fail if:

• It targets the wrong environment
• It uses invalid or inconsistent credentials
• It operates under incorrect configuration assumptions

A production-ready system ensures that all configuration elements are explicit, validated, and environment-specific, eliminating ambiguity before any transaction is executed.