Testing with devnet

This guide walks you through testing your Kobaru integration using Solana Devnet. Devnet lets you verify your integration works correctly without spending real money.

What is devnet?

Solana Devnet is a test network that mirrors mainnet behavior but uses valueless test tokens. Use it for:

Development and debugging

Integration testing

Demo environments

CI/CD pipelines

Step 1: Configure for devnet

Update your integration to use the devnet network identifier:

SDK integration

Transparent proxy

In the Kobaru Console:

Go to Services > [Your Service]

Under Network, select Solana Devnet

Save changes

Step 2: Get test USDC

You need devnet USDC to make test payments. Here's how to get some:

Option 1: Circle USDC faucet

Visit the Circle USDC Faucet

Select Solana Devnet

Enter your wallet address

Request test USDC

Option 2: Solana CLI

Then use a faucet to get devnet USDC to your address.

Option 3: Use Kobaru test wallet

Contact support@kobaru.io for access to a pre-funded test wallet.

Step 3: Test the payment flow

Test 1: Verify 402 response

Request your endpoint without payment:

Expected response:

Test 2: Verify payment acceptance

Use an x402-compatible client to make a payment:

Test 3: Verify usage tracking

For pay-per-request endpoints, verify the counter decrements:

Step 4: Test error scenarios

Insufficient funds

Use a wallet with no USDC:

Invalid transaction

Construct a malformed transaction:

Expired usage

For pay-per-request, exhaust the bundle:

Common testing issues

"Network not supported"

Cause: Your API key or capability isn't configured for devnet.

Solution: Enable the devnet capability in the Kobaru Console.

"Simulation failed"

Cause: The test wallet doesn't have devnet USDC.

Solution: Get test tokens from a faucet.

"Invalid fee payer"

Cause: Transaction not constructed correctly.

Solution: Ensure Kobaru's facilitator address is set as fee payer.

Token not found

Cause: Using mainnet USDC address on devnet.

Solution: Use the devnet USDC address: 4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU

Slow transaction confirmation

Cause: Devnet can be slower or less reliable than mainnet.

Solution: Increase your timeout settings during testing. This is normal for devnet.

Environment variables

Set up your development environment:

CI/CD integration

Add automated testing to your pipeline:

Network comparison

Property	Devnet	Mainnet
Network ID	`solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1`	`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`
USDC address	`4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU`	`EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v`
Token value	None (test tokens)	Real USD value
Use case	Development, testing	Production

Next steps

Once your devnet tests pass:

Production guide - Go-live checklist

Pricing guide - Set your production prices

Security - Review security best practices

Testing with devnet

What is devnet?#

Step 1: Configure for devnet#

SDK integration#

Transparent proxy#

Step 2: Get test USDC#

Option 1: Circle USDC faucet#

Option 2: Solana CLI#

Option 3: Use Kobaru test wallet#

Step 3: Test the payment flow#

Test 1: Verify 402 response#

Test 2: Verify payment acceptance#

Test 3: Verify usage tracking#

Step 4: Test error scenarios#

Insufficient funds#

Invalid transaction#

Expired usage#

Common testing issues#

"Network not supported"#

"Simulation failed"#

"Invalid fee payer"#

Token not found#

Slow transaction confirmation#

Environment variables#

CI/CD integration#

Network comparison#

Next steps#