FM / lib

/home/techb158/ileadtechnology.com/SSM/vendor/stripe/stripe-php/lib/

/home/techb158/ileadtechnology.com/SSM/vendor/stripe/stripe-php/lib

Name	Size	Mode	Actions
ApiOperations/	-	0755	rm
BillingPortal/	-	0755	rm
Checkout/	-	0755	rm
Exception/	-	0755	rm
HttpClient/	-	0755	rm
Issuing/	-	0755	rm
Radar/	-	0755	rm
Reporting/	-	0755	rm
Sigma/	-	0755	rm
Terminal/	-	0755	rm
Util/	-	0755	rm
Account.php	16166	0644	edit dl rm
AccountLink.php	789	0644	edit dl rm
AlipayAccount.php	2386	0644	edit dl rm
ApiRequestor.php	14711	0644	edit dl rm
ApiResource.php	3448	0644	edit dl rm
ApiResponse.php	712	0644	edit dl rm
ApplePayDomain.php	975	0644	edit dl rm
ApplicationFee.php	4162	0644	edit dl rm
ApplicationFeeRefund.php	2406	0644	edit dl rm
Balance.php	2173	0644	edit dl rm
BalanceTransaction.php	5375	0644	edit dl rm
BankAccount.php	6797	0644	edit dl rm
BitcoinReceiver.php	4138	0644	edit dl rm
BitcoinTransaction.php	844	0644	edit dl rm
Capability.php	2898	0644	edit dl rm
Card.php	7813	0644	edit dl rm
Charge.php	12222	0644	edit dl rm
Collection.php	7165	0644	edit dl rm
CountrySpec.php	1743	0644	edit dl rm
Coupon.php	2841	0644	edit dl rm
CreditNote.php	5595	0644	edit dl rm
CreditNoteLineItem.php	1770	0644	edit dl rm
Customer.php	12581	0644	edit dl rm
CustomerBalanceTransaction.php	5244	0644	edit dl rm
Discount.php	298	0644	edit dl rm
Dispute.php	5103	0644	edit dl rm
EphemeralKey.php	1545	0644	edit dl rm
ErrorObject.php	8661	0644	edit dl rm
Event.php	11700	0644	edit dl rm
ExchangeRate.php	1405	0644	edit dl rm
File.php	3115	0644	edit dl rm
FileLink.php	1394	0644	edit dl rm
Invoice.php	18452	0644	edit dl rm
InvoiceItem.php	3556	0644	edit dl rm
InvoiceLineItem.php	2593	0644	edit dl rm
LoginLink.php	385	0644	edit dl rm
Mandate.php	1063	0644	edit dl rm
OAuth.php	3393	0644	edit dl rm
OAuthErrorObject.php	861	0644	edit dl rm
Order.php	5127	0644	edit dl rm
OrderItem.php	333	0644	edit dl rm
OrderReturn.php	1648	0644	edit dl rm
PaymentIntent.php	10945	0644	edit dl rm
PaymentMethod.php	3082	0644	edit dl rm
Payout.php	5949	0644	edit dl rm
Person.php	4489	0644	edit dl rm
Plan.php	4883	0644	edit dl rm
Product.php	3976	0644	edit dl rm
Recipient.php	2841	0644	edit dl rm
RecipientTransfer.php	918	0644	edit dl rm
Refund.php	4042	0644	edit dl rm
RequestTelemetry.php	539	0644	edit dl rm
Review.php	3330	0644	edit dl rm
SetupIntent.php	6992	0644	edit dl rm
SingletonApiResource.php	917	0644	edit dl rm
SKU.php	2793	0644	edit dl rm
Source.php	8477	0644	edit dl rm
SourceTransaction.php	408	0644	edit dl rm
Stripe.php	7224	0644	edit dl rm
StripeObject.php	18869	0644	edit dl rm
Subscription.php	10559	0644	edit dl rm
SubscriptionItem.php	3997	0644	edit dl rm
SubscriptionSchedule.php	3749	0644	edit dl rm
TaxId.php	3895	0644	edit dl rm
TaxRate.php	1818	0644	edit dl rm
ThreeDSecure.php	2565	0644	edit dl rm
Token.php	3590	0644	edit dl rm
Topup.php	3903	0644	edit dl rm
Transfer.php	6229	0644	edit dl rm
TransferReversal.php	3226	0644	edit dl rm
UsageRecord.php	938	0644	edit dl rm
UsageRecordSummary.php	771	0644	edit dl rm
Webhook.php	1515	0644	edit dl rm
WebhookEndpoint.php	2219	0644	edit dl rm
WebhookSignature.php	4380	0644	edit dl rm

Edit: /home/techb158/ileadtechnology.com/SSM/vendor/stripe/stripe-php/lib/SetupIntent.php (6992B)

<?php

namespace Stripe;

