Environments & Setup
Environments & Setup
Base Hosts
Each API is called against its own host. In this collection, both hosts are represented as environment variables rather than hardcoded URLs, so you can point them at sandbox or production without editing individual requests.
All endpoint paths are appended to these hosts, e.g. in sandbox/staging:
Production hosts aren’t published in this collection — use whatever host is assigned to you for production, and keep it separate from the sandbox/staging values above.
Token Environment Variables
Both APIs automatically populate an environment variable with the bearer token once you successfully authenticate, so you don’t need to manually copy/paste tokens between requests.
This is handled by a post-response script attached to each token endpoint: on a successful response, it reads data.token from the JSON body and saves it to the environment automatically.
Other Variables Used
Sandbox/Staging Test Credentials
For trying out the Payments API in sandbox/staging, the collection ships with these test credentials:
The Disbursement API’s Create Access Token request also uses the same test-merchant / p@ssw0rd01 pair as its example body, so both APIs can be exercised end-to-end in sandbox with one set of credentials.
These are shared sandbox/staging credentials meant for trying out the collection. Use your own assigned production credentials before going live.
Minimum Setup Checklist
Set your hosts
Set payments_api_host and/or disbursement_api_host in your environment (sandbox or production, as assigned to you).
Authenticate
Call the relevant token endpoint (Create Token for Payments, Create Access Token for Disbursement).