SaaS Event-Ticketing Plattform. How to properly cancel all running "CheckoutSessions"?

[viral prism]

Hi there,

I'm building an event ticketing platform where organizers can register and connect their Mollie account with my platform Mollie account via Mollie Connect. It should be possible that the organizer can also disconnect their Mollie account from the platform. But when they disconnect, there could be 1000 people currently in a checkout session on the mollie.com website paying with credit card, PayPal, and so on.

So my idea is to just invalidate all running checkout sessions. But I am not sure if this is the correct way. Currently, it's also not possible because the payment.IsCancelable flag is false even though the status of the payment is open.

What's the suggested way of correctly disconnecting a connected Mollie account from my platform?

[vale spire]

@rough oar @hard ingot

[viral prism]

It seems like that mollie docs does not have the scenario of disconnecting a connect account: https://docs.mollie.com/docs/connect-platforms-getting-started I asked gemini and let them research that suggested a more complex Graceful Draining Strategy. Is this the way to go? I would love to see a documentation from mollie but there is none. https://gemini.google.com/share/46ae850c178e

[hollow cedar]

The biggest problem is that once a transaction is started within Mollie it gets dispatched to other partners and banks.

At that moment mollie depends on those secondary partners for the result and capabilities. (Eg the capability to cancel a transaction)

To adress your concerns on open transactions while disconnecting the mollie connection.
Might it be feasible to built in a grace period, in which you wait until all started transactions reach an end state?

[viral prism]

I wonder if it would be better to try to do it with authorize capturing flow. So if a ticketbuyer gets to the checkoutwebsite hosted by mollie and then decides to make a payment after a while with paypal, mollie informs my webserver about this event and my webserver then can capture the payment. If the webserver registered that the organizer disconnect his account, the webserver can just not capture the payment and instead release the money from the authorized payment.

I also using stripe and with stripe I can just expire all running checkoutSessions with await sessionService.ExpireAsync(order.StripeCheckoutSessionId, null, requestOptions); but I also have to research more to this.

[viral prism]

Are there any updates?