Environments & Console

Overview

Thiqwave provides separate staging and production environments for development and live operations. The Thiqwave Console at console.thiqwave.com is your control center for managing both environments, handling onboarding, monitoring transactions, and generating API keys.

Thiqwave Console

Access the Console at console.thiqwave.com to:

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

Use staging to test integrations without moving real money. Base URL: https://staging.api.thiqwave.com Characteristics:

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

The staging environment comes with pre-seeded data to help you get started immediately:

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

Never use real customer data in the staging environment. All staging data is periodically reset.

Getting started in staging

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

Production Environment

Use production for live transactions with real funds and real customers. Base URL: https://api.thiqwave.com Characteristics:

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

Before moving to production:

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

Production API keys are sensitive. Never commit them to version control. Use environment variables and secure vaults to manage credentials.

API Keys

API keys are environment-scoped. Staging keys only work with the staging environment, and production keys only work with production.

Creating API keys

In the Console:

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

Using API keys

Include your API key in the X-API-Key header for all requests:

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

Key rotation

Rotate API keys periodically for security:

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

Test scenarios (Staging only)

In staging, you can simulate different transaction outcomes by passing a test_scenario parameter. This allows you to test error handling and edge cases.

Available test scenarios

Scenario	Behavior
`completed`	Transaction completes successfully (default)
`failed`	Transaction fails with a generic error
`pending`	Transaction stays in pending state
`compliance_hold`	Transaction is held for compliance review

Using test scenarios

Pass test_scenario in your request body:

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"
  }'

Use test scenarios to verify your webhook handling, error UI, and retry logic before going live.

Switching environments in the Console

In the Console header, you’ll see an environment selector:

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

Monitoring and debugging

Viewing transactions

In the Console:

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

Checking webhook delivery

In the Console:

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

API error logs

Check the Console’s Logs section to debug API issues:

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

Base URLs summary

Environment	Base URL
Staging	`https://staging.api.thiqwave.com`
Production	`https://api.thiqwave.com`

All endpoints follow the pattern: {BASE_URL}/v1/{endpoint} Example staging request:

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

Example production request:

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

Issue	Cause	Resolution
401 Unauthorized	Invalid or expired API key	Verify API key is correct and for the current environment
403 Forbidden	API key belongs to different environment	Use the correct API key for the environment (staging vs. production)
API key not working	Key was regenerated or revoked	Generate a new key in the Console
Webhook not firing	Endpoint unreachable or misconfigured	Check webhook URL and retry delivery in Console

Next steps

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

Getting Started

Core Concepts

Guides

Reference

Environments & Console

Overview

Thiqwave Console

Staging Environment

Test data

Getting started in staging

Production Environment

Going live

API Keys

Creating API keys

Using API keys

Key rotation

Test scenarios (Staging only)

Available test scenarios

Using test scenarios

Switching environments in the Console

Monitoring and debugging

Viewing transactions

Checking webhook delivery

API error logs

Base URLs summary

Best practices

Troubleshooting

Next steps

​Overview

​Thiqwave Console

​Staging Environment

​Test data

​Getting started in staging

​Production Environment

​Going live

​API Keys

​Creating API keys

​Using API keys

​Key rotation

​Test scenarios (Staging only)

​Available test scenarios

​Using test scenarios

​Switching environments in the Console

​Monitoring and debugging

​Viewing transactions

​Checking webhook delivery

​API error logs

​Base URLs summary

​Best practices

​Troubleshooting

​Next steps

Overview

Thiqwave Console

Staging Environment

Test data

Getting started in staging

Production Environment

Going live

API Keys

Creating API keys

Using API keys

Key rotation

Test scenarios (Staging only)

Available test scenarios

Using test scenarios

Switching environments in the Console

Monitoring and debugging

Viewing transactions

Checking webhook delivery

API error logs

Base URLs summary

Best practices

Troubleshooting

Next steps