Environments & Identifiers
This guide covers the NetValve API environments, how to identify your merchant account in API requests, and webhook source IPs for allowlisting.
API Environments
NetValve provides two environments:
| Environment | Base URL |
|---|---|
| Sandbox / UAT | https://payment-api.uat.sandbox-netvalve.com |
| Production | https://api.netvalve.com |
All API endpoints documented in this site are available in both environments. Use the sandbox for development and testing, and production for live transactions.
Never use real card numbers in the sandbox environment. Always use test cards.
Hosted Payment Page URLs
| Environment | Base URL |
|---|---|
| Sandbox / UAT | https://hpp-api.uat.sandbox-netvalve.com |
| Production | https://hpp-api.netvalve.com |
Merchant Identifiers
Every API request that initiates a payment (Sale, Authorize, etc.) must include a merchant identifier so NetValve knows which merchant account to process the transaction against. There are three identifier types — you only need to send one per request.
netvalveMidId
A UUID assigned to your merchant account during onboarding (e.g. 289e253d-f955-4e29-a2c7-bb1805883ee0). This identified the actual merchant account.
"netvalveMidId": "289e253d-f955-4e29-a2c7-bb1805883ee0"
siteId
A UUID that represents a site configured for Smart Routing. A site can have routing rules that direct transactions to different MIDs based on currency, country, card type, or BIN range.
"siteId": "0b81bdb1-d33b-48aa-8c48-a38f5cffd558"
When siteId is provided, do not include netvalveMidId in the same request. If either is present, the transaction is sent directly to that MID and smart routing is bypassed.
Which identifier should I use?
| Scenario | Use |
|---|---|
| Single MID, no routing rules needed | netvalveMidId |
| Multiple MIDs with routing rules | siteId |
| Testing in sandbox | Use whichever identifier the NetValve team provided during onboarding |
If a siteId is used but no routing rule matches the transaction, the default routing rule for that site is applied. If no default rule exists, the request fails with GTW_2000 ("Invalid Merchant ID").
Webhook Source IPs
If you restrict inbound traffic to your webhook endpoint by IP, allowlist the following addresses. See Webhook Message for full webhook documentation.
Production
| IP Address |
|---|
3.83.196.158, 54.145.109.123, 54.243.241.7, 3.209.90.9 |
Sandbox / UAT
| IP Address |
|---|
3.219.158.215, 52.87.147.83, 52.71.238.176, 34.230.183.29 |
General Notes
- No IP whitelisting required — your servers do not need to be allowlisted to call NetValve APIs.
- No rate limits — there are currently no rate limits on API endpoints. Standard security protections are in place.
- Backward compatibility — future API releases are backward compatible and should not require integration changes.
- All currencies supported — NetValve supports all currencies. Your payment request is forwarded to the card network and issuing bank for processing. Settlement currency depends on the processing bank.