Getting started with PayEdge integration testing

Before you use the PayEdge test app, make sure you have the right internal setup.

1. Confirm which version you need: V2 for simple product-data testing or V3 for broader PayEdge gateway testing.
2. Confirm your target environment. V2 supports development and User Acceptance Testing servers. V3 supports development, mock development, User Acceptance Testing, and Client Acceptance Testing servers.
3. Get the required test client, credentials, users, and certificates through your internal onboarding process.
4. Use test data only. This app is for internal testing and controlled integration flows.
5. Confirm the expected authentication pattern for your test scenario, especially if you’re testing OAuth, mutual Transport Layer Security (mTLS), signed request verification, or secure data handling.

Suggested sample user journey

Use this example journey to move through the test app from basic readiness to broader gateway validation.

1. Start with GET /health in V3 to confirm that the test app is available.
2. Use V2 POST /auth/products and GET /auth/products if you only need a simple connectivity check.
3. Move to V3 POST /routing/anonymous to validate gateway routing.
4. Use V3 /auth operations to validate authorization behavior.
5. Use /auth/request-response-validator to confirm request and response contract behavior.
6. Use /auth/tokenization, /auth/secure-data, and /auth/idempotent-processing to validate the gateway services your integration depends on.
7. Use the combined secure data handling endpoints or multiple plugin endpoints when you need a more complete end-to-end test.