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
use serde::{Serialize, Deserialize};
/**To top up your Stripe balance, you create a top-up object. You can retrieve
individual top-ups, as well as list all top-ups. Top-ups are identified by a
unique, random ID.
Related guide: [Topping up your platform account](https://stripe.com/docs/connect/top-ups)*/
#[derive(Debug, Clone, Serialize, Deserialize, Default)]
pub struct Topup {
///Amount transferred.
pub amount: i64,
///ID of the balance transaction that describes the impact of this top-up on your account balance. May not be specified depending on status of top-up.
#[serde(skip_serializing_if = "Option::is_none")]
pub balance_transaction: Option<serde_json::Value>,
///Time at which the object was created. Measured in seconds since the Unix epoch.
pub created: i64,
///Three-letter [ISO currency code](https://www.iso.org/iso-4217-currency-codes.html), in lowercase. Must be a [supported currency](https://stripe.com/docs/currencies).
pub currency: String,
///An arbitrary string attached to the object. Often useful for displaying to users.
#[serde(skip_serializing_if = "Option::is_none")]
pub description: Option<String>,
///Date the funds are expected to arrive in your Stripe account for payouts. This factors in delays like weekends or bank holidays. May not be specified depending on status of top-up.
#[serde(skip_serializing_if = "Option::is_none")]
pub expected_availability_date: Option<i64>,
///Error code explaining reason for top-up failure if available (see [the errors section](https://stripe.com/docs/api#errors) for a list of codes).
#[serde(skip_serializing_if = "Option::is_none")]
pub failure_code: Option<String>,
///Message to user further explaining reason for top-up failure if available.
#[serde(skip_serializing_if = "Option::is_none")]
pub failure_message: Option<String>,
///Unique identifier for the object.
pub id: String,
///Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode.
pub livemode: bool,
///Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
pub metadata: serde_json::Value,
///String representing the object's type. Objects of the same type share the same value.
pub object: String,
///The source field is deprecated. It might not always be present in the API response.
#[serde(skip_serializing_if = "Option::is_none")]
pub source: Option<serde_json::Value>,
///Extra information about a top-up. This will appear on your source's bank statement. It must contain at least one letter.
#[serde(skip_serializing_if = "Option::is_none")]
pub statement_descriptor: Option<String>,
///The status of the top-up is either `canceled`, `failed`, `pending`, `reversed`, or `succeeded`.
pub status: String,
///A string that identifies this top-up as part of a group.
#[serde(skip_serializing_if = "Option::is_none")]
pub transfer_group: Option<String>,
}
impl std::fmt::Display for Topup {
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> Result<(), std::fmt::Error> {
write!(f, "{}", serde_json::to_string(self).unwrap())
}
}