Platforms and Environments
Country coverage, base URLs, and sandbox versus live behavior across Payments API and WAPIs
Both WiPay API products use the same country-based live and sandbox host pattern. The product difference is the path you append to the selected base URL.
Base URLs
Select the live or sandbox base URL for the country and environment you are targeting.
| Country | Code | Live Base URL | Sandbox Base URL |
|---|---|---|---|
| Barbados | BB | https://bb.wipayfinancial.com | https://bbsb.wipayfinancial.com |
| Grenada | GD | https://gd.wipayfinancial.com | https://gdsb.wipayfinancial.com |
| Guyana | GY | https://gy.wipayfinancial.com | https://gysb.wipayfinancial.com |
| Jamaica | JM | https://jm.wipayfinancial.com | https://jmsb.wipayfinancial.com |
| Trinidad & Tobago | TT | https://tt.wipayfinancial.com | https://ttsb.wipayfinancial.com |
Product Paths
After selecting the correct live or sandbox base URL, append the product path.
| Product | Path Pattern | Example |
|---|---|---|
| Payments API | /plugins/payments/request | https://ttsb.wipayfinancial.com/plugins/payments/request |
| WAPIs | /wapi/{resource-path} | https://ttsb.wipayfinancial.com/wapi/auth/tokens |
Payments API Routing
- Full endpoint pattern:
{base_url}/plugins/payments/request - Example live TT endpoint:
https://tt.wipayfinancial.com/plugins/payments/request - Example sandbox TT endpoint:
https://ttsb.wipayfinancial.com/plugins/payments/request - The Payments API still uses the
environmentrequest parameter as part of the request payload.
WAPI Routing
- Full endpoint pattern:
{base_url}/wapi/{resource-path} - Example live TT base path:
https://tt.wipayfinancial.com/wapi - Example sandbox TT base path:
https://ttsb.wipayfinancial.com/wapi
Sandbox Credentials and Behavior
Payments API
- Use
environment=sandboxfor test transactions. - Use the sandbox
account_number1234567890. - Use the sandbox API Key
123only for server-side hash verification. - The public sandbox account does not provide merchant-specific reporting or transaction history. Sandbox payments do not send automated payer or payee emails.
WAPIs
- Use the sandbox base URL for the target country.
- Authenticate with credentials valid for an account on the selected sandbox platform. A live account or credential does not automatically provide sandbox access.
- WAPI Keys use the
wapi_live_...prefix for live and thewapi_test_...prefix for sandbox. - Some endpoints, especially account-management flows, may depend on a provisioned WAPI Configuration.
Account ownership and verification
The public Payments API sandbox account 1234567890 is shared; transactions
created under it do not belong to your live merchant account. The public hash
key 123 is not a WAPI credential or a webhook signing secret.
Retrieve Transaction requires credentials for the account that owns the transaction. Adding a transaction scope to another account's token or key does not grant access to shared-account transactions.
Webhook endpoints receive events for their own merchant account on the platform where they are registered. An endpoint on your live account does not receive payment events for the shared sandbox account.
For merchant-scoped Retrieve and webhook testing, contact WiPay to confirm a suitable sandbox account and credentials. Do not substitute your live account number into the public sandbox setup unless WiPay has confirmed the appropriate test configuration.