Who wants to write a Mod of the Month? Payment API mod

[pmkb]

Currently, vBulletin only really supports PayPal for recurring payments/subscriptions. However, many people can't (or won't) use PayPal.

From what I've been reading, the problem with a lot of the other Payment API that are supported for single payments is that their systems don't communicate necessary details for vBulletin to track the subscription status for renewals/cancellations.

So, how about a mod which takes the onus for tracking subscriptions away from the processors and puts it in vBulletin?

Ie. vBulletin could track subscriptions and initiate payments/billing on schedule. Technically, they would be one time payments then, but the process could be automated on the vB side so it handles the transitioning of usergroups when subscriptions are "cancelled" (from vB UCP).

vB could use a chron job that runs once a day (late at night for example) to process any subscription payments that are due.

With vB handling the subscription management, all the supported Payment APIs would suddenly become viable alternatives/complements to PayPal for subscriptions.

[wolfyman]

+1 I need authorize.net or basically anything except paypal.

[Zachery]

Originally Posted by pmkb

Currently, vBulletin only really supports PayPal for recurring payments/subscriptions. However, many people can't (or won't) use PayPal.

From what I've been reading, the problem with a lot of the other Payment API that are supported for single payments is that their systems don't communicate necessary details for vBulletin to track the subscription status for renewals/cancellations.

So, how about a mod which takes the onus for tracking subscriptions away from the processors and puts it in vBulletin?

Ie. vBulletin could track subscriptions and initiate payments/billing on schedule. Technically, they would be one time payments then, but the process could be automated on the vB side so it handles the transitioning of usergroups when subscriptions are "cancelled" (from vB UCP).

vB could use a chron job that runs once a day (late at night for example) to process any subscription payments that are due.

With vB handling the subscription management, all the supported Payment APIs would suddenly become viable alternatives/complements to PayPal for subscriptions.

You would have to store alot of information about your customers/users on your side and you'll need to make sure things are secure.