/**
 * A SetupIntent guides you through the process of setting up and saving a
 * customer's payment credentials for future payments. For example, you could use a
 * SetupIntent to set up and save your customer's card without immediately
 * collecting a payment. Later, you can use <a
 * href="https://stripe.com/docs/api#payment_intents">PaymentIntents</a> to drive
 * the payment flow.
 *
 * Create a SetupIntent as soon as you're ready to collect your customer's payment
 * credentials. Do not maintain long-lived, unconfirmed SetupIntents as they may no
 * longer be valid. The SetupIntent then transitions through multiple <a
 * href="https://stripe.com/docs/payments/intents#intent-statuses">statuses</a> as
 * it guides you through the setup process.
 *
 * Successful SetupIntents result in payment credentials that are optimized for
 * future payments. For example, cardholders in <a
 * href="/guides/strong-customer-authentication">certain regions</a> may need to be
 * run through <a
 * href="https://stripe.com/docs/strong-customer-authentication">Strong Customer
 * Authentication</a> at the time of payment method collection in order to
 * streamline later <a
 * href="https://stripe.com/docs/payments/setup-intents">off-session payments</a>.
 * If the SetupIntent is used with a <a
 * href="https://stripe.com/docs/api#setup_intent_object-customer">Customer</a>,
 * upon success, it will automatically attach the resulting payment method to that
 * Customer. We recommend using SetupIntents or <a
 * href="https://stripe.com/docs/api#payment_intent_object-setup_future_usage">setup_future_usage</a>
 * on PaymentIntents to save payment methods in order to prevent saving invalid or
 * unoptimized payment methods.
 *
 * By using SetupIntents, you ensure that your customers experience the minimum set
 * of required friction, even as regulations change over time.
 *
 * Related guide: <a href="https://stripe.com/docs/payments/setup-intents">Setup
 * Intents API</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 null|string|\Stripe\StripeObject $application ID of the Connect application that created the SetupIntent.
 * @property null|string $cancellation_reason Reason for cancellation of this SetupIntent, one of <code>abandoned</code>, <code>requested_by_customer</code>, or <code>duplicate</code>.
 * @property null|string $client_secret The client secret of this SetupIntent. Used for client-side retrieval using a publishable key.The client secret can be used to complete payment setup from your frontend. It should not be stored, logged, embedded in URLs, or exposed to anyone other than the customer. Make sure that you have TLS enabled on any page that includes the client secret.
 * @property int $created Time at which the object was created. Measured in seconds since the Unix epoch.
 * @property null|string|\Stripe\Customer $customer ID of the Customer this SetupIntent belongs to, if one exists.If present, the SetupIntent's payment method will be attached to the Customer on successful setup. Payment methods attached to other Customers cannot be used with this SetupIntent.
 * @property null|string $description An arbitrary string attached to the object. Often useful for displaying to users.
 * @property null|\Stripe\ErrorObject $last_setup_error The error encountered in the previous SetupIntent confirmation.
 * @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 null|string|\Stripe\Mandate $mandate ID of the multi use Mandate generated by the SetupIntent.
 * @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 null|\Stripe\StripeObject $next_action If present, this property tells you what actions you need to take in order for your customer to continue payment setup.
 * @property null|string|\Stripe\Account $on_behalf_of The account (if any) for which the setup is intended.
 * @property null|string|\Stripe\PaymentMethod $payment_method ID of the payment method used with this SetupIntent.
 * @property null|\Stripe\StripeObject $payment_method_options Payment-method-specific configuration for this SetupIntent.
 * @property string[] $payment_method_types The list of payment method types (e.g. card) that this SetupIntent is allowed to set up.
 * @property null|string|\Stripe\Mandate $single_use_mandate ID of the single_use Mandate generated by the SetupIntent.
 * @property string $status <a href="https://stripe.com/docs/payments/intents#intent-statuses">Status</a> of this SetupIntent, one of <code>requires_payment_method</code>, <code>requires_confirmation</code>, <code>requires_action</code>, <code>processing</code>, <code>canceled</code>, or <code>succeeded</code>.
 * @property string $usage Indicates how the payment method is intended to be used in the future.Use <code>on_session</code> if you intend to only reuse the payment method when the customer is in your checkout flow. Use <code>off_session</code> if your customer may or may not be in your checkout flow. If not provided, this value defaults to <code>off_session</code>.
 */
class SetupIntent extends ApiResource
{
 const OBJECT_NAME = 'setup_intent';

use ApiOperations\All;
    use ApiOperations\Create;
    use ApiOperations\Retrieve;
    use ApiOperations\Update;

const STATUS_CANCELED = 'canceled';
    const STATUS_PROCESSING = 'processing';
    const STATUS_REQUIRES_ACTION = 'requires_action';
    const STATUS_REQUIRES_CONFIRMATION = 'requires_confirmation';
    const STATUS_REQUIRES_PAYMENT_METHOD = 'requires_payment_method';
    const STATUS_SUCCEEDED = 'succeeded';

/**
     * @param null|array $params
     * @param null|array|string $opts
     *
     * @throws \Stripe\Exception\ApiErrorException if the request fails
     *
     * @return SetupIntent the canceled setup intent
     */
    public function cancel($params = null, $opts = null)
    {
        $url = $this->instanceUrl() . '/cancel';
        list($response, $opts) = $this->_request('post', $url, $params, $opts);
        $this->refreshFrom($response, $opts);

return $this;
    }

/**
     * @param null|array $params
     * @param null|array|string $opts
     *
     * @throws \Stripe\Exception\ApiErrorException if the request fails
     *
     * @return SetupIntent the confirmed setup intent
     */
    public function confirm($params = null, $opts = null)
    {
        $url = $this->instanceUrl() . '/confirm';
        list($response, $opts) = $this->_request('post', $url, $params, $opts);
        $this->refreshFrom($response, $opts);

return $this;
    }
}

