Overview
This document provides a comprehensive definition and explanation of Oceanpayment’s core response codes, covering Payments, Order Management, OPCard, and OPCCOUNT accounts. These codes provide a complete view of transaction processing statuses and are essential for troubleshooting, reconciliation, and customer support.
Response Codes
Response codes are the official confirmation between merchants and Oceanpayment, ensuring transactions are transmitted accurately, securely, and reliably.
💳 Payments
🧾 Order Management
🎫 OPCard
💰️ OPCCOUNT
Response Code Types
| Type | Core Function |
|---|---|
| Payments | Indicates the result of a payment request, including success, failure, and specific reasons |
| Order Management | Codes for order-related operations and management |
| OPCard | Codes for OPCard issuance, transactions, and management |
| OPCCOUNT | Codes for operations within OPCCOUNT accounts |
Best Practices for Usage
Given the variety of response codes, the following best practices help ensure reliable integration and handling:
- Code Dependencies
- Use business response codes as the final reference for transaction outcomes.
- HTTP status codes only indicate whether the API request was successfully delivered; they do not reflect transaction results.
- User-Facing Messages
- Display clear and friendly messages based on response codes.
- Avoid exposing raw error codes (especially issuer error codes), which may confuse users or be misused.
- Logging and Monitoring
- Log all transaction requests and responses in your backend, including response codes.
- Set up monitoring and alerting for abnormal failure rates to detect issues promptly.
- Query APIs for Pending Transactions
- For transactions returned as
processingor if Asynchronous Notifications are missing, proactively use the Query Order to retrieve the final transaction status.
The list of Oceanpayment response codes may be updated or expanded. We recommend reviewing the official Oceanpayment technical documentation regularly to stay up to date.