#kadeer.amin-whoop - Free Checkout
1 messages · Page 1 of 1 (latest)
You'll have to bear with me as I'm new to the project. We're currently creating and updating orders using this API. https://stripe.com/docs/api/orders_legacy/create
When a customer completes their order for the normal workflow we hit:
https://stripe.com/docs/api/orders_legacy/pay
OOooooo....orders.....hmmm that's really outdated and not recommended.
This is an angular codebase so I imagine it's very legacy
And you don't want to collect/create Customer and Payment Method objects in Stripe?
Yes, for context the end users are having their orders paid for in a B2B deal and they are just redeeming them separately.
So you are not collecting any payment at this time? What exactly do you need to use Stripe for at this point in your flow?
The hope is to leverage the existing hooks that we have for data tracking and order fulfillment
I understand that the use case here is rather unique
Okay so you are really looking to trigger a webhook that will update data in another part of the application?
Yes, there are quite a few moving parts it seems that are triggered as stripe updates the order to paid and fulfilled that we still want these orders to go through.
I understand that. The only modern equivalent I can think of would the the invoice object, which you could mark as paid out of band. However, those require a Customer object.
Is there a way to connect an invoice with an order or would the recommendation here be to switch to using invoices instead of orders?
I would switch but, like I said, you would. need to have a Customer ID to use invoices. Are these customers actual customers in Stripe?
There's no guarantee that they are customers in stripe since their affiliate is paying for them to have our product.
Okay that might make using Invoices a non-starter.
Unfortunately Orders are so out-of-date I cannot find any good docs on them. And I started at Stripe after they were superseded by other products so I'm kind of in the dark about how they work.
Out of curiosity how out-of-date are we talking here?
Looks like 2018 was the last mention of them in our API upgrade docs
And is there any chance you could ask around for additional suggestions? If we need to do a workaround I suppose we will for this case but I'd like to at least understand what the options are before doing so.
Given the lack of readily available information, this might be better handled as a Support Ticket. That way we can more easily route the request and make sure people with experience in Orders can put eyes on it.
That would be immensely helpful. Could you direct me to where I can submit this?
Sure thing!
https://support.stripe.com/contact/email
I've placed the ticket there. I appreciate you trying your best to help me out with this!
You are very welcome! i hope we can get this resolved for you relatively quickly.