Overview#
The Onerway Merchant API Testing Platform provides a comprehensive environment for integrating with our payment processing system. This platform enables you to:Test API functionality without development resources
Receive real-time request and response data
Simulate various business scenarios
Access detailed parameter specifications and examples
Prospective merchants evaluating Onerway services
Technical teams implementing system integration
Existing merchants troubleshooting API issues
Getting Started#
Step 1: Obtain Authentication Credentials#
Before using the platform, retrieve the following from your merchant dashboard:1.
merchantNo: Your unique merchant identifier
2.
appId: Application identifier for your site
3.
secretKey: Used for signature generation (secure storage required)
Note: Contact your account manager if you haven't received these credentials
Step 2: Select Environment#
| Environment | Description | Use Case |
|---|
| Sandbox | Simulated transactions with no actual funds movement | Development and testing |
| Production | Live transactions involving actual funds | Production operations |
Important: Complete comprehensive testing in the sandbox environment before migrating to production
Step 3: Initialize Environment Variables#
Step 4: Select API Endpoints#
Our comprehensive payment processing solution covers the complete transaction lifecycle:Core Payment Functions#
Checkout 🔵: Standardized payment experience with rapid integration JS-SDK 🔵: Server-side order creation for custom payment interfaces API Core 🔵: Low-level payment processing with maximum flexibility APMs 🔵: Support for global payment methods including wallets and bank transfers | Integration | Use Case | Complexity | Customization | Maintenance |
|---|
Checkout | Rapid deployment, standard flows | Low | Basic | Low |
JS-SDK | Custom payment UI | Medium | High UI control | Medium |
API | Fully custom payment flows | High | Complete control | High |
APMs | Global market expansion | Medium | Varies by method | Medium |
Post-Transaction Processing#
Refund 🔵: Complete refund lifecycle management Settlement 🔵: Merchant fund settlement with reconciliation file access Query and Management#
Query 🔵: Comprehensive data retrieval for transactions, installments, subscriptions, chargebacks, and tokenized cards Utils 🔵: Auxiliary functions including signature verification 🔵 Stable | 🟡 Beta | 🟠 Deprecated
Step 5: Initiate Test Requests#
1.
Select the desired API endpoint from the navigation panel
2.
Complete the required request parameters (pre-populated with sample values)
3.
Click "Send" to submit the request
4.
Review the response and detailed information
If you encounter Repeated order transactions!, click the auto-generate button
Core Payment Flow#
Common Error Handling#
| Error Code | Description | Resolution |
|---|
13027 | Repeated order transactions! | Click auto-generate to refresh request parameters |
70002 | Unknown decline | Contact technical support |
Security Best Practices#
1.
Never store keys in client-side code
2.
Include valid signatures with all requests
Verify signatures on all webhook notifications
Use HTTPS for all API communications
3.
Configure API call IP whitelists in the merchant dashboard
Restrict webhook receiver server IP ranges
Terminology#
| Term | Definition |
|---|
| Merchant | Entity using Onerway payment services |
| Transaction | Single payment event |
| Settlement | Funds settlement process |
| Chargeback | Transaction dispute initiated by consumer |
| Webhook | Asynchronous notification mechanism |
| Tokenization | Card information encryption technology |
Technical Support#
For technical assistance:1.
Prepare order number, error details, and reproduction steps
2.
Submit detailed issue description with screenshots
3.
Technical team will respond within one business day
