x402 is a payment standard that enables you to accept cryptocurrency payments over standard HTTP. This eliminates the need for wallet popups and blockchain complexity, providing a payment experience similar to standard API calls.
No, blockchain knowledge is not required. Oura402 handles all blockchain operations. If you can make an HTTP request, you can integrate Oura402.
Which blockchain does Oura402 support?
Oura402 currently supports Solana. We manage all blockchain interactions, so you never need to interact with the blockchain directly.
Getting Paid
How do I receive payments?
Simply provide your wallet address to Oura402. When a customer pays you through x402, we verify the payment and the funds are transferred to your wallet.
Do I need a special wallet?
Any Solana wallet is compatible with Oura402. If you do not have a wallet yet, we recommend Phantom or Solflare.
How long does it take to receive payments?
Payments are confirmed within 2-5 seconds on Solana, significantly faster than traditional payment processors which may take several days.
What are the fees?
Oura402 does not charge a percentage of your payments. You only pay for API usage. Please visit oura402.dev/pricing for current plan details.
API & Integration
Is there an SDK available?
An SDK is not required. Oura402 uses standard HTTP endpoints, allowing you to use any HTTP client library you prefer.
Can I use this from my frontend application?
No, API keys should always be stored on the server side. Exposing your API key in frontend code creates a security risk.
What happens if the API experiences downtime?
Oura402 maintains 99.9% uptime. In the event of service disruption, please check oura402.dev/status for real-time updates.
What are the rate limits?
Rate limits depend on your subscription plan:
Free: 100 requests per minute
Paid: 1,000 requests per minute
Enterprise: Custom limits based on your requirements
You will receive a 429 Too Many Requests error response. You can either wait briefly before retrying or upgrade your plan to increase your rate limit.
Security
How should I protect my API key?
Follow these security best practices:
Store API keys in environment variables, not in source code
Never commit API keys to version control systems
Avoid exposing API keys in frontend code
Rotate keys regularly as part of your security policy
What should I do if my API key is compromised?
If you suspect your API key has been compromised:
Navigate to your dashboard
Delete the compromised key
Generate a new API key
Update your application with the new key
This process requires approximately 2 minutes to complete.
Is Oura402 secure?
Yes. Oura402 implements the same security standards as traditional payment processors. All API calls are encrypted, payments are verified on-chain, and we never hold custody of your funds.
Do not retry: Invalid parameters, authentication errors, malformed wallet addresses
Implement exponential backoff to increase the delay between successive retry attempts.
How can I test my integration without using real funds?
Begin by testing with small payment amounts. Start with the minimum payment amount to verify your integration works correctly before deploying to production.
When should I use WebSockets instead of the REST API?
WebSockets are recommended for use cases requiring real-time updates:
Payment dashboards
Real-time payment notifications
Monitoring multiple concurrent payments
For standard verification workflows, the REST API is sufficient. See WebSocket API docs for implementation details.
What are the recommended best practices for using Oura402?
Always validate that payment amounts match your expected values
Implement comprehensive logging for debugging purposes
Handle errors gracefully with appropriate user feedback
Start with a simple implementation and add complexity only when necessary
Review error messages carefully, as they typically indicate the specific issue
