Method Community

Hello,

I see that Method uses Method CRM for its own internal use. I also noticed that Method provides a "Portal" called "Subscriptoion Portal". We would like to mimic the subscriotion portal features such as:

1. Storing reacurring account information. (Credit Card and Bank Account Info). How is Method handeling this and who stoes the data to be PCI compliant?
2. Subscription Billing Date Handeling
3. Auto Recurring transactions, how is this handeled?

It seems that our billing model fits similar to what Method is using and the number of billable subscriptions can change throughout the month which should reflect in the billing. I am trying to vaiod reinventin gthe wheel and looking for some valuable feedback from Method?

Hi jwarren,

jwarren:

I see that Method uses Method CRM for its own internal use.

We definitely do!

jwarren:

I am trying to vaiod reinventin gthe wheel and looking for some valuable feedback from Method?

Our portal screens are customized but you can definitely achieve similar functionality if desired.  The customization would be a little involved for a subscription billing model so I highly recommend you speak with a Method Solution Provider or book a session with a consultant on staff.  

If you're looking to build this on your own, we can provide a little support via the forms but you may require more help than we can offer here.  Your best best is to start by making a copy of the current portal pages and dig into how these work.

With regards to PCI comliance, storing credit card numbers is something we strongly discourage.  Consider credit card tokenization if you want to store the details of a customers credit card for recurring billing.  Speaking with a solution provider or a consultant in this regard will really help you design the best system to be able to offer recurring billing.

~C

Chad,

We are exploring different "Credit Card Tokenization" options. We are looking closly at Authorize.NET CIM solution. We plan on using some consulting time soon but I would like to veify if we are headin gin the right direction. We would lieke to follow the path of least resistance and wif Method has their customer portal already working with tokenization then we will likly follow suit. Please advise.

Hi jwarren,

Token authentication is not something we have implemented yet, however it is something we are planning for. Unfortunately I don't have a timeframe to provide for you. This is something that has been discussed in the past, check out the following link: http://www.methodintegration.com/cs/forums/p/1286/10114.aspx#10114

- Ashur

Ashur,

Method stores its customers payment account information as we are all billed every month without the requiremnt of renerting our payment information. I am just looking to find out what Method has found to be the solution for it's own billing? We do not want to reinvint the wheel so if Method is using a payment gateway with PCI complioanant tokenization then we would like to move in a similar direction. I was hoping someone could shed some light?

Our system is using the MethodAPI with a custom screen but no tokenization. This is not something we'll be providing to other companies since we have plans to work with authentication tokens, which will probably be happening sometime next year.

- Ashur