1 files changed, 57 insertions, 0 deletions
diff --git a/vendor/stripe/stripe-php/lib/Token.php b/vendor/stripe/stripe-php/lib/Token.php
new file mode 100644
index 0000000..18b33e8
--- /dev/null
+++ b/vendor/stripe/stripe-php/lib/Token.php
@@ -0,0 +1,57 @@
+<?php
+
+// File generated from our OpenAPI spec
+
+namespace Stripe;
+
+/**
+ * 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. You should use our <a
+ * href="https://stripe.com/docs/payments">recommended payments integrations</a> to
+ * perform this process client-side. This ensures that no sensitive card data
+ * touches your server, and allows your integration to operate in a PCI-compliant
+ * way.
+ *
+ * If you cannot use client-side tokenization, you can also create tokens using the
+ * API with either your publishable or secret API key. Keep in mind that if your
+ * integration uses this method, you are responsible for any PCI compliance that
+ * may be required, and you must keep your secret API key safe. Unlike with
+ * client-side tokenization, your customer's information is not sent directly to
+ * Stripe, so we cannot determine how it is handled or stored.
+ *
+ * Tokens cannot be stored or used more than once. To store card or bank account
+ * information for later use, you can create <a
+ * href="https://stripe.com/docs/api#customers">Customer</a> objects or <a
+ * href="https://stripe.com/docs/api#external_accounts">Custom accounts</a>. Note
+ * that <a href="https://stripe.com/docs/radar">Radar</a>, our integrated solution
+ * for automatic fraud protection, performs best with integrations that use
+ * client-side tokenization.
+ *
+ * Related guide: <a
+ * href="https://stripe.com/docs/payments/accept-a-payment-charges#web-create-token">Accept
+ * a payment</a>
+ *
+ * @property string $id Unique identifier for the object.
+ * @property string $object String representing the object's type. Objects of the same type share the same value.
+ * @property \Stripe\BankAccount $bank_account <p>These bank accounts are payment methods on <code>Customer</code> objects.</p><p>On the other hand <a href="https://stripe.com/docs/api#external_accounts">External Accounts</a> are transfer destinations on <code>Account</code> objects for <a href="https://stripe.com/docs/connect/custom-accounts">Custom accounts</a>. They can be bank accounts or debit cards as well, and are documented in the links above.</p><p>Related guide: <a href="https://stripe.com/docs/payments/bank-debits-transfers">Bank Debits and Transfers</a>.</p>
+ * @property \Stripe\Card $card <p>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.</p><p>Related guide: <a href="https://stripe.com/docs/sources/cards">Card Payments with Sources</a>.</p>
+ * @property null|string $client_ip IP address of the client that generated the token.
+ * @property int $created Time at which the object was created. Measured in seconds since the Unix epoch.
+ * @property bool $livemode Has the value <code>true</code> if the object exists in live mode or the value <code>false</code> if the object exists in test mode.
+ * @property string $type Type of the token: <code>account</code>, <code>bank_account</code>, <code>card</code>, or <code>pii</code>.
+ * @property bool $used Whether this token has already been used (tokens can be used only once).
+ */
+class Token extends ApiResource
+{
+    const OBJECT_NAME = 'token';
+
+    use ApiOperations\Create;
+    use ApiOperations\Retrieve;
+
+    const TYPE_ACCOUNT = 'account';
+    const TYPE_BANK_ACCOUNT = 'bank_account';
+    const TYPE_CARD = 'card';
+    const TYPE_PII = 'pii';
+}