Environments & Hosts
DogPay provides functionally isolated Sandbox and Production environments. Merchants should complete integration, development, and debugging in Sandbox to ensure business logic closure before switching to Production for live operations.
Environment Isolation
DogPay Sandbox is independent development tool. Simulate entire payment flows, fund transfers, and webhook callbacks within Sandbox. API logic in Sandbox remains consistent with Production, but transactions generated in Sandbox carry no real legal or financial effect.
Web Management Dashboard
Merchants configure API keys, view billing details, and manage webhook destination URLs via management dashboard.
| Environment | Host URL |
|---|---|
| Sandbox | https://sandbox.dogpay.com |
| Production | https://dogpay.com |
API Base URL
All API requests must point to corresponding base address. Ensure BASE_URL settings in SDK or code configuration files match current testing phase.
| Environment | API Host |
|---|---|
| Sandbox | https://sandbox-api-v2.dogpay.com |
| Production | https://api.dogpay.com |
Environment Switch WarningAuthentication credentials (API Key and API Secret) for Production and Sandbox are entirely independent. When pushing system to production phase, strictly update Base URL and corresponding credentials to prevent requests from being blocked due to authentication failure。
Functional Differences
Sandbox Environment
Usage: Development debugging, simulating webhook callbacks, and exception flow testing.
Assets: Uses test tokens for simulated payments; involves no real fund movement.
Risk Control: Risk policies operate in relaxed mode, primarily used to verify business logic integrity.
Production Environment
Usage: Official business launch for processing real transactions.
Assets: Involves real settlement of fiat and cryptocurrency.
Risk Control: Enables real-time KYT (Know Your Transaction) risk screening capabilities.
Updated about 4 hours ago