#7087

pending completion

Build # #7087

Build Type

push

php-coveralls

Committed by

pakrym-stripe

Commit Message

Bump version to 10.14.0-beta.2

Run Details

1831 of 2732 relevant lines covered (67.02%)

3.81 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

66.67

/lib/SetupIntent.php

<?php

// File generated from our OpenAPI spec

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|bool $attach_to_self <p>If present, the SetupIntent's payment method will be attached to the in-context Stripe Account.</p><p>It can only be used for this Stripe Account’s own money movement flows like InboundTransfer and OutboundTransfers. It cannot be set to true when setting up a PaymentMethod for a Customer, and defaults to false when attaching a PaymentMethod to a Customer.</p>
 * @property null|\Stripe\StripeObject $automatic_payment_methods Settings for automatic payment methods compatible with this Setup Intent
 * @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 <p>The client secret of this SetupIntent. Used for client-side retrieval using a publishable key.</p><p>The client secret can be used to complete payment setup from your frontend. It should not be stored, logged, or exposed to anyone other than the customer. Make sure that you have TLS enabled on any page that includes the client secret.</p>
 * @property int $created Time at which the object was created. Measured in seconds since the Unix epoch.
 * @property null|string|\Stripe\Customer $customer <p>ID of the Customer this SetupIntent belongs to, if one exists.</p><p>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.</p>
 * @property null|string $description An arbitrary string attached to the object. Often useful for displaying to users.
 * @property null|string[] $flow_directions <p>Indicates the directions of money movement for which this payment method is intended to be used.</p><p>Include <code>inbound</code> if you intend to use the payment method as the origin to pull funds from. Include <code>outbound</code> if you intend to use the payment method as the destination to send funds to. You can include both if you intend to use the payment method for both purposes.</p>
 * @property null|\Stripe\StripeObject $last_setup_error The error encountered in the previous SetupIntent confirmation.
 * @property null|string|\Stripe\SetupAttempt $latest_attempt The most recent SetupAttempt for this SetupIntent.
 * @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 null|\Stripe\StripeObject $metadata Set of <a href="https://stripe.com/docs/api/metadata">key-value pairs</a> 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 <p>Indicates how the payment method is intended to be used in the future.</p><p>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>.</p>
 */
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 \Stripe\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 \Stripe\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;
    }

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

        return $this;
    }
}

