Postman collection

Developer tools

Every Paga Engine request, ready to send. Hashes, references and base URLs are handled for you, so you can try any use case in minutes.

Get the collection

Fork it into your workspace

Your fork is your own copy, with your own keys. When Paga updates the collection, Postman lets you pull the changes into your fork.

Run in Postman

One collection covers Sandbox and Live. There are no separate environments to import. You’ll need a free Postman account to fork it.

One file covers Sandbox and Live. There are no separate environments to import.

Set it up

Open the collection’s Variables tab

Select Paga Engine API in Postman’s sidebar, then Variables.

Add your Sandbox keys

Enter sandboxPublicKey, sandboxSecretKey and sandboxHashKey in the Current value column, then save. Find them in your Sandbox business portal; see Get your API keys.

Send any request

mode is sandbox to start with. The base URL, the hash header and a fresh referenceNumber are set for you.

🚧
Keys go in Current value only
Current value stays on your computer. Initial value is shared with anyone who can see your workspace, and is included if you export the collection. Never share a workspace that contains Live keys.

What’s inside

11 folders

One per use case

From Checkout to Bill payment, with 55 requests numbered in the same order as the guides.

Automatic

Hashes and references

Each request signs itself from the values you send. Status checks reuse the reference from the step before.

Test callbacks

Signed callbacks to your server

The “Handle the …” requests send a correctly signed callback to yourServerBaseUrl, so you can test your handler.

Switching to Live

Add your Live keys to livePublicKey, liveSecretKey and liveHashKey, then change mode to live. Every request then uses the Live servers and your Live keys. Change it back to sandbox when you’re done; Postman’s console shows which one each request used.

All collection variables (11)

Variable	What it’s for
`mode`	`sandbox` (or `test`) or `live` (or `production`). Anything else stops the request
`sandboxPublicKey`, `sandboxSecretKey`, `sandboxHashKey`	Your Sandbox keys, from the Sandbox business portal
`livePublicKey`, `liveSecretKey`, `liveHashKey`	Your Live keys, from the Live business portal. Live keys work once your business is approved
`yourServerBaseUrl`	Optional. Where the test callbacks are sent
`lastReference`	Filled in automatically. Used by status checks
`lastPaymentRequestReference`	Filled in automatically. Used by Refunds
`subsidiaryAccount`	Filled in automatically by “Create an account”. Used by the other Subsidiary Accounts steps

If something doesn’t work

“Set sandboxPublicKey…”

A key is missing for the current mode. Add it in the Variables tab, in Current value, and save.

“mode is …”

mode has a value the collection doesn’t recognise. Set it to sandbox or live.

Invalid hash or 401

Check the keys match the mode, with no extra spaces. See Error handling.

Request blocked

Your IP address may not be whitelisted. See IP whitelisting.

Need help? We’re here 24/7

Talk to our support team any time, or ask questions in the developer community.

Email support Join us on Slack