Payments POST Transaction returns 201 status

Steve Weinzirl

The Payments Transaction POST end point documentation states that a transaction can complete and return a status of 201 instead of 200.

"Response 201 Created

Returned when the transaction is successfully created but an unexpected problem occurs retrieving the full details of the transaction. The Location response header indicates where the full details of the transaction can be retrieved with a GET request."

The documentation gives no more information. There is no way to force this error while testing. I have no idea what the Location response header really contains because I can't see an example of it. I need more specific information in order to code an interface that properly handles a 201 response code.

Amanda Glosson

Hi Steve, thank you for your question.


We will work to improve this area of our documentation for the future based on your feedback.


In the mean time, I wanted to share an example of what the Location header value would look like:


"/v1/transactions/92844827-5b74-40db-907f-480b13242eb5"


It would indicate the route to the GET transaction endpoint and include the transaction id in the route as the endpoint would expect. The response BODY would be empty.


Please let us know if you have any further questions, happy to help!


Amanda