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.
In: header
Header Parameters
A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).
Request Body
application/json
Data for 3DS authentication.
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.
length <= 200000Change the authenticationOnly indicator originally set in the /payments request. Only needs to be set if you want to modify the value set previously.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/payments/details" \ -H "Idempotency-Key: 37ca9c97-d1d1-4c62-89e8-706891a563ed" \ -H "Content-Type: application/json" \ -d '{ "details": { "redirectResult": "X6XtfGC3!Y..." } }'Example response when submitting the redirect result
{ "resultCode": "Authorised", "pspReference": "V4HZ4RBFJGXXGN82"}Start a transaction POST
Sends payment parameters (like amount, country, and currency) together with other required input details collected from the shopper. To know more about required parameters for specific payment methods, refer to our [payment method guides](https://docs.adyen.com/payment-methods). The response depends on the [payment flow](https://docs.adyen.com/payment-methods#payment-flow): * For a direct flow, the response includes a `pspReference` and a `resultCode` with the payment result, for example **Authorised** or **Refused**. * For a redirect or additional action, the response contains an `action` object.
Create a payment session POST
Creates a payment session for [Drop-in](https://docs.adyen.com/online-payments/build-your-integration/sessions-flow/?platform=Web&integration=Drop-in), [Components](https://docs.adyen.com/online-payments/build-your-integration/sessions-flow/?platform=Web&integration=Components), and [Hosted Checkout](https://docs.adyen.com/online-payments/build-your-integration/sessions-flow/?platform=Web&integration=Hosted+Checkout) integrations. The response contains encrypted payment session data. The front end then uses the session data to make any required server-side calls for the payment flow. You get the payment outcome asynchronously, in an [AUTHORISATION](https://docs.adyen.com/api-explorer/#/Webhooks/latest/post/AUTHORISATION) webhook.