You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rbi/stripe/resources/account_link.rbi
+33-13Lines changed: 33 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -10,50 +10,70 @@ module Stripe
10
10
classAccountLink < APIResource
11
11
# Time at which the object was created. Measured in seconds since the Unix epoch.
12
12
sig{returns(Integer)}
13
-
attr_reader:created
13
+
defcreated;end
14
14
# The timestamp at which this account link will expire.
15
15
sig{returns(Integer)}
16
-
attr_reader:expires_at
16
+
defexpires_at;end
17
17
# String representing the object's type. Objects of the same type share the same value.
18
18
sig{returns(String)}
19
-
attr_reader:object
19
+
defobject;end
20
20
# The URL for the account link.
21
21
sig{returns(String)}
22
-
attr_reader:url
22
+
defurl;end
23
23
classCreateParams < Stripe::RequestParams
24
24
classCollectionOptions < Stripe::RequestParams
25
25
# Specifies whether the platform collects only currently_due requirements (`currently_due`) or both currently_due and eventually_due requirements (`eventually_due`). If you don't specify `collection_options`, the default value is `currently_due`.
# The URL the user will be redirected to if the account link is expired, has been previously-visited, or is otherwise invalid. The URL you specify should attempt to generate a new account link with the same parameters used to create the original account link, then redirect the user to the new account link's URL so they can continue with Connect Onboarding. If a new account link cannot be generated or the redirect fails you should display a useful error to the user.
# The type of account link the user is requesting.
53
71
#
54
72
# You can create Account Links of type `account_update` only for connected accounts where your platform is responsible for collecting requirements, including Custom accounts. You can't create them for accounts that have access to a Stripe-hosted Dashboard. If you use [Connect embedded components](/connect/get-started-connect-embedded-components), you can include components that allow your connected accounts to update their own information. For an account without Stripe-hosted Dashboard access where Stripe is liable for negative balances, you must use embedded components.
# Time at which the object was created. Measured in seconds since the Unix epoch.
33
33
sig{returns(Integer)}
34
-
attr_reader:created
34
+
defcreated;end
35
35
# When present, the deadline for sending the notice to meet the relevant regulations.
36
36
sig{returns(T.nilable(Integer))}
37
-
attr_reader:deadline
37
+
defdeadline;end
38
38
# Information about the email when sent.
39
39
sig{returns(T.nilable(Email))}
40
-
attr_reader:email
40
+
defemail;end
41
41
# Unique identifier for the object.
42
42
sig{returns(String)}
43
-
attr_reader:id
43
+
defid;end
44
44
# Information about objects related to the notice.
45
45
sig{returns(T.nilable(LinkedObjects))}
46
-
attr_reader:linked_objects
46
+
deflinked_objects;end
47
47
# Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode.
48
48
sig{returns(T::Boolean)}
49
-
attr_reader:livemode
49
+
deflivemode;end
50
50
# Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
51
51
sig{returns(T.nilable(T::Hash[String,String]))}
52
-
attr_reader:metadata
52
+
defmetadata;end
53
53
# String representing the object's type. Objects of the same type share the same value.
54
54
sig{returns(String)}
55
-
attr_reader:object
55
+
defobject;end
56
56
# Reason the notice is being sent. The reason determines what copy the notice must contain. See the [regulated customer notices](https://stripe.com/docs/issuing/compliance-us/issuing-regulated-customer-notices) guide. All reasons might not apply to your integration, and Stripe might add new reasons in the future, so we recommend an internal warning when you receive an unknown reason.
57
57
sig{returns(String)}
58
-
attr_reader:reason
58
+
defreason;end
59
59
# Date when the notice was sent. When absent, you must send the notice, update the content of the email and date when it was sent.
60
60
sig{returns(T.nilable(Integer))}
61
-
attr_reader:sent_at
61
+
defsent_at;end
62
62
classListParams < Stripe::RequestParams
63
63
# A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list.
# A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
# Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to `metadata`.
0 commit comments