Environments & Console

​

Overview

​

Thiqwave Console

• Onboarding — Complete KYB verification and get approved for live transactions
• KYB Verification — Submit and track compliance status for your business
• API Keys — Generate and manage API keys for staging and production
• Webhooks — Configure webhook endpoints and view delivery logs
• Transaction Monitoring — View all transactions, settlements, payouts, and on-chain operations
• Reports — Export transaction history and compliance reports
• Team Management — Manage team members and permissions

​

Staging Environment

• Test data only — no real funds involved
• Simulated payment rails — instant settlements and refunds
• Full API feature parity with production
• API keys scoped to staging environment only
• Test scenarios for different outcomes (success, failure, pending, compliance holds)

​

Test data

• Test business profiles — Pre-created partner accounts with completed KYB verification, so you can skip onboarding and start testing transactions right away
• Test accounts — Pre-configured fiat settlement accounts and stablecoin wallets with test balances across supported corridors

​

Getting started in staging

1. Sign in to the Console at dashboard.thiqwave.com
2. Navigate to Environments → Staging
3. Generate a staging API key
4. Use the base URL https://staging.api.thiqwave.com in your API calls
5. Test your integration with sample data

​

Production Environment

• Real funds and real payment rails
• Real customer data and compliance
• Production-grade reliability and monitoring
• API keys scoped to production environment only
• Rate limits and compliance rules enforced

​

Going live

1. Complete KYB verification in the Console
2. Wait for approval (typically 1-2 business days)
3. Generate production API keys in the Console
4. Update your application base URL to https://api.thiqwave.com
5. Use production credentials and deploy

​

API Keys

​

Creating API keys

1. Go to Settings → API Keys
2. Select the environment (Staging or Production)
3. Click Generate New Key
4. Copy the key immediately (you won’t be able to see it again)
5. Store it securely

​

Using API keys

curl -X GET "https://api.thiqwave.com/v1/accounts" \
  -H "X-API-Key: your-api-key"

​

Key rotation

1. Generate a new key in the Console
2. Update your application to use the new key
3. Verify all requests succeed with the new key
4. Delete the old key from the Console

​

Test scenarios (Staging only)

​

Available test scenarios

​

Using test scenarios

curl -X POST "https://staging.api.thiqwave.com/v1/payouts" \
  -H "X-API-Key: your-staging-key" \
  -H "Content-Type: application/json" \
  -d '{
    "quote_id": "quote_xyz789",
    "recipient": {
      "name": "Test User",
      "account_number": "123456789012",
      "bank_code": "050",
      "country": "AE"
    },
    "test_scenario": "failed"
  }'

​

Switching environments in the Console

1. Click the environment dropdown (shows “Staging” or “Production”)
2. Select the desired environment
3. The Console switches to show data for that environment
4. Your current API key, transactions, and settings are environment-specific

​

Monitoring and debugging

​

Viewing transactions

1. Go to Transactions
2. Filter by type (payouts, settlements, on-ramps, etc.)
3. Click a transaction to see full details, status, and logs

​

Checking webhook delivery

1. Go to Settings → Webhooks
2. Click View Deliveries for your endpoint
3. See delivery status, timestamps, and response codes
4. Retry failed deliveries manually

​

API error logs

1. Go to Logs
2. Filter by error type, timestamp, or request ID
3. View the full request and response

​

Base URLs summary

https://staging.api.thiqwave.com/v1/quotes

https://api.thiqwave.com/v1/quotes

​

Best practices

• Keep staging updated — Test new features in staging before deploying to production
• Use test scenarios — Simulate edge cases and errors in staging
• Rotate keys regularly — Refresh API keys every 90 days
• Monitor webhooks — Check webhook delivery logs for failures
• Test both environments — Verify integrations work in both staging and production
• Use environment variables — Never hardcode API keys or base URLs
• Tag transactions — Use metadata to track test vs. real transactions

​

Troubleshooting

​

Next steps

• Receiving Payments — Start accepting deposits
• KYB Verification — Complete compliance for production
• Webhooks — Set up event notifications