PaymentIntents to drive * the payment flow. * * Create a SetupIntent as soon as you're ready to collect your customer's payment * credentials. Do not maintain long-lived, unconfirmed SetupIntents as they may no * longer be valid. The SetupIntent then transitions through multiple statuses as * it guides you through the setup process. * * Successful SetupIntents result in payment credentials that are optimized for * future payments. For example, cardholders in certain regions may need to be * run through Strong Customer * Authentication at the time of payment method collection in order to * streamline later off-session payments. * If the SetupIntent is used with a Customer, * upon success, it will automatically attach the resulting payment method to that * Customer. We recommend using SetupIntents or setup_future_usage * on PaymentIntents to save payment methods in order to prevent saving invalid or * unoptimized payment methods. * * By using SetupIntents, you ensure that your customers experience the minimum set * of required friction, even as regulations change over time. * * Related guide: Setup * Intents API. * * @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|string|\Stripe\StripeObject $application ID of the Connect application that created the SetupIntent. * @property null|string $cancellation_reason Reason for cancellation of this SetupIntent, one of abandoned, requested_by_customer, or duplicate. * @property null|string $client_secret

The client secret of this SetupIntent. Used for client-side retrieval using a publishable key.

The client secret can be used to complete payment setup from your frontend. It should not be stored, logged, embedded in URLs, or exposed to anyone other than the customer. Make sure that you have TLS enabled on any page that includes the client secret.

* @property int $created Time at which the object was created. Measured in seconds since the Unix epoch. * @property null|string|\Stripe\Customer $customer

ID of the Customer this SetupIntent belongs to, if one exists.

If present, the SetupIntent's payment method will be attached to the Customer on successful setup. Payment methods attached to other Customers cannot be used with this SetupIntent.

* @property null|string $description An arbitrary string attached to the object. Often useful for displaying to users. * @property null|\Stripe\ErrorObject $last_setup_error The error encountered in the previous SetupIntent confirmation. * @property bool $livemode Has the value true if the object exists in live mode or the value false if the object exists in test mode. * @property null|string|\Stripe\Mandate $mandate ID of the multi use Mandate generated by the SetupIntent. * @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 null|\Stripe\StripeObject $next_action If present, this property tells you what actions you need to take in order for your customer to continue payment setup. * @property null|string|\Stripe\Account $on_behalf_of The account (if any) for which the setup is intended. * @property null|string|\Stripe\PaymentMethod $payment_method ID of the payment method used with this SetupIntent. * @property null|\Stripe\StripeObject $payment_method_options Payment-method-specific configuration for this SetupIntent. * @property string[] $payment_method_types The list of payment method types (e.g. card) that this SetupIntent is allowed to set up. * @property null|string|\Stripe\Mandate $single_use_mandate ID of the single_use Mandate generated by the SetupIntent. * @property string $status Status of this SetupIntent, one of requires_payment_method, requires_confirmation, requires_action, processing, canceled, or succeeded. * @property string $usage

Indicates how the payment method is intended to be used in the future.

Use on_session if you intend to only reuse the payment method when the customer is in your checkout flow. Use off_session if your customer may or may not be in your checkout flow. If not provided, this value defaults to off_session.

*/ class SetupIntent extends ApiResource { const OBJECT_NAME = 'setup_intent'; use ApiOperations\All; use ApiOperations\Create; use ApiOperations\Retrieve; use ApiOperations\Update; const STATUS_CANCELED = 'canceled'; const STATUS_PROCESSING = 'processing'; const STATUS_REQUIRES_ACTION = 'requires_action'; const STATUS_REQUIRES_CONFIRMATION = 'requires_confirmation'; const STATUS_REQUIRES_PAYMENT_METHOD = 'requires_payment_method'; const STATUS_SUCCEEDED = 'succeeded'; /** * @param null|array $params * @param null|array|string $opts * * @throws \Stripe\Exception\ApiErrorException if the request fails * * @return SetupIntent the canceled setup intent */ public function cancel($params = null, $opts = null) { $url = $this->instanceUrl() . '/cancel'; list($response, $opts) = $this->_request('post', $url, $params, $opts); $this->refreshFrom($response, $opts); return $this; } /** * @param null|array $params * @param null|array|string $opts * * @throws \Stripe\Exception\ApiErrorException if the request fails * * @return SetupIntent the confirmed setup intent */ public function confirm($params = null, $opts = null) { $url = $this->instanceUrl() . '/confirm'; list($response, $opts) = $this->_request('post', $url, $params, $opts); $this->refreshFrom($response, $opts); return $this; } }