5. API errors
Use the HTTP status together with the response body. For a MYR P2P PayIn, start with the error reported for each key inside paymentData.
| HTTP | Meaning | What to check |
|---|---|---|
| 401 | API key, timestamp or signature is invalid. | Use the v1 signing rules. For transaction history, check the request ID and canonical signature. |
| 403 | Request source IP is outside the allowlist. | Use an allowed source IP. |
| 404 | The requested operation could not be found. | Use the original external_id and shop_code for the correct payment direction. |
| 409 | An existing operation has the same identifier and different request data. | Retrieve the existing operation before deciding whether this is a distinct order. |
| 422 | Invalid input, currency mismatch, or a business rule prevented the request. | Inspect code and any field-level errors. Send amount as a positive decimal string and currency as MYR. |
| 429 | Rate limit reached. | Wait for the interval in the Retry-After header. |
| 500, 503 | Processing or a required service is temporarily unavailable. | On an uncertain create, look up the operation and retry with the original shop, identifier and request data. |
Missing PayIn routing field
If bank_code is omitted from paymentData, the request returns 422. The error is keyed by the missing field. The relevant response fields are shown below.
{
"message": "Invalid paymentData",
"code": "validation_error",
"errors": {
"bank_code": "Field is required"
},
"error": {
"code": "validation_error",
"message": "Invalid paymentData"
}
}
The same rule applies to wallet_provider. See the full PayIn request. Authentication failures can return a body containing only message.