Reply Flags and Processor Response Code
|
|
Cybersource recommends using the reply flag value and the processor response code to determine the transaction result. |
The following table describes the reply flags and processor response codes that the SCMP API can return for the online bank transfer services.
|
Reply Flag |
Processor Response Code |
Description |
|
DINVALIDDATA |
n10000—status: failed. n30600—status: failed. n30700—status: failed. |
Invalid request. Possible reasons: nThe request data is invalid. nProcessor declined the transaction due to tax errors or government compliance errors. |
|
DPAYMENTREFUSED |
n30200—status: failed. n30350—status: failed. n30500—status: failed. |
Possible reasons: nProcessor declined the transaction due to funding source problems. nThe transaction was flagged as high risk. nInsufficient funds. |
|
ESYSTEM |
n20000—status: failed. n20001—status: failed. n20002—status: failed. n30000—status: failed. n30100—status: failed. |
Possible reasons: nThe signature was not included in the HTTP header. nThe signature in the HTTP header has expired or its not a valid signature. nThe API version in the HTTP header was missing or is not supported. |
|
SOK |
n00001—status: pending. n00002—status: abandoned. n00003—status: authorized. n00004—status: settled. n00006—status: refunded. |
Transaction was successful. |