My name is Oleksandr, I'm interested in your project and have a few questions. A unified API seems really useful, but in my experience, the challenge isn't opening the checkout page, but rather handling different subscription cycles across different providers. Stripe and PayPal handle failed payments, cancellations, refunds, trial periods, and so on differently. How does your PayCan service handle these states without losing provider-specific data? Can the application access the original provider event if a unified model isn't sufficient?
Not right now, but it’s one of the most interesting features on our roadmap. Still waiting to see if the repo itself gets any attention from developers. TBH, I’m a little disappointed at the moment.
My name is Oleksandr, I'm interested in your project and have a few questions. A unified API seems really useful, but in my experience, the challenge isn't opening the checkout page, but rather handling different subscription cycles across different providers. Stripe and PayPal handle failed payments, cancellations, refunds, trial periods, and so on differently. How does your PayCan service handle these states without losing provider-specific data? Can the application access the original provider event if a unified model isn't sufficient?
Will it support usage based credit payment for AI applications. I am currently working on One.
Not right now, but it’s one of the most interesting features on our roadmap. Still waiting to see if the repo itself gets any attention from developers. TBH, I’m a little disappointed at the moment.
whats's the stack?
It uses PHP, Laravel and SQLite. We want to make it installable even on a simple shared hosting.