A
AdyenAdyen 39
RReq Not Received from DS
Technical
System or connectivity issues
Retryable
This decline may succeed on retry
Description
The issuer or scheme was unable to communicate the 3DS outcome via RReq.
Recommended Action
Retry the transaction.
Common Causes
- 3DS directory server communication failure
- Timeout in 3DS protocol exchange
Recovery Tips
- Retry after a short delay
Quick Reference
Code
39
Category
Technical
Retryable
Yes
Source
Adyen
Recoverability verdict
39 is often recoverable
Payments failing with code 39 are often recoverable with the right retry timing and routing. Slicker recovers up to 70% of soft declines with smart retries.
Related Decline Codes
2Retryable
Refused
The transaction was refused by the issuer without additional information.
3Retryable
Referral
The issuer requires a referral — typically a voice authorisation or manual review.
4Retryable
Acquirer Error
The transaction did not go through due to an error on the acquirer's end.
7Retryable
Invalid Amount
An amount mismatch occurred during the transaction process.