Kobaru
  1. Guides
Kobaru
  • Kobaru.io Gateway API
    • Introduction
      • What is Kobaru?
      • Quick start
      • How x402 works
    • Integration
      • Standard x402 SDK
      • Advanced SDK
      • Transparent proxy integration
      • Direct API integration
    • Core Concepts
      • Available Chains and Assets
      • Payment schemes
      • Security
      • Usage models
    • Guides
      • Pricing your API
      • Going to Production
      • Testing with devnet
      • Bazaar discovery
    • API Reference
      • Error Handling
      • Get Supported Payment Kinds
      • Verify Payment Authorization
      • Settle Payment
    • Discovery
      • List Discovery Resources
    • Schemas
      • SupportedResponse
      • ErrorResponse
      • UnauthorizedResponse
      • RateLimitResponse
      • VerifySuccessResponse
      • VerifyErrorResponse
      • SettleSuccessResponse
      • SettleErrorResponse
      • DiscoveryResourceItem
      • ListDiscoveryResourcesResponse
  1. Guides

Going to Production

Going to production#

This guide provides a checklist for launching your Kobaru integration in production. Work through each step to ensure a smooth go-live.

Pre-launch checklist#

1. Switch to mainnet#

Update your network configuration from devnet to mainnet:
SDK integration:
Transparent proxy:
1.
Go to Services > [Your Service] in the Kobaru Console
2.
Change Network from Solana Devnet to Solana Mainnet
3.
Save changes

2. Use production API key#

Create a production API key and update your environment:
API key security:
Store in environment variables, not code
Use secret management (AWS Secrets Manager, Vault, etc.)
Never commit to source control
Rotate keys periodically

3. Verify wallet address#

Confirm your production wallet is configured correctly:
Wallet address is a mainnet address
You have sole access to the private key
Wallet can receive SPL tokens (USDC)
Consider using a hardware wallet for high-value operations
Test with a small payment:
1.
Set a very low price ($0.001)
2.
Make a real payment from a test wallet
3.
Verify funds arrive in your wallet
4.
Restore your intended pricing

4. Set production pricing#

Review and finalize your pricing:
Prices reflect your costs and desired margin
Usage limits are appropriate for your use case
Consider offering bundle discounts
See Pricing guide for pricing strategies.

5. Enable error handling#

Implement robust error handling for production:

6. Set up monitoring#

Implement monitoring for your payment flow:
Metrics to track:
MetricWhy it matters
Payment success rateDetect integration issues
Average response timeMonitor performance
Error rate by typeIdentify patterns
Revenue per hour/dayTrack business health
Alerting thresholds:
Payment success rate drops below 95%
Average response time exceeds 1 second
Error rate exceeds 5%
No payments received for 1 hour (if you expect continuous traffic)

7. Configure logging#

Enable structured logging for debugging:

8. Test the full flow#

Before announcing, complete an end-to-end test:
Request endpoint without payment - expect 402 response
Submit valid payment - expect 200 response with data
Submit duplicate payment - expect idempotent response
Submit invalid payment - expect clear error message
Exhaust usage - expect 403 with usage error
Verify funds arrive in wallet

Launch day#

Gradual rollout#

Consider a phased launch:
1.
Private beta - Invite a few trusted users
2.
Public beta - Open to early adopters
3.
General availability - Full launch

Communication#

Prepare documentation for your users:
API documentation with payment instructions
Code examples in common languages
FAQ for common issues
Support contact information

Post-launch#

Monitor key metrics#

First 24 hours:
Check payment success rate
Review error logs
Verify wallet balance increases
Respond to user feedback
First week:
Analyze usage patterns
Identify optimization opportunities
Consider pricing adjustments

Ongoing maintenance#

Review API key usage monthly
Rotate keys annually (or after any suspected compromise)
Update SDK dependencies regularly
Monitor Kobaru status page for announcements

Rollback plan#

If issues arise, have a rollback plan ready:

Option 1: Disable payments#

In the Kobaru Console, temporarily disable your capabilities. Your endpoint returns a 503 Service Unavailable error, and users see a clear message that payments are temporarily disabled.

Option 2: Switch to devnet#

Update your network configuration to devnet. Existing mainnet tokens stop working, but your endpoint remains accessible for users with devnet tokens.

Option 3: Remove middleware#

If using SDK integration, remove the payment middleware to make endpoints free temporarily:

Quick reference#

Production checklist#

StepStatus
Network set to mainnet[ ]
Production API key configured[ ]
Wallet address verified[ ]
Pricing finalized[ ]
Error handling implemented[ ]
Monitoring configured[ ]
Logging enabled[ ]
End-to-end test passed[ ]

Network identifiers#

EnvironmentNetwork ID
Developmentsolana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1
Productionsolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp

Support contacts#

Technical support: support@kobaru.io
Security issues: security@kobaru.io
Status page: status.kobaru.io

Related documentation#

Testing guide - Devnet testing before production
Security - Security best practices
Error codes - Understanding error responses
Modified at 2026-01-04 13:57:15
Previous
Pricing your API
Next
Testing with devnet
Built with