Charge object. You can
- * retrieve and refund individual charges as well as list all charges. Charges
- * are identified by a unique, random ID.
- *
- * Related guide: Accept a payment with the Charges API
+ * The Charge object represents a single attempt to move money into your Stripe account.
+ * PaymentIntent confirmation is the most common way to create Charges, but transferring
+ * money to a different Stripe account through Connect also creates Charges.
+ * Some legacy payment flows create Charges directly, which is not recommended for new integrations.
*
* @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.
diff --git a/lib/Issuing/Cardholder.php b/lib/Issuing/Cardholder.php
index 31e55bc64..aac314a30 100644
--- a/lib/Issuing/Cardholder.php
+++ b/lib/Issuing/Cardholder.php
@@ -20,6 +20,7 @@
* @property \Stripe\StripeObject $metadata 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.
* @property string $name The cardholder's name. This will be printed on cards issued to them.
* @property null|string $phone_number The cardholder's phone number. This is required for all cardholders who will be creating EU cards. See the 3D Secure documentation for more details.
+ * @property null|string[] $preferred_locales The cardholder’s preferred locales (languages), ordered by preference. Locales can be de, en, es, fr, or it. This changes the language of the 3D Secure flow and one-time password messages sent to the cardholder.
* @property \Stripe\StripeObject $requirements
* @property null|\Stripe\StripeObject $spending_controls Rules that control spending across this cardholder's cards. Refer to our documentation for more details.
* @property string $status Specifies whether to permit authorizations on this cardholder's cards.
diff --git a/lib/LoginLink.php b/lib/LoginLink.php
index 3351356b8..e06930c71 100644
--- a/lib/LoginLink.php
+++ b/lib/LoginLink.php
@@ -5,6 +5,8 @@
namespace Stripe;
/**
+ * Login Links are single-use login link for an Express account to access their Stripe dashboard.
+ *
* @property string $object String representing the object's type. Objects of the same type share the same value.
* @property int $created Time at which the object was created. Measured in seconds since the Unix epoch.
* @property string $url The URL for the login link.
diff --git a/lib/Service/ChargeService.php b/lib/Service/ChargeService.php
index 0bde02792..4f6490289 100644
--- a/lib/Service/ChargeService.php
+++ b/lib/Service/ChargeService.php
@@ -23,14 +23,15 @@ public function all($params = null, $opts = null)
}
/**
- * Capture the payment of an existing, uncaptured, charge. This is the second half
- * of the two-step payment flow, where first you created a
- * charge with the capture option set to false.
+ * Capture the payment of an existing, uncaptured charge that was created with the
+ * capture option set to false.
*
* Uncaptured payments expire a set number of days after they are created (7 by default). If they are not captured
- * by that point in time, they will be marked as refunded and will no longer be
- * capturable.
+ * href="/docs/charges/placing-a-hold">7 by default), after which they are
+ * marked as refunded and capture attempts will fail.
+ *
+ * Don’t use this method to capture a PaymentIntent-initiated charge. Use Capture a PaymentIntent.
*
* @param string $id
* @param null|array $params
@@ -46,11 +47,10 @@ public function capture($id, $params = null, $opts = null)
}
/**
- * To charge a credit card or other payment source, you create a
- * Charge object. If your API key is in test mode, the supplied
- * payment source (e.g., card) won’t actually be charged, although everything else
- * will occur as if in live mode. (Stripe assumes that the charge would have
- * completed successfully).
+ * Use the Payment Intents API to initiate
+ * a new payment instead of using this method. Confirmation of the PaymentIntent
+ * creates the Charge object used to request payment, so this method
+ * is limited to legacy integrations.
*
* @param null|array $params
* @param null|array|\Stripe\Util\RequestOptions $opts
diff --git a/lib/Token.php b/lib/Token.php
index afc142369..2a2621d64 100644
--- a/lib/Token.php
+++ b/lib/Token.php
@@ -26,8 +26,6 @@
* Radar, our integrated solution for automatic fraud protection,
* performs best with integrations that use client-side tokenization.
*
- * Related guide: Accept a payment with Charges and Tokens
- *
* @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|\Stripe\BankAccount $bank_account These bank accounts are payment methods on Customer objects.
On the other hand External Accounts are transfer destinations on Account objects for Custom accounts. They can be bank accounts or debit cards as well, and are documented in the links above.
Related guide: Bank debits and transfers