#hugo-tessera_api

1 messages ¡ Page 1 of 1 (latest)

whole tundraBOT
hallow graniteBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

whole tundraBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1249551555657597038

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

surreal elbow
#

Here a summary of the sitution.
In my example, the 'platform account' is called "tessera"
I have created a payment of 100 SGD with a checkout session using the Destianation Charge flow.
So, the payment is received by the platform account, then transfered to the connected account. The fees are deducted and sent back to the platform account

coarse owl
#

Which and where do you want the name to be shown? Is it on the descriptor of customer's bank statement?

surreal elbow
#

so From the connected account perspective, using the embedded component, he will see the following:

#

Basically, I would like that the connected account sees that the transaction comes from his customer, not from the platform account

coarse owl
surreal elbow
#

So, when checking all the payment he receives, the connected account will see a payment of 100 SGD made by the platform account, which correspond to the transfer of funds that occurs using 'Destination Charge' flow
But I would like him to see the actual email of the customer that initiated the payment

#

thanaks, let me check this

#

Ok, I think the link you shared me enable to update the description of the transfer to add some info, which is nice and we are actually already doing that
What I would like to see is the email address of initiator of the payment (the actual customer), not the platform account

coarse owl
#

The description of the payment on the platform doesn't get populated to the payment on the connected account

#

You'd need to update the description of payment that is transferred from platform to connected account manually in order to show the custom description such as customer's email address

#

By default, the payment on the connected account will display platform account's name

surreal elbow
#

So what you are describing, we already have.
We updated the description of the payment that is transfered from platofrm account and added some info, including the customer email

#

What I want, is, instead of showing that the payment initiator is the platform account (which is the case using destination flow), I would like to show the customer email

ps: I won't be surprise if thats not possible tbh

coarse owl
#

Ah sorry! Let me take a closer look why the description on the destination payment isn't shown correctly

surreal elbow
#

Also, just fyi, this is the view using the embedded payment components

coarse owl
#

This is indeed strange! Custom description is supported on the payments embedded component as well

#

Still checking

#

This seems like a bug to me, and I'm able to reproduce the issue by following this guide (https://docs.stripe.com/connect/supported-embedded-components/payments#customising-description). Can I suggest writing to Support https://support.stripe.com/contact with the example destination payment ID (py_xxx), so that we can follow up with you on this matter?

Show a list of payments with export, refund, and dispute capabilities.