pub struct Token {
pub bank_account: Option<BankAccount>,
pub card: Option<Card>,
pub client_ip: Option<String>,
pub created: Timestamp,
pub id: TokenId,
pub livemode: bool,
pub type_: String,
pub used: bool,
}
Expand description
Tokenization is the process Stripe uses to collect sensitive card or bank account details, or personally identifiable information (PII), directly from your customers in a secure manner. A token representing this information is returned to your server to use. Use our recommended payments integrations to perform this process on the client-side. This guarantees that no sensitive card data touches your server, and allows your integration to operate in a PCI-compliant way.
If you can’t use client-side tokenization, you can also create tokens using the API with either your publishable or secret API key. If your integration uses this method, you’re responsible for any PCI compliance that it might require, and you must keep your secret API key safe. Unlike with client-side tokenization, your customer’s information isn’t sent directly to Stripe, so we can’t determine how it’s handled or stored.
You can’t store or use tokens more than once. To store card or bank account information for later use, create Customer objects or External accounts. Radar, our integrated solution for automatic fraud protection, performs best with integrations that use client-side tokenization.
For more details see <https://stripe.com/docs/api/tokens/object>.
Fields§
§bank_account: Option<BankAccount>
§card: Option<Card>
§client_ip: Option<String>
IP address of the client that generates the token.
created: Timestamp
Time at which the object was created. Measured in seconds since the Unix epoch.
id: TokenId
Unique identifier for the object.
livemode: bool
Has the value true
if the object exists in live mode or the value false
if the object exists in test mode.
type_: String
Type of the token: account
, bank_account
, card
, or pii
.
used: bool
Determines if you have already used this token (you can only use tokens once).