jasperste

[visual solstice]

Hello! We'll be with you shortly. 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.

• jasperste, 5 hours ago, 13 messages

[prisma anchor]

If the embedded component does not support them then creating your own button that makes the API call will be the way to go.

Just to double check, is that a limitation that we document somewhere, or are you getting an error when trying to use the embedded component to instantiate a refund on a Custom account?

I haven't played much with this API myself. Trying to reproduce now, but I can see our demo in our doc for the embedded component uses a Custom account and the UI at least has a refund button. So this may be possible

[visual harbor]

With Standard the customer is a customer of the merchant, meaning refunds are done directly from merchant to customer. With Custom the payments are usually done via us, meaning the customers of the merchant pay us and we transfer the money (destination charges with on_behalf_of). This seems to be a reason why payments are shown differently

For example

this one is Standard and allows a refund

The first one shows payments as if they are coming from us (Connect Custom), the second one shows as payments from their actual customers (Connect Standard)

(all test payments btw)

[prisma anchor]

Would you mind sending me the ID of an account session that you created for a custom account? Having trouble getting this to work on my account. I did not realize that this is beta functionality, so our beta team may be better able to speak to what you can do here but I am still happy to try myself to see if I can get an idea of what is possible with this API

[visual harbor]

Yes, 2 seconds!

acct_1ONEQyQRNrLyyRPS

oh sorry, you said session

Not sure how to get an id. It returns a client secret currently

[prisma anchor]

Client secret should work as well if you can send that

[visual harbor]

_PYsdkqffDPi58ZsxknPtOiBHRiFMl9DsxjNncl63y8CFjIh

[prisma anchor]

Thank you, trying to find this

[visual harbor]

Thanks for helping out!

this is a difference, this is the details for the Connect Custom payments

And this for Standard (including a refund button)

(we use the same API call for both Standard and Custom btw, so we use refund_management=>true, dispute_management=>true, capture_payments=>true and payouts.enabled=>true). We are able to set different params for Custom, but not sure which one

For Custom it seems to show payments as coming from us (which is theoretical, but not very helpfull in this component), for Standard it shows payments as we expected

[prisma anchor]

Gotcha. Unfortunately I still haven't been able to get myself set up to test this and am not finding much info documented on this flow. If you reach out to the beta team, they should have a better idea on whether there is an easy stripe-hosted way for your custom accounts to initiate refunds like this.