PaymentDisputeReasonCode
Stay organized with collections
Save and categorize content based on your preferences.
Reason code for disputed transaction.
Enums |
UNKNOWN_REASON |
Do not ever set this default value! |
FRAUD |
Fraudulent transaction. |
FAMILIAR_FRAUD |
Fraudulent transaction made by a family member, friend, or member of the household. |
SUSPICIOUS |
Suspicious transaction. |
CHARGE_NOT_RECOGNIZED |
The user does not recognize the charge on their bill. |
CREDIT_NOT_PROCESSED |
The user was told they would get a refund but they never got it. |
DUPLICATE_PAYMENT |
The user was charged twice for the same purchase. |
SUBSCRIPTION_CANCELED |
The user canceled a subscription but was still charged. |
INPUT_ERROR |
User input error. |
INSUFFICIENT_FUNDS |
User didn't have sufficient funds. |
NOT_DELIVERED |
Item was never delivered. |
DEFECTIVE_OR_NOT_AS_DESCRIBED |
Merchandise was defective or not as described. |
INCORRECT_MERCHANDISE |
The user received the wrong merchandise. |
UNWANTED_MERCHANDISE |
The user was charged for and received merchandise they did not order. |
UNCLEAR |
Missing or unclear signal. This should be used when the reason is unknown. |
OTHER |
Other reasons that are not relevant as risk is concerned. Should be used if the reason is known but does not fit in a currently defined reason. |
TRANSACTION_AMOUNT_DIFFER |
The amount that was charged to the user was not the amount they expected. |
PAID_BY_OTHER_MEANS |
The user was charged for a transaction that they had already paid for by some other means, such as a different instrument. |
LATE_PRESENTMENT |
The transaction was not submitted in time for processing. |
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-07-29 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-29 UTC."],[[["\u003cp\u003eThis documentation outlines the various reasons for payment disputes or issues.\u003c/p\u003e\n"],["\u003cp\u003eEach reason is represented by a unique code (enum) for categorization and analysis.\u003c/p\u003e\n"],["\u003cp\u003eThese codes help in identifying the nature of a dispute, like fraud, unrecognized charges, or delivery problems.\u003c/p\u003e\n"],["\u003cp\u003e"UNCLEAR" should be used when the reason for the issue is unknown, while "OTHER" is for known reasons not fitting existing categories.\u003c/p\u003e\n"],["\u003cp\u003eThese enums ultimately aid in risk assessment and resolution of payment-related concerns.\u003c/p\u003e\n"]]],["The document outlines a set of enumerated values (enums) representing various reasons for transaction issues. Key actions include identifying specific transaction problems such as `FRAUD`, `DUPLICATE_PAYMENT`, `SUBSCRIPTION_CANCELED`, or `NOT_DELIVERED`. Other enums relate to user errors like `INPUT_ERROR` and `INSUFFICIENT_FUNDS`. `UNCLEAR` and `OTHER` are used for unknown or undefined reasons. It is not allowed to use `UNKNOWN_REASON`. Additionally, issues like `TRANSACTION_AMOUNT_DIFFER` and `LATE_PRESENTMENT` are included.\n"],null,["# PaymentDisputeReasonCode\n\nReason code for disputed transaction.\n\n| Enums ||\n|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|\n| `UNKNOWN_REASON` | Do not ever set this default value! |\n| `FRAUD` | Fraudulent transaction. |\n| `FAMILIAR_FRAUD` | Fraudulent transaction made by a family member, friend, or member of the household. |\n| `SUSPICIOUS` | Suspicious transaction. |\n| `CHARGE_NOT_RECOGNIZED` | The user does not recognize the charge on their bill. |\n| `CREDIT_NOT_PROCESSED` | The user was told they would get a refund but they never got it. |\n| `DUPLICATE_PAYMENT` | The user was charged twice for the same purchase. |\n| `SUBSCRIPTION_CANCELED` | The user canceled a subscription but was still charged. |\n| `INPUT_ERROR` | User input error. |\n| `INSUFFICIENT_FUNDS` | User didn't have sufficient funds. |\n| `NOT_DELIVERED` | Item was never delivered. |\n| `DEFECTIVE_OR_NOT_AS_DESCRIBED` | Merchandise was defective or not as described. |\n| `INCORRECT_MERCHANDISE` | The user received the wrong merchandise. |\n| `UNWANTED_MERCHANDISE` | The user was charged for and received merchandise they did not order. |\n| `UNCLEAR` | Missing or unclear signal. This should be used when the reason is unknown. |\n| `OTHER` | Other reasons that are not relevant as risk is concerned. Should be used if the reason is known but does not fit in a currently defined reason. |\n| `TRANSACTION_AMOUNT_DIFFER` | The amount that was charged to the user was not the amount they expected. |\n| `PAID_BY_OTHER_MEANS` | The user was charged for a transaction that they had already paid for by some other means, such as a different instrument. |\n| `LATE_PRESENTMENT` | The transaction was not submitted in time for processing. |"]]