Failure codes and status details
Learn more about possible status details based on failure codes for VOP requests
VOP requests can fail. When this is the case, their status is set failed
and failure_code
and status_details
are added for additional context.
Outgoing requests
Failure code | Status details |
---|---|
business_error | identification type is not supported by party agent |
party agent is not a participant | |
additional information not supported by party agent | |
technical_error | there was an error processing the request, please contact the support. |
psp_technical_error | missing response timestamp in header |
invalid response timestamp in header | |
missing or mismatched request ID in header | |
invalid content type in header | |
failed to parse error response | |
non standard error response | |
PSP took more than 5 seconds to respond | |
responding PSP responded with a 500 - internal server error | |
responding PSP responded with an invalid request format error | |
responding PSP responded with a client invalid / unrecognized error | |
responding PSP responded with a client inconsistent error | |
responding PSP responded with a timestamp invalid error | |
responding PSP responded with an unknown error | |
PSP returned invalid response, PartyNameMatch and PartyIDMatch are empty | |
PSP returned invalid response, both PartyNameMatch and PartyIDMatch are set | |
PSP returned invalid response, PartyIDMatch is set for 'name' request | |
PSP returned invalid response, PartyNameMatch is empty for 'name' request | |
PSP returned invalid response, PartyNameMatch is set for … request | |
PSP returned invalid response, PartyIDMatch is empty for … request | |
PSP returned close match but no matched name | |
PSP returned close match but suggested name is too long | |
PSP returned invalid response value for partyNameMatch | |
PSP returned invalid response value for partyIdMatch |
Incoming requests
Error code | Status details |
---|---|
business_error | client response identification type mismatch: expected ..., got ... |
technical_error | There was an error processing the request, please contact the support. |
Updated 7 days ago