HTTP Result Codes - Success

HTTP Result Code
Reason
Explanation
200
Successful
The operation has been successfully performed.

HTTP Result Codes - Client Errors

HTTP Result Code
Reason
Explanation
400
Input error
Error in the input parameters.
Failed
The transaction failed because of a processing error at Payvision.
Failed, retry
The transaction failed but can be retried.
Declined
Declines, etc. In these cases the processing was performed correctly, but the end-result for the consumer is not sucessful.
Business rule error
Error due to a business rule or a configuration error.
Fraud
Errors suggesting fraudulent behavior.
Customer processing error
Error or cancellation by the consumer at the supplier. For example, the consumer abandoned their transaction at the supplier.
Referrals
Errors due to a referral by the supplier.
401, 403
Security error
Error in the authentication data. Generally no further details are available for security reasons.
404
Not found
The transaction failed because of a processing error at Payvision.

HTTP Result Codes - Server Errors

HTTP Result Code
Reason
Explanation
500, 501
Unexpected error
Unexpected error.

How POST and GET HTTP Result Codes Work

When a POST request is used to create a payment, a checkout or a token, there are two results to be considered:

  • HTTP Code Result
  • Operation Result

If the resource was successfully created by the POST request, the returned results are as presented below:

  • A HTTP Code Result - Success
  • An Id and TrackingCode ("tokenId" only for tokens) to be able to GET the subsequently created resource

Example: Successful POST & GET payment requests

POST /gateway/v3/payments
{  
   "action":"payment",
   "header":{ "businessId":"[BUSINESSID]" },
   "body":{...}
}
{ 
  "result": 0, 
  "description": "Ok", 
  "header":{...},
  "body":{ [with id and trackingCode] } 
}
GET /gateway/v3/payments/[PAYMENTID]?businessId=[BUSINESSID]
Same response received in the Payment POST Response.

Example: Unsuccessful POST payment request

POST /gateway/v3/payments
{  
   "action":"payment",
   "header":{ "businessId":"[BUSINESSID]" },
   "body":{...}
}
{
  "result": -1,
  "description": "Input error",
  "header": {
    "requestTimestamp": "2017-06-05T15:25:22Z",
    "requestCode": "100.a1be3b40-60d3-4a69-a21f-6d325615bafc"
  },
  "body": {
    "error": {
      "code": 10010500,
      "message": "Invalid transaction source"
    }
  }
}

Example: GET payment request

A GET payment cannot be requested because an **Id** or a **TrackingCode** is required.

What's next