Unhandled unsent verification_status in Plaid Ruby binding

[aanojima]

Description

I'm encountering an undocumented verification_status value of unsent in the response from the /accounts/get endpoint when using the Plaid Ruby binding. This status is not listed in the official Plaid API documentation for verification_status. As a result, it is unclear how this status should be interpreted, and the Ruby binding does not appear to explicitly handle it.

Steps to Reproduce

1. Initialize a Plaid client using the Plaid Ruby binding.
2. Call the /accounts/get endpoint to retrieve account details.
3. Observe the verification_status field in the response for an account.
4. Note that the value is unsent, which is not documented.

Expected Behavior

• The verification_status field should only contain documented values, or the documentation should be updated to include the unsent status.
• The Ruby binding should explicitly handle the unsent status, ensuring consistent behavior.

Actual Behavior

• The verification_status field contains an undocumented status value of unsent.
• This status is not handled explicitly in the Ruby binding, which may lead to unexpected behavior.

Environment

• Plaid Ruby binding version: 36.1.0
• Ruby version: 3.2.7

Additional Context

• This issue may impact logic that relies on handling specific verification statuses.
• If the unsent status is intentional, please clarify its meaning and add it to the official documentation.

[phoenixy1]

Thank you for reporting this! I believe this is a very uncommon state that was accidentally left out of the OpenAPI specification file -- I am working with the team to confirm that and add it now. The description of the state is:

unsent: The Item is pending micro-deposit verification, but Plaid has not yet sent the micro-deposit.

Assuming this is supposed to be in the API (which based on initial review of the code and feedback from the team, I think it is) we will add this in the next client library release.