When calling the DPO Pay by Network API, the gateway returns a numeric Result and human-readable ResultExplanation value.
Use these codes to determine next steps in your payment flow.
000means success.
All other codes indicate a validation, configuration, or processing error.
Response Fields
| Field | Description |
|---|---|
Result | Numeric response code indicating the outcome |
ResultExplanation | Text explanation of the result |
TransToken | Returned when a token is successfully created |
TransRef | DPO transaction reference (if created) |
notes | Additional notes (if provided) |
AllocationID | Returned for xPay allocation payments |
AllocationCode | Receiver merchant code (xPay allocation) |
Common Response Codes
| Code | Meaning | Action for Developer |
|---|---|---|
| 000 | Transaction created | Proceed → redirect shopper or process next step |
| 801 | Missing Company Token | Ensure CompanyToken is included |
| 802 | Invalid Company Token | Verify token value / environment |
| 803 | Missing or invalid Request type | Set <Request>createToken</Request> (or correct operation) |
| 804 | XML formatting error | Ensure valid XML structure & field case |
| 901 | Field exceeds max length | Trim values (names, refs, descriptions) |
| 902 | Missing mandatory fields | Check payment + customer fields |
| 904 | Unsupported currency | Use valid currency for merchant account |
| 905 | Transaction exceeds limit | Use smaller amount or contact support |
| 906 | Monthly merchant limit exceeded | Contact DPO Support |
| 922 | Invalid provider reference | Verify payment provider configuration |
| 923 | Allocation > PaymentAmount | Check allocation data (xPay only) |
| 930 | Invalid block payment code | Review merchant configuration |
| 940 | CompanyRef already paid | Treat as duplicate order or display existing status |
| 950 | Required tag missing | Check body tags match docs exactly |
| 960 | Tag sent multiple times | Remove duplicate XML fields |
Best Practices
- Log
Result+ResultExplanation+TransRef(if present). - If you get
804(XML error), validate structure & remove BOM/whitespace. - For
940duplicate reference, query status before retrying. - For merchant limit codes (
905,906), send customer friendly decline message.
Related Guides
| Topic | Link |
|---|---|
| Create Token | /developers/create-token |
| Callback Processing | /developers/payment-callbacks |
| Status Lookup | /developers/verify-token |
| Refund / Void | /developers/refund-void |
Next Step: Verify Token Example
Most merchants pair this table with polling for final status:
<API3G>
<CompanyToken>{{CompanyToken}}</CompanyToken>
<Request>verifyToken</Request>
<TransToken>{{TransToken}}</TransToken>
</API3G>Support
If you hit an unclear gateway response, contact DPO Support and include:
TransReforTransTokenCompanyRef- Full raw XML request (with token masked)
- Full raw XML response
- Timestamp and environment