Default to Recurring Payment

[olandir]

I would like to make it so that the checkout page defaults to the recurring payment. We're doing a partnership program which by its very nature is people signing up to partner long term. I've tried different ways of doing this, but to me, the setup doesn't make it intuitive as to what to do to make a recurring payment, which I think would cause a lot of problems with our online giving.

I would really like a way to make it so that repeating is on by default. Any help would be greatly appreciated. I would like people to be able to set the amount they want to pay monthly as well so any solution can't force a fixed amount.

[olandir]

Update, I've looked at both the Simple Basket and Form as a Service options. Both give the option to turn recurring on by default which is great, but they won't work unless you have a limit on them. You can't specify just to repeat the payment with no end? This only seems possible if someone chooses it manually. The closest i can get to this is setting the interval to 999 which is the highest you can set it to, but then on the checkout page it says "repeat for 999" intervals, which just looks goofy. Whereas if let the user turn repeat on manually, it just says repeat every month because I have "indefinite" in the policy. Why can't i duplicate this anywhere else so I can have this on automatically?

This seems like a simple request

[CnP.Support]

Good day!

Repeat with NO END is simply Installment= 999 - in the special case of 999 the receipt will reflect no END DATE for the recurring and asks the patron to contact the organization for cancellation.

So in FaaS simply hide the installment field and set it to 999 and it will do what you are trying to do.

The addition of Indefinite to the Classic and Catalog pages were done a while back but the option for always OPEN is not in there.

See release note & knowledge base article:

• http://forums.clickandpledge.com/sho...ght=indefinite
• http://forums.clickandpledge.com/con...rring-Payments

I will go ahead and add this to the request for one of the future updates.

[olandir]

Hi, thank you for the resposne. I went with the simple basket approach because FaaS had some shortcomings in it that I did not expect and we needed to get this up and running as quickly as possible. The only problem with "basket" is when you send "999" to it, it shows "999" in the basket itself which is a little goofy. I think a better way to do this would be for the basket not to show "999" to avoid any confusion.

[CnP.Support]

Good day!

It is hard for me to imagine the shortcomings of FaaS! It is the easy interface to the API and all of our system works off of the API platform.

FaaS offers every feature, except ticketing, that the full API offers but not requiring any programming knowledge.