Generated enums like AchPaymentAllOfAttributes.StatusEnum (and the identical pattern in BookPaymentAllOfAttributes.StatusEnum) use a @JsonCreator-annotated fromValue(String) factory method that throws IllegalArgumentException when the value isn't one of the enum's known constants:
@JsonCreator
public static StatusEnum fromValue(String value) {
for (StatusEnum b : StatusEnum.values()) {
if (b.value.equals(value)) {
return b;
}
}
throw new IllegalArgumentException("Unexpected value '" + value + "'");
}
Because this uses a custom @JsonCreator factory rather than Jackson's built-in enum-by-name resolution, standard Jackson leniency options (e.g. DeserializationFeature.READ_UNKNOWN_ENUM_VALUES_AS_NULL) have no effect — the factory method's exception propagates regardless, surfacing as a ValueInstantiationException that fails deserialization of the entire response object, not just the one field.
Observed in practice: the API returned a payment status of 'PendingReview', which isn't present in StatusEnum (PENDING, REJECTED, CLEARING, SENT, CANCELED, RETURNED). This causes createPayment to throw even though the underlying HTTP response was a successful 2xx — the payment was created, but the client can never read its ID, status, or any other field from the response.
Generated enums like
AchPaymentAllOfAttributes.StatusEnum(and the identical pattern inBookPaymentAllOfAttributes.StatusEnum) use a @JsonCreator-annotated fromValue(String) factory method that throwsIllegalArgumentExceptionwhen the value isn't one of the enum's known constants:Because this uses a custom
@JsonCreatorfactory rather than Jackson's built-in enum-by-name resolution, standard Jackson leniency options (e.g.DeserializationFeature.READ_UNKNOWN_ENUM_VALUES_AS_NULL) have no effect — the factory method's exception propagates regardless, surfacing as a ValueInstantiationException that fails deserialization of the entire response object, not just the one field.Observed in practice: the API returned a payment status of 'PendingReview', which isn't present in StatusEnum
(PENDING, REJECTED, CLEARING, SENT, CANCELED, RETURNED). This causes createPayment to throw even though the underlying HTTP response was a successful 2xx — the payment was created, but the client can never read its ID, status, or any other field from the response.