#brittkim
latent juniper
So like I said, I'm using Stripe connect, and I have a connected account (acct_1NsX5eEHE3e6biJR
). I created a product with that connected account.
Then on the frontend, I am using the CardElement with my publishable key. After submission, my backend creates a customer, a paymentIntent with the connectedAccountId
But when I try to create the subscription with that priceId, it says "No such price: 'price_1NsX9CEHE3e6biJRGC4d0zZU'"
So I figured, maybe the product needs to be created by my account, and not the connected account, but after that I got "No such customer: 'cus_OgHFgCcxfPqpGL'
But creating the customer on the connectedAccount's behalf, resulted with No such PaymentMethod: 'pm_1Nsv3uG51kXHv01dE1rWcHRl'; Which would mean I need to have the frontend use the customer's publishable key?
mortal raptor
Hi, you typically see this error when you create the object on one account and trying to access it using another account's API keys.
To step back, what charge type are you trying to use?
latent juniper
standard
mortal raptor
With Standard Connect account, I assume you're using direct charges. You can learn more about the charges types here: https://stripe.com/docs/connect/charges
To make calls on your connected account, you can use the Stripe Account Header here, https://stripe.com/docs/connect/authentication
So with all of your requests to create a customer, price, and payment method you can pass the Stripe Account header so you can make API calls for your connected accounts.
latent juniper
Yes, I'm about to do this with the backend
But the frontend card then becomes the problem
because the PaymentMethod is tied to my account, not the connected account
mortal raptor
Client-side libraries set the connected account ID as an argument to the client application. We document this here:
latent juniper
Ah!
Perfect! It's the same pattern of passing it in as an arg
okay! This will resolve everything I'm sure
mortal raptor
I think you might also be referring to cloning PaymentMethods: https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods
latent juniper
Thanks!
mortal raptor
Sure!
latent juniper
Okay! That allowed me to make the subscription without any backend errors... but it looks like the sub failed for some reason?
nocturne turtleBOT
mortal raptor
Can you share the request id that failed to create this Subscription?
mortal raptor
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
latent juniper
Hm, I actually don't see the requests. Is that because I made them with the connect account technically?
mortal raptor
You shared the screenshot above. Can you share the customer id instead then?
latent juniper
cus_OgHtOoC1B9IjMT
mortal raptor
Taking a look
So the Subscription was successfully created, https://dashboard.stripe.com/test/logs/req_ruKpZY7ozLej9m. I think this might be helpful to better understand how Subscriptions work: https://stripe.com/docs/billing/subscriptions/overview. The payment for this invoice did not succeed, and an action, 3DS authentication is required from the customer, https://dashboard.stripe.com/test/events/evt_1NsvJvEHE3e6biJRVAKwI9tY.
latent juniper
Hm, that's interesting. Though I used a stripe test card... Some payment methods require customer authentication
Is there a card that is already authenticated?
slow creek
Hello! I'm taking over and catching up...
We have a lot of different test cards here, some of which do not trigger authentication: https://stripe.com/docs/testing
latent juniper
ha, which ones? I don't see anything about a card not triggering authentication. I see a lot of cards that DO require it though haha
slow creek
Have you tried the 4242424242424242 test card?
slow creek
Sounds like you have Radar rules turned on that will try and force 3D Secure on any card that supports it.
latent juniper
Interesting
slow creek
The 4242 test card does not trigger 3D Secure by default, but it does support it.
latent juniper
Hm, these are brand new default accounts. Is that typical?
slow creek
No. Let me have a look at the specific transaction...
latent juniper
You need an id or anything?
slow creek
Nope, it's above, I'm good...
This might take a few minutes, haven't forgotten about you though!
Oh, I see it.
In your request to create the Subscription you specifically request 3D Secure: https://dashboard.stripe.com/test/logs/req_ruKpZY7ozLej9m
You set request_three_d_secure to any: https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_settings-payment_method_options-card-request_three_d_secure
latent juniper
Oh! I see. Does that default to automatic?
slow creek
Yes.
latent juniper
I just removed that code, and it still failed =/
slow creek
Can you give me the request ID?
latent juniper
I really want to, but I don't know how haha
when I look at my logs, there is nothing
slow creek
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Make sure you view the Dashboard as the connected account.
latent juniper
that's my problem, I don't control that account
slow creek
Navigate to the connected account you're making these requests on, click on the ••• button, and you should have an option to view the Dashboard as the connected account.
slow creek
This is the way to get that info.
slow creek
Looking...
latent juniper
I found the problem
slow creek
You used the 0446 test card:
This card requires authentication for one-time and other on-session payments. However, all off-session payments will succeed as if the card has been previously set up.