Initial Setup in Postman

To begin testing, you must import the official GPAS test assets and configure your target environment.

1. Import Assets

Download and import the following files into your Postman workspace:

ARCHIVO	VERSION	DATE	DESCRIPTION
GPAS_Wallet_Integration.postman_collection	2.0.1	2026-02-05	Main logic for Sessions, Balances, and Transactions.
GPAS_Wallet_Integration.postman_environment	2.0.1	2026-02-05	Template for staging and production variables.
GPAS_Wallet_Integration.postman_globals	2.0.1	2026-02-05	Global configuration required for all test suites.

Steps:

1. Open Postman.
2. Click Import (top left).
3. Drag and drop the three files at once.
4. Ensure the items appear in your “Collections” and “Environments” tabs.

2. Configure Environment Variables

Select the imported environment and populate the following critical variables with your local or staging credentials:

Variable	Description	Requirement
{{baseUrl}}	The gateway/destination URL of your API.	Example: https://qa-api.yourwallet.com
{{walletId}}	The unique identifier of the wallet to be tested.	Unique per operator.
{{authToken}}	The initial token provided by the launcher (AuthToken).	Used in the /sessions call.
{{secretKey}}	The secret credential used for SHA1 signature generation.	Keep this secure! Never share it.
{{parentSystemId}}	The GPAS identifier in your system (x-parent-system-id).	Provided by the GPAS team.

Tip

Make sure there are no leading or trailing spaces in your variable values, especially in the secretKey, as this will cause signature verification failures.

3. Dynamic Variables

Some variables in the collection (like {{walletSessionId}} or {{externalReference}}) are automatically updated by Postman scripts during the test execution flow. You do not need to configure these manually.