Multiple Websites to one Payment Provider

[Ivan Chong]

Hello Everyone!

Im fairly new to Kill Bill, was wondering how do we integrate multiple ECommerce websites (say 3) to a single Kill Bill instance, that works with one Payment Provider, like Stripe?

Thank you in advance!

[karan bansal]

Hi Ivan,

Thanks for writing in! Welcome to Killbill :)

Killbill is essentially designed to support Multi-tenancy i.e. each website in your case will become a separate tenant in turn giving you the ability to have separate catalogs, accounts and all entities separate. 

You can read more about here and here. 

Let me know for any follow up questions.

Regards

Karan

[Ivan Chong]

Hey Karan,

Thank you so much!

[sh...@methodmaker.co.nz]

Hi Karan,

We are also interested in using Kill Bill as a payment processor for upstream eCommerce systems. Can you provide more information about how this would be supported. 

You suggest setting up seperate tenancies for each upstream ecommerce system. Is there an alternative approach that would also work? For example can we configure each ecommerce system to use a given account, say ecommerce-site-1 ecommece-site-2 etc in the same tenancy?

We would also like to know what payment apis are called and the sequence in which they need to be invoked.

Thanks in advance

Shaun

[Mary McCauley-Stiff]

Hi Shaun,

>>You suggest setting up separate tenancies for each upstream ecommerce system. Is there an alternative approach that would also work? For example can we configure each ecommerce system to use a given account, say ecommerce-site-1 ecommece-site-2 etc in the same tenancy?

If these separate ecommerce websites were ONE tenant, they would need to share the same catalog and customer accounts. Does that fit your business case? (For the catalog portion, you could possibly develop a catalog plugin to handle different catalogs for each website.) 

>> We would also like to know what payment apis are called and the sequence in which they need to be invoked.

Check out the Payment Routing section of the Developing a Payment Control Plugin guide. 

Regards,

Mary

[Shaun Forgie]

Hi Mary,

So are you saying that the direct payment API needs to reference an existing product plan and price list defined in the current catalog? I was under the impression that we could configure this behaviour to deal with raw payments independently of the catalog. 

I had imagined that Kill Bill could be set up to either create accounts and payment methods automatically as part of the payment processing flow. For example an upstream eCommerce cart would pass the total amount | currency through to KB. This would then redirect the user to a KB payment page which would present the user with payment gateway | payment method options based on Tenant | Account settings.

Rgs

Shaun

--
You received this message because you are subscribed to a topic in the Google Groups "Kill Bill users mailing-list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/killbilling-users/0xMZUrnbtMY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to killbilling-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/killbilling-users/649451c2-e3f7-45ac-b368-f6929b6d2c12n%40googlegroups.com.

--

Shaun Forgie [Principal] - Method Maker Ltd
57a McIntyre Rd, Manukau 2022, Auckland, New Zealand
Mobile +64 21 666 910

[Mary McCauley-Stiff]

Hi Shaun

>>So are you saying that the direct payment API needs to reference an existing product plan and price list defined in the current catalog? I was under the impression that we could configure this behaviour to deal with raw payments independently of the catalog.

Nope - I am not saying that. I was only addressing the use case of having multiple websites (ecommerce1, ecommerce2, etc.) under the SAME tenant.

>>I had imagined that Kill Bill could be set up to either create accounts and payment methods automatically as part of the payment processing flow. For example an upstream eCommerce cart would pass the total amount | currency through to KB. This would then redirect the user to a KB payment page which would present the user with payment gateway | payment method options based on Tenant | Account settings.

This sounds reasonable, though I'd like someone else on the KB team to correct me if I'm wrong.

Regards,
Mary

[Mohamed]

Hello All, 
Reviving an old discussion. i have a case of an edtech platform where schools can sell their classes and courses, do each school have to get their own tenants.
Or is it better to keep one tenants for all the schools but will need to tag invoice and payments to know from who they belong to?
It's more of a scalabilty issue, i don't know how KB will behave if we have 100's of tenants?

kind regards,
moh