#san_api

1 messages · Page 1 of 1 (latest)

sonic onyxBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1332275290247794699

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

tiny matrix
#

When a buyer pays (e.g., using a credit card or Apple Pay), that transaction does not appear under the connected account's Dashboard, it only shows up in the platform's Dashboard.
Seems expected given that the API objects are created on the platform not the connected account. on_behalf_of just describes the settlement merchant: https://docs.stripe.com/connect/destination-charges#settlement-merchant

Create charges on your platform account, collect fees, and immediately transfer the remaining funds to your connected accounts.

#

Is there any integration mode that allows us to see the connected account's transactions in both the platform's Dashboard and the connected account's Dashboard.
Not really, no. In the scenario you describe (SC&T) then only the transfer from your platform to the conncted account would appear on the connected account's Dashboard

covert herald
tiny matrix
#

Correct

covert herald
#

ok thanks @tiny matrix

covert herald
tiny matrix
#

Completely unrelated really. That header just facilitates you making API calls for your connected accounts

sonic onyxBOT
cursive cove
#

👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!