Introduction
- Confirm connectivity
- Test gateway routing
- Validate authorization
- Check secure data handling
The PayEdge test app helps you validate how an application works behind the PayEdge gateway before you expose it to consumers or move it into production. You can use it to test connectivity, request and response handling, authentication, routing, validation, tokenization, idempotency, and secure data handling in controlled, non-client-visible environments.
The app supports controlled end-to-end testing scenarios where you need a test client, credentials, users, certificates, and example request data before production deployment.
How to choose
The version you choose depends on what you need to validate. If you only need to confirm basic connectivity and request handling, start with V2. If you need to validate end-to-end PayEdge gateway behavior, including security and data protection services, use V3.
PayEdge test app V2
Use V2 when you need a lightweight way to confirm that your application can connect to PayEdge and exchange simple request and response data. V2 gives you one product-based test resource, /auth/products, where you can create or retrieve controlled product data in a non-client-visible development or User Acceptance Testing environment.
PayEdge test app V3
Use V3 when you need to test a fuller PayEdge integration flow. V3 helps you validate how your consumer API works with PayEdge security, routing, validation, tokenization, idempotency, encryption, and plugin behavior before consumer exposure.
Comparison table
| Feature | PayEdge test app V2 | PayEdge test app V3 |
|---|---|---|
| Best fit | Basic connectivity and request or response validation using simple product data. | End-to-end PayEdge gateway testing across security, routing, validation, tokenization, idempotency, encryption, and plugin behavior. |
| Primary function | Helps you confirm that your application can send requests, receive responses, and handle controlled product data before rollout. Supports connectivity, request and response handling, and application behavior validation. | Helps you confirm that your consumer API integrates correctly with PayEdge security, routing, and data protection services. Verifies consumer API integration with PayEdge security, routing, and data protection services. |
| Main resource type | Product data, including product identifier, name, price, category name, and quantity. | Payment-style test data, including account details, parties, addresses, country codes, currency codes, and headers such as Include-Request and Idempotency-Key. |
| Available operations | GET /auth/products and POST /auth/products. |
Health check, anonymous routing, authorization, request and response validation, tokenization, idempotent processing, signed request verification, secure data handling, and multi-plugin testing. |
| Environment coverage | Development and User Acceptance Testing. | Development, mock development, User Acceptance Testing, and Client Acceptance Testing. |
| Authentication and security testing | References J.P. Morgan OAuth security definitions, but exposed test flow focuses on product data. | Includes test paths for OAuth, mutual Transport Layer Security (mTLS), signed request verification, tokenization, and Secure Data Handling. |
| Use it when you want to... | Run a quick, simple integration test. | Prove that your application works across the PayEdge gateway services you’ll rely on in a real integration. |
What you can build
Use the PayEdge test app to create a safe, repeatable integration testing experience for teams that need to prove application readiness before production deployment.
A pre-production integration smoke test
Confirm your app can connect to PayEdge, send a request, and process the response without using live client-facing flows.
A gateway readiness checklist
Help your team validate routing, authorization, validation, tokenization, idempotency, and secure data handling before release.
An example consumer journey
Walk a test user through the major PayEdge gateway behaviors using controlled request payloads and known response patterns.
A regression test pack
Create a regression test pack that your team can run after gateway, certificate, credential, or application changes.
A developer onboarding flow
Give new internal teams a safe, realistic way to learn how PayEdge request patterns work before they integrate with production APIs.
A certification support flow
Help implementation teams confirm that test clients, users, certificates, and credentials work before an application moves to the next environment.