#stripe_connect_platform

1 messages · Page 1 of 1 (latest)

verbal patrolBOT
earnest kettle
#

Good question. Just to make sure I understand your situation right: are your connected accounts all standard connected accounts that can create these payment links otherwise?

#

In that case, I don't know if there will be a good way to check this from the Stripe objects themselves. You may have to record the IDs of which payment links you created on your own servers and only display those

vital iris
#

yes. connected accounts are all standard connected accounts that can create these payment links otherwise

#

you guys make it really hard to collect our application fee.

#

ok, we are doing something like that. ok. I wish there was an attribute.

#

we are using metadata but it is easily hackable and makes a big financial difference to us

#

but ok

#

i think we did it the best way given the constraints.

earnest kettle
#

One thing you might be able to do here is listen for the payment_link.updated event. You can check the event's previous_attributes hash to see if the payment link's metadata has been changed. It would let you detect when your metadata is removed here so you could add it back and flag to your user not to remove it

#

Can you clarify more of your issues on collecting your application fee here?

vital iris
#

uh it is so complex you guys. Stripe made this really complex. It would take me 5 pages but in general

#

We would love to just take a Payment Link they made in your beautiful UI and update it so we get our application fee.

#

but we cannot. 😦

#

I understand why but we cannot.

#

Even if the customer wants this they cannot.

#

So.....

#

We also would love if we could create a simple simple Payment Link via the API and let the customer via his own dashboard update it with all the bells and whistles. But the customer is blocked from updating his own link created by us in his own dashboard. He cannot. 😦

#

You throw an error that "links created via the API cannot be updated in the dashboard"

#

We requested an locked true/false attribute or something.

#

So....

#

We just spent 6 months and $$$$$ creating the entire same options you guys offer in the dashboard to work around all the above constraints so the customer can make complex payment links in our UI. That is the only way I could figure out to work around all the contraints.

#

Now that we did all the above, we want to get the application fee for all that work. heheh

#

so complex! could be really simple if we could have just let the customer create a simple simple link in our app and update thecomplex options in Stripe dashboard. That is the issue in summary.

#

Anyway so here we are and we just want to show the links in our UI that they made in our UI and let them just use those if they want to use our plugin.

earnest kettle
#

Gotcha, thank you for laying that out. I can see how your life could have been a lot easier if either editing your user's payment links or them updating the ones you create via the API was possible. I'll put in some more feedback about this or add to whatever we have recorded from the last time you raised this. Like you said some of this is an understandable restriction but this could be worth pushing on a bit more.

vital iris
#

Now please don't. 🙂

#

Basically it was so much work that we have a little competitive advantage since no one but me would be crazy enough to code all that!!! 😉

earnest kettle
#

Yeah, fair enough. Bravo on recreating that much UI functionality

vital iris
#

if you allow it, i should have just sat on the beach the last 6 months and waited for you guys to add a locked attr to Payment Links.

#

i am sort of kidding since i know Stripe is always moving fast to meet customer needs.

#

Well yours is better since you have a crazy preview that is dynamic and shows errors. I really wanted a simple flow of initial creation by us and update by the customer in his dashboard where he gets that cool dynamic preview but i gave up on the request as we never heard anything from the Payment Link API team on that.

#

Anyway, sunk cost. OK, thanks! We will do our best given the constraints. Thank you!

#

"You have to do what you cannot not do" -
Cloud Atlas

#

lol

earnest kettle
#

Yeah definitely! This is a great solution within what was possible here. Sorry to hear it was really involved, hope we can avoid things like that being necessary for the flows you want to make in future

vital iris
#

👍