killbill for external payments

[Yuri Buerov]

Hello,

We are considering killbill as subscriptions management system. At the moment we do not provide subscriptions, but we are planning to do so. 

We have our internal system, which is in charge of processing payments from different payment providers, and managing user accounts. So I'm wondering, is it possible to replace some parts of this system with killbill. 

What I'm looking for: 

1) Each user has his own account with balance. 

2) User can deposit money to account (we will not be able to use/implement payment plugins at the moment, as we already support multiple payment providers  and this part of the system works quite well, so we will track it in our system). 

3) User can withdraw money from their account.  Same remarks as for previous requirement. But here we have to have possibility  to reserve amount on user account (with check that user has sufficient balance),  and finalize or reverse payment transaction depending on payout status from particular payment provider (we process it in our system as I mentioned higher).

4) We can manually adjust an amount on user account. 

I'm just started exploring killbill documentation, and I have been playing with an API locally. I got confused that purchase payments are not affecting account balance (maybe some action from external payment plugin needed?), and from other hand, I can subtract any amount from user account using `invoices/charges/` endpoint and it does not depend on available balance. 

Maybe you guys, who are more  familiar with this system could help me to find out is it possible to use killbill for use cases listed above, and point me in the right direction.

Cheers 

[stephane brossier]

Answers inlined below

On Mon, Jun 7, 2021 at 11:26 AM Yuri Buerov <yurib...@gmail.com> wrote:

Hello,

We are considering killbill as subscriptions management system. At the moment we do not provide subscriptions, but we are planning to do so. 

We have our internal system, which is in charge of processing payments from different payment providers, and managing user accounts. So I'm wondering, is it possible to replace some parts of this system with killbill. 

What I'm looking for: 

1) Each user has his own account with balance. 

Supported by Account#balance

 

2) User can deposit money to account

I am not what you mean by deposit  money to account: What Kill Bill supports is the notion of Account#credit which can be used for subsequent invoices

 

(we will not be able to use/implement payment plugins at the moment, as we already support multiple payment providers  and this part of the system works quite well, so we will track it in our system). 

Using multiple payment providers seems unrelated to writing payment plugins -- it seems this would actually be mandatory unless you already have an internal payment system  integrating with your payment gateways?

3) User can withdraw money from their account.  Same remarks as for previous requirement. But here we have to have possibility  to reserve amount on user account (with check that user has sufficient balance),  and finalize or reverse payment transaction depending on payout status from particular payment provider (we process it in our system as I mentioned higher).

The opposite of Account#credit is  Account#charge -- or we also support deleting credits.

4) We can manually adjust an amount on user account. 

I'm just started exploring killbill documentation, and I have been playing with an API locally. I got confused that purchase payments are not affecting account balance (maybe some action from external payment plugin needed?), and from other hand, I can subtract any amount from user account using `invoices/charges/` endpoint and it does not depend on available balance. 

There are 2 main sets of payment apis, one is linked to invoices / account#balance and one is independent (pure payment integration, unrelated to subscriptions/invoices,...)