#FocussedGrind
1 messages · Page 1 of 1 (latest)
We don't deduplicate against any fields for Customers, so you'd need to track that yourself somehow
Cool. Thanks
And we can save stripe customer id in our database (i.e, outside stripe env) correct?
Of course! Generally we'd recommend mapping the cus_xxx ID with a session/user in your system. If a session/user has a cus_xxx set, then prevent creating another
Got it.
And the request body for that endpoint could be only of format x-www-form-urlencoded , correct?
Yes, every endpoint expects form-urlencoded payloads:
The Stripe API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
Our customers pay 25$ and stripe fees is 2.9% + 30c and finally we (marketplace) get 23.97$. But for our customers, they should still see 25$. How can we add the difference amount to the customer's balance, but customer not noticing the difference that we market place adding the stripe fee difference
Sounds like you're a Connect platform? What kind of charges are you using?
yes, connect platform. Creating separate charges and transfers.
Then your platform your need to account for the difference, if the intention is to transfer 25$ to the connected account