#umbra-price
nimble musk
most likely the secret key you're using in the app is not the one for the account who's dashboard you're looking at in the screenshot.
Or the price exists in test mode but you're using a livemode key, or vice versa
upbeat axle
Ok, I'll check it out and get back to you
The key I'm sending is test and the product is also created in test mode, do you have any other ideas?
nimble musk
are you sure it's right account? maybe you have multiple Stripe accounts and you're using the key from a different one.
upbeat axle
I am sure that this is the correct key, because it is installed globally and with the help of this key, before creating a subscription, I create a customer. Also, I used to have subscription for customers working, but I needed to change the logic to add subscription for connected accounts and after that I got this problem
That is, it worked with customer accounts but does not work with the customer account created for the connected account
nimble musk
that makes total sense then right since you're trying to use a Price on an entirely different account?
https://stripe.com/docs/connect/authentication you need to pass the Stripe-Account header to make a request to access data that exists on a connected account.
upbeat axle
I'm send my Stripe account, maybe another reason?
nimble musk
not sure what you mean
nimble musk
so if you do that, the API call is running on that Stripe account. So if you mention a Price ID in that API call, we are looking at that account for it.
so it naturally will give you a "no such" error if you're passing a Price ID that exists on your platform account instead of on the connected account you're running the API call on.
You'd need to create the Price and Products on the connected account in this model.
upbeat axle
Okay, maybe this isn't what I need at all then. I want to implement subscription to my platform for my connected accounts. Do I then have to create a product every time? This will be data duplication
nimble musk
who do you want to pay the Stripe processing fees and be liable for disputes?
upbeat axle
I did not have time to clarify the details regarding the commission with my customer, but as far as I understand, yes, the responsibility for resolving disputes will be on my platform
nimble musk
then you want to be using Destination-style charging where you create the subscription on the platform and use transfer_data.
make sure to read https://stripe.com/docs/connect/subscriptions fully.
Based on your answer above you want https://stripe.com/docs/connect/subscriptions#use-destination-charges-to-create-a-subscription but you built https://stripe.com/docs/connect/subscriptions#use-direct-charges-to-create-a-subscription instead (I see those Direct Charges docs are wrong too which confuses matters)
upbeat axle
I want to implement something similar to the example from the first link in the "Create subscriptions to bill connected accounts section" So I should use the transfer date then, right?
nimble musk
you're not billing the connected accounts are you? You're billing an end-customer by having your platform charge them and then transferring some of the funds from that charge to a connected account.
upbeat axle
excuse me and allow me to clarify - by the end customer, do you mean the one who pays for the prodcut to the connected accounts?
nimble musk
I suppose so. I mean, whomever it is that you charge to make money in your platform.
the way Connect works if you have a Customer buying something, a Platform facilitating the payment and a Connected Account receiving money.
upbeat axle
No, in this case I want the person who earns on my platform to pay for the subscription, i.e. the connected account owner
nimble musk
maybe in your set up you have a Customer that is the same underlying person as a Connected account(like you collect a credit card from the person owning the account and charge that). That's what the docs you mentioned about "billing a connected account" talk about.
But there's no actual link in the API there, the concepts are the ones I mentioned, you can have extra context on your side about the relationships between Customers and Connected accounts but it's not part of the API model.
nimble musk
No, in this case I want the person who earns on my platform to pay for the subsc...
cool then see my post above.
Either way, you'd have a Customer on your platform and then you can charge it using a subscription in any of the ways we support(in your case you likely want the Destination Charge example I linked to).
upbeat axle
Okay, thank you very much for your explanation and patience. I will read everything you sent and try to do it again
nimble musk
no worries. To be clear, I talk in terms of the API terminology
so there is a Customer buying something, a Platform facilitating the payment and a Connected Account receiving money. It's quite possible and somewhat common that the Customer and Connected Account can be the same person(or you just do a payment between the Customer and the Platform) but that's more like logic on your side(like in your database you say that John Doe has a Customer cus_123 on your platform that you can charge to make money/fees and also a connected account acct_1234 for receiving money) than actually being modelled in the API.
upbeat axle
That's right, the connected account and the customer are the same person, so I think we understood each other. Thanks again for the explanation, have a nice day😁
spare ploverBOT
This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact
whole meadow
@upbeat axle karllekko is out but I have re opened this thread. Do you have a new question about this?
upbeat axle
Hi, one minute
Hello. Yes, I read the documentation that was sent to me earlier and it seems to me that the transfer date is used to send funds to the connected account. I need to withdraw funds from the connected account user and send them to my account. That is, what is described here https://stripe.com/docs/connect/subscriptions#use-direct-charges-to-create-a-subscription I already tried to implement it and stopped at the error with the price, I understood what the matter was, but I don't understand how to create a subscription for an account. In support, I was told that I should have a customer account associated with the connected account. I created it as shown in the screenshot and how do I link it to subscriptions if my previous version doesn't work?
whole meadow
Not sure if I fully follow where this is going wrong. To clarify, are you currently creating these subscriptions on the connect account itself using the stripe_account parameter in the API? https://stripe.com/docs/api/connected_accounts
upbeat axle
Yes, I just need companies to subscribe to my platform
As I understand it, the customers in the connected account (which is on the screen above) are not needed for this, they are just customers of my connected account, right?
whole meadow
Correct, if the subscription lives on your platform then you don't need products and prices on the connected accounts.
So the plan is to have payments be made to your platform and then make transfers from your platform to the connected accounts basically?
upbeat axle
No, I plan to have the connected accounts pay me and that's it, then the money stays with me
whole meadow
Ah gotcha, so yes, you will still only need customer objects on your platform
upbeat axle
You mean I don't need connected accounts at all?
whole meadow
If you are only ever taking payments then yes you only need Customer objects. Customers are for taking payment, Accounts are for when you are paying money out
upbeat axle
Okay, but in the future I plan to make payments to connected account accounts from end customers, so I chose connected accounts.
So in order to implement subscriptions with connected accounts, I just need to create a customer account without connecting it to the connected account, right?
whole meadow
Right. You only need Customer objects when taking payments. Accounts aren't part of a subscription like that
upbeat axle
That is, if in the end everything looks like this, that there is a customer account and a separately connected account without subscriptions, then everything is fine, and it should be?
Please, just say yes or no?😅
rotund trout
Hi 👋 I'm stepping in for @whole meadow There is a lot going on here. Can you summarize what it is you are trying to accomplish?
upbeat axle
Hi Check out the last couple of posts
rotund trout
I see a lot of confusion about what Connect Accounts do versus Customers. I'd like you to give me your impression of how they work.
upbeat axle
As I understood from the messages above, I need the customer's account to implement the subscription, I need the connected account so that I can manage their funds - first freeze, and then pay out, but in this case, the customer and the connected account belong to the same person, correct ?
rotund trout
Just Customer, not Customer Account
We are specific about our terms to avoid confusion
But yes
Customer - can make payments to merchant for goods/services
Connect Account - Can be part of transactions, collecting share of revenue. The platform can also control payouts depending on the configuration
upbeat axle
Okay, but I need to implement the subscription for my connected account, so I create a customer account for it and already connect the subscription for this customer account. So as shown in the screenshots above, is that correct?
rotund trout
Okay it's not at all clear what is going on here so can you clarify the following:
- Subscription - Who is the customer and what are they subscribing to
- Connect Account - How are they involved in the subscription
upbeat axle
Yes, I just need companies to subscribe to my platform
My connected accounts subscribe to my platform, they are the customers in this case
upbeat axle
Okay, but in the future I plan to make payments to connected account accounts fr...
But in the future it will be like this
rotund trout
Okay so the Customer object is the one with the subscription in that case. But, since Discord truncates strings when quoting, I am not sure what "But in the future it will be like this" is referencing.
upbeat axle
I'm currently trying to create a subscription for connected accounts, that's why I'm here. But in the future, my published records will have end customers can send them money, so I'm creating a connected account
rotund trout
I'm currently trying to create a subscription for connected accounts
Because of how connect works this wording is confusing. do you mean create subscriptions on their behalf or with them as customers?
upbeat axle
With them as customers
rotund trout
Okay. So then you set them up as Connect Accounts once they have subscribed so that they can take part in other transactions through your platform?
upbeat axle
No, I plan to have the connected accounts pay me and that's it, then the money s...
As stated here
upbeat axle
Okay. So then you set them up as Connect Accounts once they have subscribed so ...
Yes, that's right
rotund trout
Alright, perfect. Then is the second screenshot you shared just to clarify that the Subscription won't show up in the Connect Account?
Because, as far as Stripe records are concerned, the Customer record and the Connect Account record are not related. It's up to your integration to keep track of that relationship
upbeat axle
Alright, perfect. Then is the second screenshot you shared just to clarify that...
Yes, because it confused me, as I understand they are not related in any way
rotund trout
That is understandable
But from Stripe's perspective, it's the Customer record and your platform Account that are in the relationship defined by the Subscription.
upbeat axle
So I have to configure this relationship?
Or should everything remain as it is in my case?
rotund trout
You cannot link them in Stripe. You need to keep track of the relationship between the Customer record and the Connect Account yourself