This page explains how redirect payment methods work in your integration and how your application handles the return.
What redirect methods are
With a redirect payment method, the shopper is sent away from your checkout to a bank or payment provider to authorize the payment, then returned to your site or app. Many local and alternative payment methods use this pattern. The exact methods available depend on the market and on your account configuration, so do not assume a specific method is available without confirming it. See Supported Payment Methods.
Redirect methods are accepted through Adyen and must be enabled on your merchant account. Contact Valpay to enable specific methods.
This is not the same as 3D Secure. A redirect method is a payment method where the shopper authorizes the payment at their bank or provider. 3D Secure is an extra authentication step on a card payment that may also redirect the shopper. Both are handled as additional actions by Drop-in and Components, but they serve different purposes. See Security & Compliance ▸ 3D Secure (SCA).
How the redirect is handled
You include a returnUrl. When your server creates the payment (for example in the
/sessionsrequest), include areturnUrl. This is where the shopper comes back after authorizing.The shopper authorizes. Drop-in or Components sends the shopper to the bank or provider, where they approve the payment.
The shopper returns to your returnUrl. The provider redirects the shopper back to your
returnUrl, appending a redirect result to the URL.The redirect result is handled on return. With Drop-in and Components in the Sessions flow, the redirect is handled on the client side: the library uses the redirect result to complete the payment and shows the outcome to the shopper.
// Your server creates the payment with a returnUrl
{
"returnUrl": "https://your-site.com/checkout/return"
// ... merchantAccount, amount, reference, store (Store ID), etc.
}
// After authorizing, the shopper is redirected back to:
// https://your-site.com/checkout/return?redirectResult=...
// Drop-in / Components uses the redirect result to complete the payment.
Confirm the outcome with a webhook
The result shown after the redirect is not the authoritative outcome. Adyen confirms the final result with a webhook, for example an AUTHORISATION notification. Update your order based on the webhook, not on the redirect result alone. See Standard Payment Flow and Webhooks.
Notes
With Drop-in and Components, Adyen returns the eligible payment methods per transaction, including any redirect methods enabled on your account.
The Sessions flow handles redirects on the client side. The Advanced flow can also confirm a redirect on your server. See Sessions vs Advanced Flow.