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.

Endpoint destination URL
Click to copy

Header Parameters


A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).

Request Parameters


Data for 3DS authentication.


Use this collection to submit the details that were returned as a result of the /payments call.

Max length: 200000

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.

threeDSAuthenticationOnlybooleanDeprecated in version 69

Use authenticationData.authenticationOnly instead.

Change the authenticationOnly indicator originally set in the /payments request. Only needs to be set if you want to modify the value set previously.

Response parameters

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.

    Show moreShow less
  • 400 - Bad Request

    A problem reading or understanding the request.

    Show moreShow less
  • 401 - Unauthorized

    Authentication required.

    Show moreShow less
  • 403 - Forbidden

    Insufficient permissions to process the request.

    Show moreShow less
  • 422 - Unprocessable Entity

    A request validation error.

    Show moreShow less
  • 500 - Internal Server Error

    The server could not process the request.

    Show moreShow less