AS1024/itflow
1
0
Fork 0
mirror of https://github.com/itflow-org/itflow synced 2026-03-12 08:44:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Bump stripe-php from 19.0.0 to 19.4.1

Browse Source
This commit is contained in:
johnnyq
2026-03-07 17:19:48 -05:00
parent 11ba077726
commit 526fa1aff5
228 changed files with 3494 additions and 1049 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
plugins/stripe-php/lib/Token.php
View File

@@ -9,7 +9,7 @@ namespace Stripe;
* 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
* <a href="https://stripe.com/docs/payments">recommended payments integrations</a> to perform this process
* <a href="https://docs.stripe.com/payments">recommended payments integrations</a> 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.
*
@@ -21,15 +21,15 @@ namespace Stripe;
* 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 <a href="https://stripe.com/docs/api#customers">Customer</a>
* information for later use, create <a href="https://docs.stripe.com/api#customers">Customer</a>
* objects or <a href="/api#external_accounts">External accounts</a>.
* <a href="https://stripe.com/docs/radar">Radar</a>, our integrated solution for automatic fraud protection,
* <a href="https://docs.stripe.com/radar">Radar</a>, our integrated solution for automatic fraud protection,
* performs best with integrations that use client-side tokenization.
*
* @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 null|BankAccount $bank_account <p>These bank accounts are payment methods on <code>Customer</code> objects.</p><p>On the other hand <a href="/api#external_accounts">External Accounts</a> are transfer destinations on <code>Account</code> objects for connected accounts. They can be bank accounts or debit cards as well, and are documented in the links above.</p><p>Related guide: <a href="/payments/bank-debits-transfers">Bank debits and transfers</a></p>
* @property null|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|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://docs.stripe.com/sources/cards">Card payments with Sources</a></p>
* @property null|string $client_ip IP address of the client that generates 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.