1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
use serde::{Serialize, Deserialize};
use super::{
TransferAuthorizationDecision, TransferAuthorizationDecisionRationaleCode,
WebhookEnvironmentValues,
};
///Fired when Plaid is unable to originate a new ACH transaction of the recurring transfer on the planned date.
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct RecurringTransferSkippedWebhook {
/**A decision regarding the proposed transfer.
`approved` – The proposed transfer has received the end user's consent and has been approved for processing by Plaid. The `decision_rationale` field is set if Plaid was unable to fetch the account information. You may proceed with the transfer, but further review is recommended. Refer to the `code` field in the `decision_rationale` object for details.
`declined` – Plaid reviewed the proposed transfer and declined processing. Refer to the `code` field in the `decision_rationale` object for details.
`user_action_required` – An action is required before Plaid can assess the transfer risk and make a decision. The most common scenario is to update authentication for an Item. To complete the required action, initialize Link by setting `transfer.authorization_id` in the request of `/link/token/create`. After Link flow is completed, you may re-attempt the authorization request.*/
pub authorization_decision: TransferAuthorizationDecision,
/**A code representing the rationale for approving or declining the proposed transfer.
If the `rationale_code` is `null`, the transfer passed the authorization check.
Any non-`null` value for an `approved` transfer indicates that the the authorization check could not be run and that you should perform your own risk assessment on the transfer. The code will indicate why the check could not be run. Possible values for an `approved` transfer are:
`MANUALLY_VERIFIED_ITEM` – Item created via a manual entry flow (i.e. Same Day Micro-deposit, Instant Micro-deposit, Database Insights, or Database Match), limited information available.
`ITEM_LOGIN_REQUIRED` – Unable to collect the account information due to Item staleness. Can be resolved by using Link and setting [`transfer.authorization_id`](https://plaid.com/docs/api/link/#link-token-create-request-transfer-authorization-id) in the request to `/link/token/create`.
`MIGRATED_ACCOUNT_ITEM` - Item created via `/transfer/migrate_account` endpoint, limited information available.
`ERROR` – Unable to collect the account information due to an unspecified error.
The following codes indicate that the authorization decision was `declined`:
`NSF` – Transaction likely to result in a return due to insufficient funds.
`RISK` - Transaction is high-risk.
`TRANSFER_LIMIT_REACHED` - One or several transfer limits are reached, e.g. monthly transfer limit. Check the accompanying `description` field to understand which limit has been reached.*/
#[serde(default, skip_serializing_if = "Option::is_none")]
pub authorization_decision_rationale_code: Option<
TransferAuthorizationDecisionRationaleCode,
>,
///The Plaid environment the webhook was sent from
pub environment: WebhookEnvironmentValues,
///Plaid’s unique identifier for a recurring transfer.
pub recurring_transfer_id: String,
///The planned date on which Plaid is unable to originate a new ACH transaction of the recurring transfer. This will be of the form YYYY-MM-DD.
pub skipped_origination_date: chrono::NaiveDate,
///`RECURRING_TRANSFER_SKIPPED`
pub webhook_code: String,
///`TRANSFER`
pub webhook_type: String,
}
impl std::fmt::Display for RecurringTransferSkippedWebhook {
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> Result<(), std::fmt::Error> {
write!(f, "{}", serde_json::to_string(self).unwrap())
}
}