Submit details for a payment
Submits details for a payment created using /payments. This step is only needed when no final state has been reached on the /payments request, for example when the shopper was redirected to another page to complete the payment.
A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).
Use this collection to submit the details that were returned as a result of the /payments call.
Encoded payment data. For authorizing a payment after using 3D Secure 2 Authentication-only:
If you received resultCode: AuthenticationNotRequired in the /payments response, use the threeDSPaymentData from the same response.
If you received resultCode: AuthenticationFinished in the /payments response, use the action.paymentData from the same response.
Change the authenticationOnly indicator originally set in the /payments request. Only needs to be set if you want to modify the value set previously.
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.
HTTP Responses
200 - OK
The request has succeeded.
400 - Bad Request
A problem reading or understanding the request.
401 - Unauthorized
Authentication required.
403 - Forbidden
Insufficient permissions to process the request.
422 - Unprocessable Entity
A request validation error.
500 - Internal Server Error
The server could not process the request.