[darrenwestall]

We’re about to implement a credit system for a new product, I’ll try this instead and feedback to you.

Would be amazing if you handled the buying of additional pay as you go credits for us too - that’s the next thing we’d need to build.

[darrenwestall]

Having to pay to try is a little disappointing, but I’ve done it.

Sent you a chat with some queries - we need to use cycles and payg in combination, and the api call to get remaining credits should include the cycle start and renewal date, with the different credit types remaining too.

The option to choose which credit type subtract should come from by default would be good too - to allow users to use their cycle credits first and then eat into their payg back up credits.

[fraromeo]

It's possible to use cycle and payg in combination, it's exactly the strength of Creduse.

About the `get-active-balance` endpoint - you're right, it's pretty basic at the moment. It just gives you the total active balance and user ID. It doesn't break down cycle vs PAYG credits or show cycle dates yet.

I've add it to the top of my pipeline. I'll be working on improving this endpoint to give you more detailed info about the user's credit balance.

Regarding the option to choose which credit type to subtract from, I'll keep this in mind and consider its feasibility. Can't promise anything on this just yet, but I appreciate the idea.

I really like your suggestions though! It's exactly the kind of feedback I'm looking for. Thanks for bringing this up, and thanks for subscribing!

[fraromeo]

Great! Thanks for giving Creduse a try.

By "handled the buying of additional payg credits" do you mean the payment processing?

[darrenwestall]

I do. I mean providing a JavaScript widget that lets people see their credits, renewal dates and buy more. Then it would be an end to end credit solution.