1	<?php
2
3	// File generated from our OpenAPI spec
4
5	namespace Stripe;
6
7	/**
8	* A SetupIntent guides you through the process of setting up and saving a customer's payment credentials for future payments.
9	* For example, you could use a SetupIntent to set up and save your customer's card without immediately collecting a payment.
10	* Later, you can use <a href="https://stripe.com/docs/api#payment_intents">PaymentIntents</a> to drive the payment flow.
11	*
12	* Create a SetupIntent as soon as you're ready to collect your customer's payment credentials.
13	* Do not maintain long-lived, unconfirmed SetupIntents as they may no longer be valid.
14	* The SetupIntent then transitions through multiple <a href="https://stripe.com/docs/payments/intents#intent-statuses">statuses</a> as it guides
15	* you through the setup process.
16	*
17	* Successful SetupIntents result in payment credentials that are optimized for future payments.
18	* For example, cardholders in <a href="/guides/strong-customer-authentication">certain regions</a> may need to be run through
19	* <a href="https://stripe.com/docs/strong-customer-authentication">Strong Customer Authentication</a> at the time of payment method collection
20	* in order to streamline later <a href="https://stripe.com/docs/payments/setup-intents">off-session payments</a>.
21	* If the SetupIntent is used with a <a href="https://stripe.com/docs/api#setup_intent_object-customer">Customer</a>, upon success,
22	* it will automatically attach the resulting payment method to that Customer.
23	* We recommend using SetupIntents or <a href="https://stripe.com/docs/api#payment_intent_object-setup_future_usage">setup_future_usage</a> on
24	* PaymentIntents to save payment methods in order to prevent saving invalid or unoptimized payment methods.
25	*
26	* By using SetupIntents, you ensure that your customers experience the minimum set of required friction,
27	* even as regulations change over time.
28	*
29	* Related guide: <a href="https://stripe.com/docs/payments/setup-intents">Setup Intents API</a>
30	*
31	* @property string $id Unique identifier for the object.
32	* @property string $object String representing the object's type. Objects of the same type share the same value.
33	* @property null\|string\|\Stripe\StripeObject $application ID of the Connect application that created the SetupIntent.
34	* @property null\|bool $attach_to_self <p>If present, the SetupIntent's payment method will be attached to the in-context Stripe Account.</p><p>It can only be used for this Stripe Account’s own money movement flows like InboundTransfer and OutboundTransfers. It cannot be set to true when setting up a PaymentMethod for a Customer, and defaults to false when attaching a PaymentMethod to a Customer.</p>
35	* @property null\|\Stripe\StripeObject $automatic_payment_methods Settings for automatic payment methods compatible with this Setup Intent
36	* @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>.
37	* @property null\|string $client_secret <p>The client secret of this SetupIntent. Used for client-side retrieval using a publishable key.</p><p>The client secret can be used to complete payment setup from your frontend. It should not be stored, logged, or exposed to anyone other than the customer. Make sure that you have TLS enabled on any page that includes the client secret.</p>
38	* @property int $created Time at which the object was created. Measured in seconds since the Unix epoch.
39	* @property null\|string\|\Stripe\Customer $customer <p>ID of the Customer this SetupIntent belongs to, if one exists.</p><p>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.</p>
40	* @property null\|string $description An arbitrary string attached to the object. Often useful for displaying to users.
41	* @property null\|string[] $flow_directions <p>Indicates the directions of money movement for which this payment method is intended to be used.</p><p>Include <code>inbound</code> if you intend to use the payment method as the origin to pull funds from. Include <code>outbound</code> if you intend to use the payment method as the destination to send funds to. You can include both if you intend to use the payment method for both purposes.</p>
42	* @property null\|\Stripe\StripeObject $last_setup_error The error encountered in the previous SetupIntent confirmation.
43	* @property null\|string\|\Stripe\SetupAttempt $latest_attempt The most recent SetupAttempt for this SetupIntent.
44	* @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.
45	* @property null\|string\|\Stripe\Mandate $mandate ID of the multi use Mandate generated by the SetupIntent.
46	* @property null\|\Stripe\StripeObject $metadata Set of <a href="https://stripe.com/docs/api/metadata">key-value pairs</a> that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
47	* @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.
48	* @property null\|string\|\Stripe\Account $on_behalf_of The account (if any) for which the setup is intended.
49	* @property null\|string\|\Stripe\PaymentMethod $payment_method ID of the payment method used with this SetupIntent.
50	* @property null\|\Stripe\StripeObject $payment_method_options Payment-method-specific configuration for this SetupIntent.
51	* @property string[] $payment_method_types The list of payment method types (e.g. card) that this SetupIntent is allowed to set up.
52	* @property null\|string\|\Stripe\Mandate $single_use_mandate ID of the single_use Mandate generated by the SetupIntent.
53	* @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>.
54	* @property string $usage <p>Indicates how the payment method is intended to be used in the future.</p><p>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>.</p>
55	*/
56	class SetupIntent extends ApiResource
57	{
58	const OBJECT_NAME = 'setup_intent';
59
60	use ApiOperations\All;
61	use ApiOperations\Create;
62	use ApiOperations\Retrieve;
63	use ApiOperations\Update;
64
65	const STATUS_CANCELED = 'canceled';
66	const STATUS_PROCESSING = 'processing';
67	const STATUS_REQUIRES_ACTION = 'requires_action';
68	const STATUS_REQUIRES_CONFIRMATION = 'requires_confirmation';
69	const STATUS_REQUIRES_PAYMENT_METHOD = 'requires_payment_method';
70	const STATUS_SUCCEEDED = 'succeeded';
71
72	/**
73	* @param null\|array $params
74	* @param null\|array\|string $opts
75	*
76	* @throws \Stripe\Exception\ApiErrorException if the request fails
77	*
78	* @return \Stripe\SetupIntent the canceled setup intent
79	*/
80	public function cancel($params = null, $opts = null)
81	{
82	$url = $this->instanceUrl() . '/cancel';	1✔
83	list($response, $opts) = $this->_request('post', $url, $params, $opts);	1✔
84	$this->refreshFrom($response, $opts);	1✔
85
86	return $this;	1✔
87	}
88
89	/**
90	* @param null\|array $params
91	* @param null\|array\|string $opts
92	*
93	* @throws \Stripe\Exception\ApiErrorException if the request fails
94	*
95	* @return \Stripe\SetupIntent the confirmed setup intent
96	*/
97	public function confirm($params = null, $opts = null)
98	{
99	$url = $this->instanceUrl() . '/confirm';	1✔
100	list($response, $opts) = $this->_request('post', $url, $params, $opts);	1✔
101	$this->refreshFrom($response, $opts);	1✔
102
103	return $this;	1✔
104	}
105
106	/**
107	* @param null\|array $params
108	* @param null\|array\|string $opts
109	*
110	* @throws \Stripe\Exception\ApiErrorException if the request fails
111	*
112	* @return \Stripe\SetupIntent the verified setup intent
113	*/
114	public function verifyMicrodeposits($params = null, $opts = null)
115	{
116	$url = $this->instanceUrl() . '/verify_microdeposits';	×
117	list($response, $opts) = $this->_request('post', $url, $params, $opts);	×
118	$this->refreshFrom($response, $opts);	×
119
120	return $this;	×
121	}
122	}

stripe / stripe-php / #7087

Source File Press 'n' to go to next uncovered line, 'b' for previous

Source File
Press 'n' to go to next uncovered line, 'b' for previous