Error codes
Soft decline
Adyen
Adyen code XD – Forward to Issuer
The transaction needs to be forwarded to the issuer. The shopper should contact their issuing bank for clarification.
What does Adyen refusal code XD mean?
Adyen refusal code XD Forward to Issuer is a generic issuer refusal similar to code XA, returned when the issuer blocked the transaction without providing a specific documented reason. Like XA, it maps loosely to the do_not_honor family of generic declines.
Is it a soft or hard decline?
Code XD is a soft decline. A portion of these are transient and recover with intelligent retry timing, while others require outreach for a different payment method.
Common root causes
Issuer risk or velocity thresholds
Temporary issuer-side conditions
Unrecognized merchant descriptors
BIN or acquirer-route mismatches
Recommended recovery steps
Retry with issuer-aware timing rather than immediately.
Apply 3-D Secure when supported to improve authorization rates.
Clarify descriptors to reduce cardholder-initiated issuer blocks.
Escalate to outreach if retries are consistently unsuccessful.
How FlyCode handles Adyen code XD
FlyCode classifies XD declines alongside other generic issuer refusals (XA, 01, 05) and applies the same pattern-based recovery logic. ML models identify transient vs. persistent cases using network-level signals and Mastercard/Visa data, retrying only when it is statistically worthwhile.
What does Adyen refusal code XD mean?
Adyen refusal code XD Forward to Issuer is a generic issuer refusal similar to code XA, returned when the issuer blocked the transaction without providing a specific documented reason. Like XA, it maps loosely to the do_not_honor family of generic declines.
Is it a soft or hard decline?
Code XD is a soft decline. A portion of these are transient and recover with intelligent retry timing, while others require outreach for a different payment method.
Common root causes
Issuer risk or velocity thresholds
Temporary issuer-side conditions
Unrecognized merchant descriptors
BIN or acquirer-route mismatches
Recommended recovery steps
Retry with issuer-aware timing rather than immediately.
Apply 3-D Secure when supported to improve authorization rates.
Clarify descriptors to reduce cardholder-initiated issuer blocks.
Escalate to outreach if retries are consistently unsuccessful.
How FlyCode handles Adyen code XD
FlyCode classifies XD declines alongside other generic issuer refusals (XA, 01, 05) and applies the same pattern-based recovery logic. ML models identify transient vs. persistent cases using network-level signals and Mastercard/Visa data, retrying only when it is statistically worthwhile.
What does Adyen refusal code XD mean?
Adyen refusal code XD Forward to Issuer is a generic issuer refusal similar to code XA, returned when the issuer blocked the transaction without providing a specific documented reason. Like XA, it maps loosely to the do_not_honor family of generic declines.
Is it a soft or hard decline?
Code XD is a soft decline. A portion of these are transient and recover with intelligent retry timing, while others require outreach for a different payment method.
Common root causes
Issuer risk or velocity thresholds
Temporary issuer-side conditions
Unrecognized merchant descriptors
BIN or acquirer-route mismatches
Recommended recovery steps
Retry with issuer-aware timing rather than immediately.
Apply 3-D Secure when supported to improve authorization rates.
Clarify descriptors to reduce cardholder-initiated issuer blocks.
Escalate to outreach if retries are consistently unsuccessful.
How FlyCode handles Adyen code XD
FlyCode classifies XD declines alongside other generic issuer refusals (XA, 01, 05) and applies the same pattern-based recovery logic. ML models identify transient vs. persistent cases using network-level signals and Mastercard/Visa data, retrying only when it is statistically worthwhile.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
Is Adyen code XD a soft or hard decline?
How is XD different from XA?
They are near-duplicates returned by different acquirer integrations. Both indicate a generic issuer refusal without a specific reason, and both are handled with similar retry-plus-outreach recovery logic.
How does FlyCode handle Adyen XD?
FlyCode's ML models classify XD declines alongside other generic issuer refusals, timing retries for when success is statistically likely and escalating to outreach when the block is persistent.
