pub struct Card {Show 33 fields
pub account: Option<Expandable<Account>>,
pub address_city: Option<String>,
pub address_country: Option<String>,
pub address_line1: Option<String>,
pub address_line1_check: Option<String>,
pub address_line2: Option<String>,
pub address_state: Option<String>,
pub address_zip: Option<String>,
pub address_zip_check: Option<String>,
pub allow_redisplay: Option<CardAllowRedisplay>,
pub available_payout_methods: Option<Vec<CardAvailablePayoutMethods>>,
pub brand: String,
pub country: Option<String>,
pub currency: Option<Currency>,
pub customer: Option<Expandable<Customer>>,
pub cvc_check: Option<String>,
pub default_for_currency: Option<bool>,
pub description: Option<String>,
pub dynamic_last4: Option<String>,
pub exp_month: i64,
pub exp_year: i64,
pub fingerprint: Option<String>,
pub funding: String,
pub id: CardId,
pub iin: Option<String>,
pub issuer: Option<String>,
pub last4: String,
pub metadata: Option<HashMap<String, String>>,
pub name: Option<String>,
pub networks: Option<TokenCardNetworks>,
pub regulated_status: Option<CardRegulatedStatus>,
pub status: Option<String>,
pub tokenization_method: Option<String>,
}Expand description
You can store multiple cards on a customer in order to charge the customer later. You can also store multiple debit cards on a recipient in order to transfer to those cards later.
Related guide: Card payments with Sources
For more details see <https://stripe.com/docs/api/cards/object>.
Fields§
§account: Option<Expandable<Account>>§address_city: Option<String>City/District/Suburb/Town/Village.
address_country: Option<String>Billing address country, if provided when creating card.
address_line1: Option<String>Address line 1 (Street address/PO Box/Company name).
address_line1_check: Option<String>If address_line1 was provided, results of the check: pass, fail, unavailable, or unchecked.
address_line2: Option<String>Address line 2 (Apartment/Suite/Unit/Building).
address_state: Option<String>State/County/Province/Region.
address_zip: Option<String>ZIP or postal code.
address_zip_check: Option<String>If address_zip was provided, results of the check: pass, fail, unavailable, or unchecked.
allow_redisplay: Option<CardAllowRedisplay>This field indicates whether this payment method can be shown again to its customer in a checkout flow. Stripe products such as Checkout and Elements use this field to determine whether a payment method can be shown as a saved payment method in a checkout flow. The field defaults to “unspecified”.
available_payout_methods: Option<Vec<CardAvailablePayoutMethods>>A set of available payout methods for this card.
Only values from this set should be passed as the method when creating a payout.
brand: StringCard brand.
Can be American Express, Diners Club, Discover, Eftpos Australia, Girocard, JCB, MasterCard, UnionPay, Visa, or Unknown.
country: Option<String>Two-letter ISO code representing the country of the card. You could use this attribute to get a sense of the international breakdown of cards you’ve collected.
currency: Option<Currency>Three-letter ISO code for currency in lowercase.
Must be a supported currency.
Only applicable on accounts (not customers or recipients).
The card can be used as a transfer destination for funds in this currency.
This property is only available when returned as an External Account where controller.is_controller is true.
customer: Option<Expandable<Customer>>The customer that this card belongs to. This attribute will not be in the card object if the card belongs to an account or recipient instead.
cvc_check: Option<String>If a CVC was provided, results of the check: pass, fail, unavailable, or unchecked.
A result of unchecked indicates that CVC was provided but hasn’t been checked yet.
Checks are typically performed when attaching a card to a Customer object, or when creating a charge.
For more details, see Check if a card is valid without a charge.
default_for_currency: Option<bool>Whether this card is the default external account for its currency.
This property is only available for accounts where controller.requirement_collection is application, which includes Custom accounts.
description: Option<String>A high-level description of the type of cards issued in this range. (For internal use only and not typically available in standard API requests.).
dynamic_last4: Option<String>(For tokenized numbers only.) The last four digits of the device account number.
exp_month: i64Two-digit number representing the card’s expiration month.
exp_year: i64Four-digit number representing the card’s expiration year.
fingerprint: Option<String>Uniquely identifies this particular card number. You can use this attribute to check whether two customers who’ve signed up with you are using the same card number, for example. For payment methods that tokenize card information (Apple Pay, Google Pay), the tokenized number might be provided instead of the underlying card number.
As of May 1, 2021, card fingerprint in India for Connect changed to allow two fingerprints for the same card—one for India and one for the rest of the world..
funding: StringCard funding type. Can be credit, debit, prepaid, or unknown.
id: CardIdUnique identifier for the object.
iin: Option<String>Issuer identification number of the card. (For internal use only and not typically available in standard API requests.).
issuer: Option<String>The name of the card’s issuing bank. (For internal use only and not typically available in standard API requests.).
last4: StringThe last four digits of the card.
metadata: Option<HashMap<String, String>>Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
name: Option<String>Cardholder name.
networks: Option<TokenCardNetworks>§regulated_status: Option<CardRegulatedStatus>Status of a card based on the card issuer.
status: Option<String>For external accounts that are cards, possible values are new and errored.
If a payout fails, the status is set to errored and scheduled payouts are stopped until account details are updated.
tokenization_method: Option<String>If the card number is tokenized, this is the method that was used.
Can be android_pay (includes Google Pay), apple_pay, masterpass, visa_checkout, or null.