#Zia

1 messages · Page 1 of 1 (latest)

fading iglooBOT
crimson gale
#

hi! what exactly are you looking to do?

steep cove
#

ok, let me explain in details

#

we are using standard connected stripe account
and creating products on the standard connected accounts

#

now we have a scheduled subscription that is created on standard account

#

we need to enable our client to purchase that

#

but on generating the token for payment

#

stripe says that the token in not valid

#

card[number]=4242424242424242&card[cvc]=456&card[exp_month]=05&card[exp_year]=29&guid=9e59f373-9038-4e70-874a-12a5933a768b836a68&muid=06631487-f136-4248-b0e0-2f950d4bc55d2340cd&sid=91743fb2-2cb2-41d2-a5da-3fdea10f132873f07f&payment_user_agent=stripe.js%2F63fd7ebb3%3B+stripe-js-v3%2F63fd7ebb3&time_on_page=51243&key=pk_test_e1qKCH8nGu2pauX2C5bTbkwg00kuJL38au

crimson gale
#

what's the exact error message you're getting and the request ID req_xxx for the error?

steep cove
#

sure let me get that

crimson gale
#

also why are you using the Tokens API? It's deprecated; you should use PaymentMethods/PaymentIntents/Checkout instead.

steep cove
#

request Id: req_S8ZTYIqQhPyYCI

#

standard Account Id: acct_1MZ7PgFpOYH1L8S2

#

we are dealing with a legacy application
which is using all this

crimson gale
#

so in that request you're trying to create a PaymentMethod on the connected account, but passing the ID of a Token created on the platform ,which won't work as they're different accounts

steep cove
#

😦

#

yes, that's what I want to know that how we can modify our token call to get the token generated on standard account

crimson gale
steep cove
#

instead of generating it on our platform