ZENITHPAY MASTER — PWT + DVA
Version 1.0.0 | Reviewed 19 October 2026

IMPORT THESE TWO FILES INTO POSTMAN:
1. ZenithPay-Master-PWT-DVA.postman_collection.json
2. ZenithPay-Private-Template.postman_environment.json

Select the private environment. Fill apiToken with the existing merchant Developer token. The environment contains no live token, BVN, customer email or account details. Fill only the variables for the request you intend to send. Web login does not issue this Developer token.

REQUESTS:
- Assign Dedicated Virtual Account
- Initialize Pay With Transfer
- Query PWT Payment Status
- Read PWT Callback Diagnostics
- Manual PWT Callback Retry (disabled by default)

READ THE GUIDE:
Open ZenithPay-PWT-DVA-Integration-Guide.html in a browser. The text version contains the same information. It includes complete DVA and PWT setup, required fields, naming, response handling, callbacks, signature verification, duplicate handling, uncertainty/retry guidance, troubleshooting and the D+1 06:00 Africa/Lagos settlement policy supplied by ZenithPay.

EXAMPLES AND PHP:
examples/ contains anonymized DVA and illustrative PWT JSON callbacks. They are reference data, not requests to replay into production. verify-zenithpay-callback.php authenticates a raw callback only; the merchant must supply its own validation, durable reference deduplication, atomic business credit and acknowledgement handling. ZENITHPAY_WEBHOOK_SECRET is a private variable name; its value must match the existing merchant Developer signing token.

USE INDIVIDUAL REQUESTS:
Do not blindly run the whole collection against production. DVA assignment and PWT initialization can create real provider accounts. PWT status may contact the provider. Manual retry sends a real callback after deliberate enablement; it must not be used to test duplicate credit against live data. This bundle contains no provider-notify simulation, settlement execution or payout request.

This downloadable bundle does not publish website changes or modify a remote Postman workspace. API endpoints and existing live merchant behavior are preserved.

VALIDATION:
161 offline checks passed, including the official Postman schema, actual Collection SDK request objects, JavaScript scenarios, retained DVA request rules and PHP HMAC positive/negative cases. No live financial requests were sent. See VALIDATION.json.
