Adyen · Decline codes
What does Adyen refusal reason 39 “RReq not received from DS” mean?
Checked
Adyen refusal reason 39, "RReq not received from DS", means the issuer or the card scheme was not able to communicate the outcome of 3D Secure authentication through the RReq (results request) message. The shopper may have completed authentication, but the result never reached Adyen, so the payment could not continue. A fresh attempt usually works.
- Type
- Authentication error (technical)
- Who declined
- The issuer or card scheme 3D Secure systems
- Retry
- Yes, the shopper can try again.
- Shopper action
- Try the payment again.
- Merchant action
- Allow a retry; check for a pattern if it repeats.
What PlatformDTC does
PlatformDTC does not connect to Adyen; its checkout runs on Stripe and PayPal. Its Stripe rail never retries an authentication step without the shopper present; the customer is asked to confirm the payment themselves.
Why it happens
In 3D Secure 2 the directory server (DS) of the card scheme relays the authentication result. If that message does not arrive, there is no result to continue with.
What the shopper can do
Try the payment again and complete verification once more.
What the store can do
Let the shopper retry. A cluster of code 39 across many shoppers points to a scheme or issuer incident.
For developers
refusalReasonCode "39". RReq is the results request sent from the directory server in the 3D Secure 2 flow.
Frequently asked questions
- What is an RReq in Adyen refusal 39?
- The 3D Secure results message the issuer and scheme send back; refusal 39 means it never arrived.
- Did the shopper fail 3D Secure (Adyen 39)?
- Not necessarily. The result was lost in transit, so a new attempt can succeed.
Sources
- Adyen refusal reasons — Adyen
Related
- 42 — 3D Secure failed because of a problem at the card network or issuer.
- 11 — 3D Secure authentication was not done or did not succeed.
- 38 — The issuer declined the exemption request and requires 3D Secure for this payment.
- 46 — Adyen stopped the attempt itself so you are not charged scheme penalty fees for excessive retries.
- 50 — The shopper disabled the token the merchant used for recurring charges.
- 2 — The issuer refused the payment and gave no usable reason; Adyen's catch-all refusal.
- 3 — The issuer referred the payment: it wants the cardholder (or merchant) to contact it first.
- 4 — Something failed on the acquirer's side, not with the shopper's card.