#hritik9607_api

1 messages ¡ Page 1 of 1 (latest)

native kilnBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1215552279164358698

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

unique cove
#

{
"future_requirements": {
"yelo-beta": {
"alternatives": [],
"current_deadline": 1713294000,
"currently_due": [
"settings.payments.statement_descriptor"
],
"disabled_reason": null,
"errors": [],
"eventually_due": [
"person_HB4gtdOVeSAujj.id_number",
"settings.payments.statement_descriptor"
],
"past_due": [],
"pending_verification": [
"business_profile.mcc"
]
}
}
}

in the future requirement it is giving me this

haughty martenBOT
unique cove
#

so i am unable to understand what data need to full fill by this connect user

queen hound
unique cove
#

Do I need to create a checkout link for a custom account user, on which they will fulfill the required data? This is because we've integrated the Stripe hosted checkout integration type.

#

please guide me what should i do here

queen hound
#

can you share the corresponding account id for which you're seeing that future requirements on? the prefix of the account id will be acct_

unique cove
#

acct_1GciHNIsbTYJtr0d

#

this is the account

queen hound
#

you can create an Account Link with type="account_update" and collection_options.future_requirements="include"

unique cove
#

let updateObj = {
account: stripe_account_number,
failure_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/error.html?domain_name=" + opts.domain_name,
success_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/success.html?domain_name=" + opts.domain_name,
type: 'account_update',
};

let acc_details = await stripe.accountLinks.create(updateObj);

if i am creating the account like this then where to use " collection_options.future_requirements="include" "

#

let updateObj = {
account: stripe_account_number,
failure_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/error.html?domain_name=" + opts.domain_name,
success_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/success.html?domain_name=" + opts.domain_name,
type: 'account_update',
collection_options.future_requirements="include"
};

#

so do i need to include collection_options.future_requirements="include" in the object which is passed in creating the link

queen hound
#
let updateObj = {
        account: stripe_account_number,
        failure_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/error.html?domain_name=" + opts.domain_name,
        success_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/success.html?domain_name=" + opts.domain_name,
        type: 'account_update',
        collection_options : {
            future_requirements : "include"
        },
    };
unique cove
#

ok let me try with this

unique cove
#

let updateObj = {
account: "acct_1GciHNIsbTYJtr0d",
failure_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/error.html?domain_name=" + opts.domain_name,
success_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/success.html?domain_name=" + opts.domain_name,
type: 'account_update',
collection_options: {
future_requirements: "include"
}
};

i am trying the above object but getting this
code: 'parameter_missing',
doc_url: 'https://stripe.com/docs/error-codes/parameter-missing',
message: 'Missing required param: collection_options[fields].',
param: 'collection_options[fields]',
request_log_url: 'https://dashboard.stripe.com/logs/req_FIrng0jaP9MG1K?t=1709882894',
type: 'invalid_request_error',

Learn more about error codes and how to resolve them.

#

statusCode: 400,
requestId: 'req_FIrng0jaP9MG1K'

queen hound
unique cove
#

let updateObj = {
account: "acct_1GciHNIsbTYJtr0d",
failure_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/error.html?domain_name=" + opts.domain_name,
success_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/success.html?domain_name=" + opts.domain_name,
type: 'account_update',
collection_options: {
fields: ["eventually_due","currently_due"],
future_requirements: "include"
}
};

is this object correct?

#

i mean this one

collection_options: {
fields: ["eventually_due","currently_due"],
future_requirements: "include"
}

queen hound
#

you can try

unique cove
#

type: 'StripeInvalidRequestError',
raw: {
message: 'Invalid string: {:"0"=>"eventually_due", :"1"=>"currently_due"}',
param: 'collection_options[fields]',

#

this error is coming
Error occurred: StripeInvalidRequestError: Invalid string: {:"0"=>"eventually_due", :"1"=>"currently_due"}
at StripeError.generate (/Users/hritik/Documents/test/node_modules/stripe/cjs/Error.js:10:20)
at res.toJSON.then.Error_js_1.StripeAPIError.message (/Users/hritik/Documents/test/node_modules/stripe/cjs/RequestSender.js:105:54)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
type: 'StripeInvalidRequestError',
raw: {
message: 'Invalid string: {:"0"=>"eventually_due", :"1"=>"currently_due"}',
param: 'collection_options[fields]',
request_log_url: 'https://dashboard.stripe.com/logs/req_p5HK1cyEkGgYxZ?t=1709883683',
type: 'invalid_request_error',
headers: {