Environments and testing
Validate behavior before using production credentials.
Environment configuration
Confirmed sandbox and production base URLs, access requirements, and test fixtures are pending publication. Obtain these values from KPPAY before running an integration.
Keep environment URLs and credentials in configuration rather than scattering them throughout application code.
Test scenarios
| Scenario | What to verify |
|---|---|
| Valid request | Required fields, response schema, and stored result |
| Invalid input | Useful validation errors and no unintended side effects |
| Rejected credentials | Safe error handling without exposing secrets |
| Network timeout | An explicit recovery path for an unknown outcome |
| Duplicate submission | Behavior matches the documented duplicate-request policy |
| Repeated event | Processing does not repeat a business action |
Safe test data
Use approved synthetic fixtures. Do not copy production credentials or personal data into local test files.
Before switching environments
Confirm that all endpoint URLs, credentials, event destinations, and data stores point to the intended environment. Review the go-live checklist.