PayEdge test app V3 overview
Use the PayEdge test app V3 when you need to validate how your application works with PayEdge gateway services in a controlled, non-client-visible environment. V3 helps you test more advanced integration behavior, including authentication, routing, request and response validation, tokenization, idempotency, encryption, and plugin behavior before consumer exposure.
V3 gives you several test resources that support different gateway flows:
| Resource | What you use it for |
|---|---|
/health |
Check whether the V3 test app is available. |
/routing/anonymous |
Test Layer 7 routing through an anonymous routing path. |
/auth |
Test authorization-protected request flows using OAuth or mutual Transport Layer Security (mTLS). |
/auth/request-response-validator |
Validate requests and responses against the OpenAPI Specification contract. |
/auth/tokenization |
Test account number tokenization. |
/auth/idempotent-processing |
Test retry behavior using an idempotency key. |
/auth/secure-data |
Test encryption and decryption through secure data handling. |
/auth/uber-plugins |
Test multiple PayEdge plugins with Layer 7 authorization. |
V3 uses payment-style test data rather than simple product data. The request body can include account details and party information, such as:
primaryAccountDetailsaccountNumberaccountTypeaccountCurrencycompanyIdbasicPartynamepostalAddressdateAndPlaceOfBirthcountryOfResidence
You can also use optional headers for specific test flows. For example, the Include-Request header adds the request body into the response for a longer response, and the Idempotency-Key header helps test retry handling for endpoints that support idempotent processing.