#jchannon

1 messages · Page 1 of 1 (latest)

radiant wolfBOT
lavish perch
#

I think you can edit capabilities by clicking the connect account in the connect accounts tab of your dashboard and scrolling to the bottom

#

There should be a capabilities section

nimble kestrel
#

that's what I was hoping but can't see anything

lavish perch
#

Gotcha. Not sure then. We're not really dashboard experts in here. We mostly just help developers integrate our api

#

You could ask our support team: https://support.stripe.com/contact

Stripe: Help & Support

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

#

Please never publicly share your secret key

#

Can you reshare the snippet you tried without the secret key in it?

nimble kestrel
# 
curl https://api.stripe.com/v1/accounts/acct_1Nie8c4ZjO5tDYHa \                        
  -u REDACTED: \
  -d "capabilities.transfers=true"
{
  "error": {
    "code": "parameter_unknown",
    "doc_url": "https://stripe.com/docs/error-codes/parameter-unknown",
    "message": "Received unknown parameter: capabilities.transfers. Did you mean capabilities?",
    "param": "capabilities.transfers",
    "request_log_url": "https://dashboard.stripe.com/acct_1Nie8c4ZjO5tDYHa/test/logs/req_6PmcjHmw0IUSfC?t=1692891923",
    "type": "invalid_request_error"
  }
}
lavish perch
#

try capabilities[transfers]

nimble kestrel
#

bingo, thanks

#

hmm still an exception though

#

does it take time for transfers to be acknowledged inside Stripe?

lavish perch
#

What exception

radiant wolfBOT
nimble kestrel
#

Your destination account needs to have at least one of the following capabilities enabled: transfers, crypto_transfers, legacy_payments

lavish perch
#

Can you share the request id?

nimble kestrel
#

req_d15VM4BSsjVjcE

#

i've just done a GET on the account and capabilities is empty even though the earlier POST seemed to succeed

lavish perch
#

Looks like you sent the same idempotency key for that transfer

#

So the same response was used

#

Try making the transfer without idempotency key or using a different key

nimble kestrel
#

diff key same error

#

requestid : req_uKuNlO2tvkkanP

lavish perch
#

I don't actually see a request where you enabled transfers

#

But I also see that account has charges disabled

#

And that's a pre-requisite for enabling transfers I believe

#

You'll need to fulfill the outstanding requirements on the account

nimble kestrel
#

i can see the requirements via curl but i can't see a way to resolve them in the dashboard

# 
curl https://api.stripe.com/v1/accounts/acct_1Nie8c4ZjO5tDYHa \                                                                                         
  -u REDACTED: \
  -d "tos_acceptance[date[1692893067]]"
#

is that valid?

fluid island
#

👋 hopping in here since codebame_duchess has to head out

nimble kestrel
#

thanks

#

i tried adding the ip too but this payload is invalid -d "tos_acceptance[date]=1692893067, tos_acceptance[ip]=78.32.147.140"

#

should it be json?

fluid island
#

You're likely making your curl requests wrong you probably want -d "tos_acceptance[date]"=1692893067 -d "tos_acceptance[ip]"="78.32.147.140"

nimble kestrel
# 
curl https://api.stripe.com/v1/accounts/acct_1Nie8c4ZjO5tDYHa \                                                     
  -u REDACTED: \
  -d "tos_acceptance[date]=1692893067" \ -d "tos_acceptance[ip]=78.32.147.140"

{
  "error": {
    "code": "parameter_missing",
    "doc_url": "https://stripe.com/docs/error-codes/parameter-missing",
    "message": "Missing required param: tos_acceptance[ip].",
    "param": "tos_acceptance[ip]",
    "request_log_url": "https://dashboard.stripe.com/acct_1Nie8c4ZjO5tDYHa/test/logs/req_Svhl4syZTBY3qf?t=1692893430",
    "type": "invalid_request_error"
  }
}
curl: (3) URL using bad/illegal format or missing URL
curl: (3) bad range in URL position 16:
tos_acceptance[ip]=78.32.147.140
fluid island
#

Backing up for a second here - why are you making curl requests and not using one of our server-side libraries to make these requests? Is this just a one-off test?

nimble kestrel
#

yeah

#

i've got a test connect account that seems to have missing requirements and then i'm using the server side libraries to send a transfer request to it

#

the exception i get above is from the .NET Stripe library

fluid island
#

Just do it all on one line to be sure it works
curl https://api.stripe.com/v1/accounts/acct_1Nie8c4ZjO5tDYHa -u REDACTED: -d "tos_acceptance[date]=1692893067" -d "tos_acceptance[ip]=78.32.147.140"

nimble kestrel
#

that did it however

# 
"error": {
    "message": "You cannot accept the Terms of Service on behalf of Standard and Express connected accounts.",
#

🙂

#

ok i'll see if i can setup a test new connected account

fluid island